Windows 10: Oh look, another broken Windows update! KB4493472 and KB4493446 causing issues

Reports are coming in left and right that the recent security updates for Windows 7, Windows 8.1, Windows Server 2008 R2 and Windows Server 2012 R2 are causing issues on machines they are installed on under certain circumstances.

I added a note to the Tuesday's Patch Overview for this month's Windows updates but the issue appears even more widespread than thought initially.

What we know so far



The issue affects pre-Windows 10 operating systems only, at least that is what is been reported at the time. In other words: Windows 7, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

The updates that may cause issues are:

• KB4493448 Security-only update for Windows 7 SP1 and Windows Server 2008 R2 SP1
• KB4493472 Monthly rollup update for Windows 7 SP1 and Windows Server 2008 R2 SP1
• KB4493467 Security-only update for Windows 8.1 and Windows Server 2012 R2
• KB4493446 Monthly rollup update for Windows 8.1 and Windows Server 2012 R2
• KB4493450 Security-only update for Windows Server 2012
• KB4493451 Monthly rollup update for Windows Server 2012

The issue

Sophos reports that machines with the update may fail to boot. The computer mentions systems with Sophos Central Endpoint and SEC installed specifically and recommends not to install the new update at this point in time.

If the update is installed already, Sophos recommends booting into Safe Mode, disabling Sophos Antivirus, booting into the regular system, uninstalling the Windows update there, and enabling the Sophos Anti-Virus service afterward.

Avast published a support article on the company's KB site that describes a similar issue. The company reports that PCs running Avast for Business and Avast Cloud Care on Windows machines may become locked or frozen on start after installing the new Windows updates.

Windows machines (particularly those running Windows 7) are becoming locked or frozen on startup after Microsoft updates KB4493472, KB4493448, and KB4493435.

Some of these machines are completely unable to log in, and some log in after a very extended period of time.
​

Avast suggests that users roll back the update as well and has published instructions on how to do so on the linked support page.

Microsoft has yet to acknowledge the issue; no support article lists the problem as a known issue yet.

It is still recommended to create a system backup before you install any new update for Windows on your machines.

Now You: are you affected by issues after installing these updates? (via Ask Woody)

Ghacks needs you. You can find out how to support us here or support the site directly by becoming a Patreon. Thank you for being a Ghacks reader. The post Oh look, another broken Windows update! KB4493472 and KB4493446 causing issues appeared first on gHacks Technology News.

read more...

 

Re: Windows 10 update

Hi,

The black screen error may occur if there are broken system files or applications causing software conflicts. To isolate this issue, please answer the following questions:

• When did the issue start?
• Were there any changes made to your computer prior to the issue?
• What troubleshooting steps have you done so far?

In the meantime, we suggest that you follow the troubleshooting steps found on this

article to resolve this issue.

We're looking forward to your response.

 

Windows update issues

Came here to suggest this.*Laugh :laugh:

Definitely not an issue with the Windows Servers as I just re-installed yesterday and got all my updates.

 

Windows Updates failed to instal

I'm not sure how differant XP media center Edition is but you could clear the history \ cache if these folders are there.

Step 1 Register DLL files.

=================

By trying this step, we can check if the update engines are working properly.



1. Close all instances of Internet Explorer.

2. Click Start and Run, type "Regsvr32 atl.dll" (without quotes) in the Open box and click OK.



Note: There is a space between regsvr32 and atl.dll



3. Similarly, one by one, register the files listed below:



Regsvr32 msxml3.dll

Regsvr32 wuapi.dll

Regsvr32 wuaueng.dll

Regsvr32 wuaueng1.dll

Regsvr32 wups2.dll

Regsvr32 wucltui.dll

Regsvr32 wups.dll

Regsvr32 wuweb.dll

Regsvr32 qmgr.dll

Regsvr32 qmgrprxy.dll

Regsvr32 jscript.dll



Note: If you encounter errors while registering any of these files then skip that file and continue with the next one.



If the issue persists, let's move on to the steps below to verify Windows Update services and temporary folders.



Step 2 Verify the relevant Windows Update services.

=========================================

1. Click Start->Run, type "services.msc" (without quotation marks) in the open box and click OK.

2. Double click the service "Automatic Updates".

3. Click on the Log On tab, please ensure the option "Local System account" is selected and the option "Allow service to interact with desktop" is unchecked.

4. Check if this service has been enabled on the listed Hardware Profile. If not, please click the Enable button to enable it.

5. Click on the tab "General "; make sure the "Startup Type" is "Automatic" or "Manual". Then please click the button "Stop" under "Service Status" to stop the service.

6. Then please click the button "Start" under "Service Status" to start the service.

7. Please repeat the above steps with the other services:



Background Intelligent Transfer Service

Event Log

Remote Procedure Call (RPC)



Note: Event log service is enabled on all of the hardware profiles; this service does not have an option to enable or disable on certain hardware profile.



If it still does not help, let's proceed to step 3.



Step 3 Reload the Update temporary folders.

===================================

One possible cause is that the temporary folder for Windows Update is containing corrupted files. Let's erase all the files there to get the system clean.



1. Click Start, Run, type: cmd and press Enter. Please run the following command in the opened window.



Net stop WuAuServ



2. Click Start, Run, type: %windir% and press Enter.

3. In the opened folder, rename the folder SoftwareDistribution to Sdold.

4. Click Start, Run, type: cmd and press Enter. Please run the following command in the opened window.



Net start WuAuServ



Please test the Windows Update website and let me know the result. If the issue persists, to clarify the issue and provide more accurate troubleshooting steps, please assist me in collecting the following information.