Bork Tuesday, Any Problems Yet?

Maybe MS is sending out the update with the OS patch without the AV reg key here. If i install the jan rollup 6894 without the reg key, then i don't think WSA would be compatible with OS patch.

 

In my opinion, since you got it via WU, you should be fine. FWIW, for January in W7, I installed the other package (KB4056897), did not get it via WU. WU would not offer it to me, I downloaded it from the catalogue. All has been well with that computer (No AV, No reg key).

Bo

 

See Windows Update Catalog (Package Details Tab)

This update replaces the following updates:
.
.
.
2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4056892)
2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4073290)

 

Not when I query the Windows Update Catalog:

 

I think you overlooked the up/down arrows to the right.
If you use the down arrow to scroll down, you will see KB4056892 and KB4073290 that Adric mentioned.

 

Yes. Forgot to do that. Also appears to be only applicable to:

 

I've never seen a motherboard BIOS update from Microsoft WU. Driver updates yes (which btw has screwed up my W10 system twice as they are installing automatically which does not work well if you are using AppGuard). What type of system did this happen on? Maybe a Surface system?

 

Yes, possibly... I didn't think of that.

 

Yep, I am at .214 and current. So no problems really....

 

It was on an HP laptop with W7. I found the update among many in the list of non important or not required updates that had been released a lot earlier. I said Why not, but it turned out to be a bad idea.

About driver updates in W10. I know I experienced at least a couple of them in the 7 months I had the new system. They were done silently, finding out about them a day or two after they taken place. No issue, but I can see how using a program like AppGuard can cause problems with this type of silent updates.

Bo

 

We have similar configurations (W7-SP1x64 & WSA9.0.19.43). Fwiw, when I was offered that KB a few days ago (via Windows Updates) I installed it and so far all is well.

 

It looks like WSA reset my app yesterday, so when i had to enter my lic code again i went from v44 back to a reworked v43 that must have had the m and s reg key in it because now i get ms updates again.

 

Seems like MS & Webroot aren't quite sure what's up!

 

These updates are cumulative. The point is KB4058258 is the latest cumulative update and it supersedes the previous one. I.e KB4073290 supersedes KB4056892 and KB4058258 supersedes KB4073290.

 

That's interesting. There are installers that run cmd.exe, which also happens to be on the Guarded apps list. Potentially, those installations could fail, too.
I know I am replying to an old post, but the main point still applies.

 

Hold your breath, avoid the snake oil, and get Windows updated
https://www.computerworld.com/artic...id-the-snake-oil-and-get-windows-updated.html

​

 

Great article, Thanks.

 

I had no issues with January updates and will continue to let Windows 10 download updates when it decides to.

The only issue I have with Windows Update, is that for the last year or two it has kept finding a Visual Studio Service Pack 1 Update for Vista. I hide the update, but before long it returns. Windows is unable to install the update, perhaps because I'm running Windows 10 and not Vista.

 

Update kb4058258 for Windows 10 x64 RS3 failed, due to Sandboxie 5.23.3.0.
After uninstalling SBIE, the update installed successfully through the regular Windows update mechanism.

 

Besides SBIE, I was also running Emsisoft, Appguard, and OSArmor. Yeah, I know, that's a lot of code running all at the same time. When I removed SBIE, but left the others, the update finally succeeded.
So I would attribute the repeated failures to some kind of interaction between SBIE and my other security softs.

 

It failed 8 times, with several reboots in between, so that's a pretty good indicator of a problem, I think.
I suspect that OSArmor + SBIE was the culprit combination. I have seen OSArmor get into fights with a couple other security softs, so I would't be surprised if it combines poorly with SBIE as well.

 

I have the KB4074598 (Monthly Rollup) for W7. I will wait a few days to see what happens before i install it. Also got another .net to install this month.