Windows 10 KB4535996 update creates fresh trouble for users

[Karlston]

Windows 10 KB4535996 update creates fresh trouble for users

It looks like Microsoft’s last optional update, Windows 10 KB4535996 has caused a lot of trouble for those who installed it. We reported last week that some users are complaining about BSODs, random freezes while trying to install the latest optional update and as a result of that, the KB4535996 update failed to install. But what is worse is that the update seems to have created new problems for some users.

 

Users on Microsoft Forum, Twitter, and on various other platforms voiced their concerns about the optional update because the update makes it impossible for some users to put their PCs on Sleep mode. Users are complaining that PCs are waking up automatically from the Sleep mode after installing the update.

 

Another user took to Twitter to confirm the existence of such a bug. “Since the latest Windows 10 updates, KB4537572 and KB4535996, my computer is waking itself from sleep every couple of hours. Didn’t do this prior to updates,” a user noted on Twitter.

 

“This needs to be addressed. We should be able to prevent an optional update if it causes problems. No I have to either pause updates for 7 days and then uninstall KB4535996 again. This update causes both my laptop and desktop to not go into sleep mode,” a user wrote on Microsoft’s answer forum.

 

Users are also facing issues such as FPS drops, audio stutters, increased boot times or boot failures. Thankfully, the update is working fine for the majority of the people, meaning only a handful of people are facing problems. But that doesn’t mean these are not pressing issues.

 

Unfortunately, Microsoft hasn’t acknowledged these issues just yet, so there are no official fixes available at this moment. But what you can do is uninstall the latest optional update and that should make everything normal once again.

HOW TO UNINSTALL WINDOWS 10 KB4535996 UPDATE

1. Hit Windows+I to open the Settings app
2. Click the “Update & security” option.
3. On the “Update & security” screen.
4. Switch to the “Windows Update” tab.
5. Click the “View update history” option.
6. Click the “Uninstall updates” link.

via: Windowslatest

 

 

Source: Windows 10 KB4535996 update creates fresh trouble for users  (MSPoweruser)

[Karlston]

No, Microsoft hasn’t issued a “Windows 10 update warning”

Fool me once, shame on you. This time the shame’s on me.

 

I click through on clickbaity things from time to time, and I decided to see if the breathless report from one of the major online publications had picked up something that slipped under my radar.

 

Nope. I need to rap my own knuckles here.

 

Here’s the fact. The “optional,  non-security, C/D Week” patch for Win10 version 1903 and 1909, KB 4535996, has a bunch of problems. Mayank Parmar first wrote about them on March 5 in Windows Latest. Lawrence Abrams repeated that list and added a few more the next day in BleepingComputer.

 

We’re seeing a handful of common installation bugs:

• The patch won’t install, or rolls back
• There are blue screens or black screens after installation
• Complaints of slowness from various sources

We’re also seeing one novel problem, first reported (to the best of my knowledge) by Rafael Rivera. The tool used by Visual Studio to self-sign code, signtool.exe, triggers “Failed to sign” errors after installing the update:

If you’re having trouble with signtool.exe, check if you have KB4535996 (optional 2020-02 CU) installed. Looks like WTLogConfigCiScriptEvent got removed from wldp.dll without sufficient testing.

Microsoft has listened to Rivera (for a change!) and a Visual Studio community post from a Microsoft engineer now says:

We’re aware of issues with signtool.exe after installing the latest optional update for Windows 10, version 1903 or Windows 10, version 1909 (KB4535996). If you are encountering issues or receiving errors related to signtool.exe, you can uninstall the optional update KB4535996. We are working on a resolution and estimate a solution will be available in mid-March.

Of course, neither the Knowledge Base article nor the official Windows Release Information page say squat.

 

I haven’t talked much about these bugs here because I rarely talk about bugs in beta software — and, make no mistake, the monthly “optional, non-security, C/D Week” patches are beta versions. Maybe even alpha, depending on your definitions. The changes in those patches graduate to full, living, breathing cumulative updates on the following Patch Tuesday.

 

Neither Susan nor I ever, ever, ever recommend that you install the monthly optional updates. There’s too much downside, and almost no upside. This is a case in point.

 

This month, though, things are a little different. With nearly all of Microsoft’s employees now working from home, it isn’t clear if all the known bugs (much less the unknown ones!) will get fixed in time for Tuesday. But I’ll have more about that tomorrow in Computerworld.

 

 

Source: No, Microsoft hasn’t issued a “Windows 10 update warning” (AskWoody - Woody Leonhard)