-
Deanna’s Freeware Spotlight: MultiPack Visual C+ Installer
If you install a lot of applications – particularly ones developed with Microsoft Visual Studio – you accumulate a lot of different Visual C++ redistributable libraries. In our day-to-day computing, we rarely, if ever, think about these runtimes — even when an application starts behaving badly. But when one of these packages becomes corrupted, it can be the culprit causing applications and games to crash or fail to start.
Freeware guru Deanna McElveen shows you how to take charge with a freeware program called MultiPack Visual C++ Installer by “BobSpwg”
In the new AskWoody Plus Newsletter issue 16.6.0 – out this morning. Now available – yes, for free — on AskWoody.
-
Patch Lady – Access gets beat up again
I was updating the master patch list tonight and spotted that there’s a new known issue listed on all of the Windows patches in regard to Access:
Last time it was Access 97 format, this time it’s Access 95 format. Apparently we keep old databases around for a long time.
It’s expected to be fixed in late February.
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working. Option 1: Convert the database to a newer .mdb file format. This doesn’t require a change to the Connection string. - Use Microsoft Access to open a database that has an older file format.
- You will be asked if you would like to convert. Click Yes and save the database with the .accdb file extension.
- Open the .accdb.
- From the File menu, click Save as and select Access 2002-2003 Database.
Option 2: Convert the database to the .accdb file format. To use the .accdb file format, you must change the Connection string after conversion.
The easiest way to convert is to use Microsoft Access 2010 or earlier.
- Use Microsoft Access to open a database that has an older file format.
- You will be asked if you would like to convert. Click Yes and save the database with the .accdb extension.
Microsoft is working on a resolution and estimates a solution will be available late February.
-
Anomalous, buggy behavior on AskWoody
While we’re waiting for the Windows Secrets merge to kick in (several delays, sorry), I’d like to come up with a list of clearly weird behavior on the Lounge, and toss the list to the devs.
Here’s my favorite:
Anonymous posters can create new topics.
AskWoody Loungers can create new topics.
AskWoody_MVPs cannot.
Also, I’ve seen many reports of AskWoody_MVPs not being able to edit their posts, or delete them. I tried several combinations with an AskWoody_MVP account and didn’t have any problems. There’s a 60-minute time limit on deletions. Can anybody replicate the problem?
-
Cimpanu: The US Govt Accountability Office recommends the US adopt GDPR-like privacy legislation
It’s about time.
Catalin Cimpanu, writing for ZDNet, has some great news:
An independent report authored by a US government auditing agency has recommended that Congress develop internet data privacy legislation to enhance consumer protections, similar to the EU’s General Data Protection Regulation (GDPR).
The report (PDF) recommends:
Congress should consider developing comprehensive legislation on Internet privacy that would enhance consumer protections and provide flexibility to address a rapidly evolving Internet environment. Issues that should be considered include what authorities agencies should have in order to oversee Internet privacy, including appropriate rulemaking authority.
It’s about time. (Although it looks like the report was published on January 15. First I’ve heard of it.)
-
Microsoft updates its schedule for SHA-2 ‘critical’ Win7 update, now due in March
Remember the dire warning, back last November, that you had to install a forthcoming Win7 security patch in order to continue to receive security patches?
I had an article in Computerworld about it:
Microsoft is changing its method for electronically signing patches from an old approach known as SHA-1 to the much more secure SHA-2. If you want to continue to get Win7, Server 2008 and WSUS security patches, you need to install a patch in February or March that makes Windows SHA-2-conversant.
I hadn’t heard anything more about the transition until @abbodi86 posted an update a few minutes ago. Ends up that Microsoft will push the patch in March, according to a new bulletin posted just a few hours ago:
Starting in early 2019, the migration process to SHA-2 support will occur in stages, and support will be delivered in standalone updates. Microsoft is targeting the following schedule to offer SHA-2 support.
March 12, 2019
Stand Alone updates that introduce SHA-2 code sign support will be released as security updates.
Windows 7 SP1,
Windows Server 2008 R2 SP1…
July 16, 2019
Required: Updates for legacy Windows versions will require that SHA-2 code signing support be installed. The support released in March and April will be required in order to continue to receive updates on these versions of Windows.
I’m sure you Win7 fans will love the fact that “legacy Windows” now includes Win7, Server 2008, and Server 2008 R2, but nevermind….
Nothing wrong with being a legacy, eh?
-
Pssssst… I still don’t believe the part about Microsoft testing 20H1, then jumping back to 19H2
I’ve read the reviews, seen the posts, and I still don’t believe it.
Dona Sarkar said yesterday:
Today we are releasing a new build to Insiders who have opted into Skip Ahead. These builds are from the 20H1 development branch. Some things we are working on in 20H1 require a longer lead time. We will begin releasing 19H2 bits to Insiders later this spring after we get 19H1 nearly finished and ready; once 19H1 is “nearly finished and ready” we’ll also use the Release Preview ring for previews of drivers and quality updates on 19H1.
In a world of truly absurd Windows beta testing, that’s even more absurd than normal.
I honestly don’t think we’ll end up with a 19H2. None at all. If Microsoft’s smart, they’ll move to 20H1 and dump this absurd every-six-month release rate. I know the arguments. I know that Office gets new versions every six months. But Windows ain’t Office. And it shouldn’t be hobbled with the same release cycle.
I’m still hopeful that 19H2 will go the way of the dodo.
-
Win10 updating terminology is changing again – but this time maybe it’s tied to a major improvement
In retrospect, I’m not convinced the terminology change is tied to anything worthwhile.
Details in Computerworld Woody on Windows.
Here’s my earlier, rosier take…..
******************************************
At least I have my fingers crossed.
First, John Wilcox announced on the Windows IT Pro blog:
IF YOU USE WINDOWS UPDATE FOR BUSINESS: Beginning with Windows 10, version 1903 (the next feature update for Windows 10), the Windows 10 release information page will no longer list SAC-T [Semi-Annual Channel Targeted] information for version 1903 and future feature updates. Instead, you will find a single entry for each new SAC release. In addition, if you are using Windows Update for Business, you will see new UI and behavior to reflect that there is only one release date for each SAC release. If you use System Center Configuration Manager, Windows Server Update Services (WSUS), or other management tools, there will now only be one feature update published to WSUS, and this will occur at the time of release.
That’s a major change to the meaning of SAC-T. I’ve long used the promotion of a Win10 version to SAC (from SAC-T) as an indication that it may be ready, in a few months, to install. Wilcox shows a screenshot of the new Win10 version 1903 Windows Update Advanced options pane, and it’s substantially different from what we’re seeing now.
Reason to be cynical – Oh gawd, they changed the terminology again.
Reason to be hopeful – maybe this means that when a new Win10 version is released it’ll be, you know, tested.
Combine that with more unexpected news. People in the Windows Insider Program Skip Ahead ring were expecting to start testing version 19H2 (for lack of a better term, probably destined to become Win10 version 1909). But earlier today, Microsoft released Skip Ahead build 18336. According to Dona Sarkar and Brandon LeBlanc:
These builds are from the 20H1 development branch. Some things we are working on in 20H1 require a longer lead time. We will begin releasing 19H2 bits to Insiders later this spring after we get 19H1 nearly finished and ready; once 19H1 is “nearly finished and ready” we’ll also use the Release Preview ring for previews of drivers and quality updates on 19H1.
Which is an incredibly convoluted way to run a beta program, unless….
… unless the talk of 19H2 is a smokescreen, and Microsoft’s finally going to start releasing new versions of Win10 every year.
Hey, a guy can hope.
-
Fred Langa: How do I unfreeze my laptop? I’ve pressed ctrl-shift-del but it did not work
You’d be surprised how few people know that they may need to take the battery out… if they can…
More words of classic wisdom from Fred Langa on his web site.