[German]As of December 10, 2019, Microsoft has released a collection of security updates for its products. The article includes a Patchday review that provides information about issues related to updates.
Advertising
Issues with Windows 7 Updates
The updates KB4530734 (Monthly Rollup Update) and KB4530692 (Security only Update) showed at least an unusual behavior on Windows 7 clients.
Very long installation time under Windows 7
In the German article Patchday: Updates für Windows 7/8.1/Server (10. Dez. 2019) several blog readers reported (and here) a very long installation time of the Windows 7 updates. One user wrote:
For me, the update just paralyzed the PC completely. Since one hour "Updates are being configured". And that with i5 processor, 8 GB RAM and 500 GB SSD. So far – at least in the last years – the Win7-update was always a matter of a few minutes and the hours of downtime for updates I know only from my Win10 computer. Should this "adaptation" of Win7 make me migrate my favorite PC (so far) to Win10?
In the comments readers point out that the update installation takes an unusually long time (especially when configuring the updates).
If the machine does not come out of the update configuration loop, use my tip from this article and boot into safe mode via F8. Have the updates installed there.
KB4530734 ends with black screen
t reddit.com there is this thread, in which a user complains a black screen after installing the monthly rollup update KB4530734. The problem is confirmed by some users.
Installing this month's Win7 Servicing Stack Update KB 4523206 may lock up your PC. Only known fix at this point is to revert to backup. (You can't uninstall a SSU.) Tell me again how MS patches are getting better? https://t.co/ebbQcourES
— Woody Leonhard (@AskWoody) December 12, 2019
Advertising
It is suspected that uninstalled Servicing Stack Update (SSU) KB4523206 is responsible for this boot problem. Woody Leonhard has posted a corresponding article (see also tweet above).
Trouble with TrueCrypt
In connection with TrueCrypt (it's outdated anyway) there seems to be boot problems with encrypted drives, as I read here.
Install issues with Windows Server
I have received feedback on Windows Server 2008 R2 boot problems as well as Windows Server 2012.
Windows Server 2008 R2 boot issues
The comment here about Windows 7/Server 2008/R2-Updates KB4530734 (Monthly Rollup Update) and KB4530692 (Security only Update) describes boot issues. In a VM, Windows Server 2008 R2 goes to the Recovery Console and no longer starts. The host is VMware. And this comment mentions that Windows Server 2008 R2 ran into problems after the update was installed.
This patch caused our Server 2008R2 server to have problems – RDP connection failed, DFS Namespace server would not start – the dependant Server service did not start.
Removed the patch and all is working again.
Could be an isolated case, though. In addition, it was not specified which update caused the error.
Windows Server 2012 boot loop
f Windows Server 2012 falls into a boot loop during the installation of the December 2019 updates, the .NET Framework update KB4533096 could be the cause, as Woody Leonhard suggests in the following tweet.
Is your Windows Server 2012 (not R2) in a boot loop? Blame this month's .NET patch, KB 4533096. Boot into Safe Mode and you'll be able to bring the server back. https://t.co/kaEEjOZEgy
— Woody Leonhard (@AskWoody) December 12, 2019
Here, too, it helps to boot Windows Server 2012 in safe mode. Then the installation should be finished.
Windows 10: Problem with Drive Mapping
Woody Leonhard points out a problem with drive mapping (sharing of network drives) in connection with the cumulative update KB4530684 for Windows 10 Version 1903/1909:
Reported problem with Drive Mappings after installing this month's Win10 1909 cumulative update, KB 4530684. Looks like it knocks out AD management. Only identified solution is to roll back the patch. Can you confirm? https://t.co/zHMKLXe9Hv
— Woody Leonhard (@AskWoody) December 12, 2019
After installing the update, the network drives had disappeared and the AD management tools could no longer find the domain. A rollback of the update fixed the problem. But it seems to have been an isolated case.
Office 365 Updates pulled
I didn't discuss the updates for Office 365 here in the blog. However, the Microsoft Update Catalog contains certain updates. In Bleeping, this post reported that Office 365 updates have been withdrawn. Reason: The updates caused the error 0x800b0004 (a certificate error TRUST_E_SUBJECT_NOT_TRUSTED) when distributing via SCCM.
Similar articles:
Microsoft Office Patchday (December 3, 2019)
Microsoft Security Update Summary (December 10, 2019)
Patchday: Updates for Windows 7/8.1/Server (Dec. 10, 2019)
Patchday Windows 10-Updates (December 10, 2019)
Patchday Microsoft Office Updates (December 10, 2019)
The US and UK being so publicly supportive of Internet Freedom in rhetoric, yet so thoroughly undermining it in action represents a key impediment to worldwide Internet Freedom. If the leading international states are unwilling to forward Internet Freedom in any more than phrase, how can others be expected to in deed? The present-day machine of Internet governance in trendy offers an enormously antagonistic environment inside which to foster Internet Freedom. The power of big corporations and organizations is huge and the have an impact on they have is equal to their energy. Both of these factors further obstruct the proliferation of Internet Freedom in a way this is currently being decided inside the courts of America. It isn't always the undemocratic states that appear to pose the biggest danger to Internet Freedom, however the very states that should be shielding it.
KB4530684 makes Windows 10 noticeably slower as quite a lot of people have noticed. My Toshiba Satellite Pro P200 laptop really suffers as does its user.
How could such a performance hit have got past Microsoft's testers?
Many thanks for your excellent and relevant commentaries on Windows and technology issues. You web pages are always my first port of call and are most valuable to my computer activities.
This issue occurs at every startup/restart. Some sort of diagnostics seems to be running and the procedure eventually completes. Older systems take longer to complete the procedure. My 13 years-old Toshiba Satellite Pro P200 laptop (fabulous display screen) takes upwards of 20 minutes to complete it and is very sluggish for that time (normally surprisingly quick for such ancient hardware). Up-to-date systems complete much more quickly so maybe this is why the issue has gone undetected by Microsoft.
Another 'bright' idea gone wrong?
We had a few windows2008 servers reboot after installing KB4530692 this weekend and would not boot.
Error: recent hardware[…]signed incorrectly or damaged[…] \
file: \windows\system32\winload.exe
status 0xc000428
info: windows cannot verify the digital signature for this file.
Had to restore each VM from a backup previous to this update