Issues with Microsoft’s November 2017 Updates

[German]On November 14, 2017 Microsoft ‘celebrated’ Patchday and released a bunch of updates. Some seems to be ‘problem bears’, the Malicious Software Removal Tool (MSRT) for instance. Here is an overview, what I’ve seen so far.

Update KB890830, released November 14, 2017 has some flaws. I received this German comment, where a user reported error code 0x8024001e. Also here are further comments with issues. Error 0x8024001E stands for WU_E_SERVICE_STOP (Operation did not complete because the service or system was being shut down). In normal cases I would blame third party antivirus products. But it seems, that Microsoft failed again with update KB890830.

Also here is a comment – reporting that MSRT install hangs for an hour at 0 %. Another user reported, that MSRT detected 29337 folders with malicious content. And here a user found in update history, that KB890830 hasn’t been installed.

Advertising

I recognized, that MSRT has been offered in Windows 7 Update als Important, but the checkbox was unchecked. Some reader told me, that the checkbox was previously checked, but changed to unchecked during the day. Did MS become aware of issues?

I assume that a wrong code branch was used to build the update, which now causes the trouble. My advice: Hides KB890830 in the updates. Under Windows 10 you can download the instructions from the blog post How to block Windows 10 updates.

Windows Update error 0x8024a11a

Within this thread a user reported, that several of his Windows 10 systems hangs during first reboot. He received error 0x8024a11a and was forced to manually restart the machines again.

This list doesn’t cover this error code, but the group this code belongs to, indicates an AU error. Maybe a driver is causing this issue. A clean boot (see here) could solve this issue (see also my blog post Windows 10: Update error 0x8024a112).

HP 3D Drive Guard software is installed on many HP systems. The Drive Guard protects the hard disk of the computer (only applies to notebooks). This monitors the acceleration of the device for values, which can be dangerous for the hard disks, and move the hard disk heads into a parked position, if necessary.

It broke every visual in the desktop file. Interestingly enough, when I published the file with the broken visuals to the service it worked perfectly in the service. I then saved the broken file and reopened it and my visuals started working again.

Update Error 0x800705b4

And here is a comment, reporting, that November patchday is causing trouble on Windows Server 2016, which drops an update error 0x800705b4.

Windows -Update blocks dot matrix printer

Just an addendum – thx to a German blog reader: At tenforums.com is a thread with title Dot Matrix Printer Stopped Working After Update. A user wrote:

And bunch of other Microsoft Office update. But I think one of these update is the main culprit of my problem.
Today, my dot matrix printer Epson LX-310 can’t print any work document. Switching to other non dot-matrix printer will print without any problem. Tried with POS printer and inkjet printer.

I tried with my other work computer which got updated too, and this problem persists. First I think my LX-310 is faulty, but after testing with my Epson LX-300, same problem happened. When I tried with a laptop runs Win10 that didn’t upgraded yet, it prints without any problem.
The document will sit in queue, and then dissappear, indicating that it has finished printing. But printer doesn’t move. Connection using USB. My PC didn’t have print port.

The initial post deals with Windows 10, but also other Windows versions are affected. Within the thread linked above, other user reported, that they are affected with more than 40 systems and are unable to print invoices. One user blame update KB4048953 for this issue, after uninstalling, the printer works again.

At Technet is this forum thread, where the issue has been reported for Windows Server 2012 R2 and an EPSON LQ690 printer. There update KB4048957 is blamed for the issue. Overall I found the following updates causing this issue so far:

KB4048953 for Windows 10 Version 1607

KB4048958 for Windows 8.1

KB4048957 for Windows 7/Windows Server 2012 R2

KB4048960 for Windows 7

One German user reported, that also Windows 7 (KB4048960) is affected. The affected printers are from Epson (LX-310, LX-300, LQ2180, EPSON LQ690 and LQ2190, and probably more). One user tried a network redirection to a system which don’t have the update to force printing:

net use LPT2 \\pc\printer

Within this post somebody wrote, that Microsoft released another update for Windows 10 that fixes this issue – but I can’t test it. Addendum: Microsoft released some updates that fixes the issue – see articles linked below.

Also found that Epson LQ-590 printer quit working after Microsoft updates circa 11/15/2017. Is connected to port USB0001, other printer (HP LJ 4350) connected to another USB port works fine.
Did a system restore to a date prior to update and can now print. Changed update settings to download but ask before updating but it still updated and knocked out the printer again. A System Restore to a prior date corrected again. The problem update appears to be a USB driver update.
Has anybody started a class action lawsuit against MS because of these debacles?

I would like to join one if they have. In the last 2 years, I have lost several business days (and several customers) because of my expensive computer equipment not being usable – due to both Windows 10 policy and failures due to bugs. I also lost a very expensive custom built program, when Microsoft decided that it didn’t like the look of it. Meantime they keep pushing out ‘new’ features (that hardly anybody has expressed an interest or need in) without bothering to fix some of the most critical issues. They talk about Win 10 being the most modern, secure operating system, but some of its kernel was written in 2006… and regards security, I am now a lot more scared of what Microsoft will screw up on my machine than I ever have been about hackers. It’s getting to the stage where I’d rather go back and run an (allegedly) insecure OS than put myself through more of the frustration of dealing with a ‘modern’ and ‘secure’ OS. Microsoft have screwed up about 30 business days of mine in the last 2 years. Hackers have screwed up 0 business days of mine in the last 2 years. Who should I be more afraid of?
Anyway, I’m ranting…sorry… I completely agree with you…and want to be part of any legal undertaking against this arrogant company and its shabby products and abhorrent practices.

FYI, This issue is also knocking out the LPT port printers.
My client uses Epson FX890 and since the updates have not been able to print invoices. A massive problem. After selling them a new printer, I now have huge egg on my face, and my client no longer trusts me. Thanks Microsoft!!!

One of these November updates also breaks indexing in outlook when using G Suite. Not sure which one specifically. Only fix I found was a system restore before these updates.
Using Windows 7 64 bit and Outlook 2010 32 bit.

…there is a reason many or us remain on Win7 or even XP Pro SP3. There is also
good reason why I will NEVER upgrade to Win10…not ever. I simply cannot afford
Microsoft messing with my gear constantly…I have bills to pay…landlord likes to
get his rent to … 8)

I installed the cumulative KB4056892 update overnight on my desktop PC on the 24th January 2018 as it askd me to do. I run an Amd dual core, 8gb RAM blah blah my machine usually runs like a dream – 20+ years it exp. I turned my pc on in the morning and no boot. Windows logo and “couldn’t install windows” error. The error stopped windows automatically going to recovery mode after 2 attempts so I had to manually crash the pc twice to start recovery module. The auto update did not create a restore point so I had to reset the pc. At least I was able to keep my files. This process took up 5 hours of my time (well maybe 1 hour and 4 hours of waiting and watching lol). Ive now turned off updates as it tried to do it again……I’ve since learned this seems to be an AMD issue only so be careful peeps – If you aren’t careful and don’t know what your doing this could cost you some dollars to fix. Kinda agreeing with SSS NNN comment above – Never had these issues with Win7 or XP. Rant Over lol

I experience a similar behavior on a virtual machine with a test install of a plain Windows 10 V1709. After rebooting during installing the latest January 2018 cumulative updates, no more mouse clicks are detected. Tried to reboot the machine without success fixing this issue. So I switched off the VM twice, to force a Windows PE boot. Then I got a blue sceen with stop code 0xc0000017 (see my article here). It’s a mess.

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.