Bork Tuesday, Any Problems Yet?

For what it's worth...
I encountered the DCOM 10016 error (component permissions) that relate to Windows Security Center. It appears 2 mins after each reboot as the Security Center service is set to autostart with a delay, while the component Windows.SecurityCenter.SecurityAppBroker tries to start very early in the boot process and because Security Center is not yet there it errors.
Setting the service to start without a delay fixes this.

[EDIT] I'm posting this as I encountered the same errors on 2nd of October (this one and the 1534 I posted earlier). All for 1809.

 

Yes ... I still had build 17134.165. Now it is at least the newest until 1809: 17134.407

 

I was there yesterday. Looks Ok.

I noticed that as well.
But I noticed another thing - am I right that the system partition is a bit shrinked by the update?
I am unable to restore a partition with Drive Snapshot. I had to do a complete disk restore.

 

Osaban,

I downloaded the ISO as we have multiple computers that haven't been updated to 1809. I used the ISO on my computer just as an experiment. Gaining 1 GB of Free Space in my main OS made it worthwhile.

 

Seer,

I noticed my Windows partition (UEFI system) had been resized 831 MiB smaller and a 831 MiB Recovery partition had been created after the Win10 partition. The old Recovery partition, 550 MiB, at the start of the drive was no longer in use. However, if the old Recovery partition was deleted then Win10 wouldn't load. It froze on the circle of dots. Undeleting the partition allowed Win10 to load. Even more interesting was if a blank partition (no files) was created in the 550 MiB space (after deleting the partition) then Win10 loaded. We are still working on this.

In my MBR computer a new 834 MiB Recovery partition was created at the expense of the Win10 partition size.

 

Yes, 1 GB on my MBR computer and 0.5 GB on my UEFI computer. These 6 monthly upgrades always give me increased Free Space after Disk Cleanup.

 

Thank you Brian for confirming.
I was not taking notice of exact sizes, but it is shrinked around 500MB here.
Not a concern, just a curiosity as I did not notice that when 1809 was initially released.

[EDIT] Here's the error log -

 

Lol, u guys using 8 gb hard drives or what? You're like sherlock holmes analyzing how many megabytes u saved

 

I have 6 Windows OS on that GPT disk so saving disk space is a bonus.

 

Why do u have 6 Windows OSes?

 

It's a test computer.

 

What do you test on it?

 

Multi-booting Windows and Linux OS. There are 17 partitions in total.

 

It's not about available MBs.
Saving space means smaller images and faster restores.
Different people have different perspectives.

 

And if it's an SSD faster speed

 

I also regained about 1 GB (on my 60 GB SSD).

 

Woody will be happy to hear that you installed already.

 

Regarding Windows 10, how Microsoft uses its consumers, Woody Leonhard says he tends to think of users as 'cannon fodder'.
But I am not Woody, and I certainly do not use Windows 10 (and I never will), and I image - of course. In case anything should go wrong, I can simply restore the previous image. I remember only one case in over more than ten years that I needed to, because of some update related glitch.

 

This is exactly what I have always done with Win 7.... install every important update the day they come out, and if there's a problem, roll back to my previous month's image. And likewise, I've almost never had to do that.

What you don't see Woody doing (and what he really should do) is tell people to image their setups right before Patch Tuesday, as we have done all these years, and their problems are over. Instead, Woody seems busy selling his stories and Patch Tuesday horrors. But the simple truth is, there is a very simple and easy solution to this problem. Imaging.... and it's not beyond the reach of the average Joe user either...

 

https://support.microsoft.com/en-us...-drives-don-t-work-in-windows-10-version-1809

 

It depends on the type of computer and method of restoring. Creating a new image is easy, restoring it is a bit more complex. With my old laptop (MBR type), it was easy, once the boot sequence was set to boot from CD it was a matter of a few clicks.

With my two relatively new laptops (GPT type) I have to change the boot sequence every time I restore an image by entering the BIOS and reset it afterwards to boot from hard drive... Perhaps there is an easier way, but what I described would be pretty daunting for the average Joe.

 

Yeah, it might be a bit of a stretch for average Joe, granted. A lot, perhaps even most, of the users aren't even aware of such things. Good point.

 

https://www.askwoody.com/2018/malic...-kb-890830-throwing-weird-winxp-eula-prompts/

 

I just did a clean install of 1809 today and then let it do the November updates, and so far I see no problems/issues. I was even pleasantly surprised to see that they had fixed several crazy bugs in Edge since the original 1809 release. So I'm going to go with it and see how things go. So far, so good.

 

It looks like a bug in this month's Malicious Software Removal Tool, KB890830 for W7 32 bit per Woody.