Octopuss

What do you mean one minor update?

Update: The updates kept failing because I uninstalled (and blocked from reinstalling) Edge. Yes. What the F***!!! Microsoft will never change.

@Tihiy, could you post these changelogs on the website as well please? I don't go here anymore and check the website mostly, but there are barely any changes mentioned.

It seems like it isn't. https://docs.microsoft.com/en-us/windows-hardware/customize/desktop/unattend/microsoft-windows-setup-diskconfiguration-disk-createpartitions-createpartition-type and https://docs.microsoft.com/en-us/windows-hardware/customize/desktop/unattend/microsoft-windows-setup-diskconfiguration-disk-modifypartitions-modifypartition-typeid

I have just tried this in a VM and sure enough, once that partition existed, the CU installed just fine. If it's not present, it fails during reboot after seemingly successful installation. This started some time a few months ago, basically in the 2nd half of last year I guess. I have the usual GPT setup with 100MB EFI, 128MB MSR, and the actual Win partition. I have been doing this for years and it only started to give me problems with this thing. Oh and btw, installing a CU manually works just fine even without the partition. That's kinda bizarre. Something must have changed somewhere but... meh.

It wasn't until yesterday that I realized the cumulative updates keep failing to install because - judging by some random google results when I googled the 0x800F0922 or 0xc1900104 error - there's no reserved partition, you know, that 500MB thing, on my system. I have my unattended installation that I've been using since Windows 7 and it always worked just fine. I started seeing CUs fail to update some time during last year and always thought it was because my system got somehow was broken after over two years of torturing it. Does anyone know when has that partition became a requirement? I don't understand it anyway, what does the partition do for the updates? Interestingly, manually installing the CUs work fine,.

Hmm. All this registry stuff is confusing as hell, but I thought ntuser.dat is HKEY_CURRENT_USER according to https://docs.microsoft.com/en-us/windows/win32/sysinfo/registry-hives Also I am working with a mounted Win image where the paths are different. ntuser.dat is at <mountdir>\Users\Default\NTUSER.DAT, so I really am utterly lost.

I found one regtweak that, bizarrely, resides in [HKEY_USERS\S-1-5-20\Software\Microsoft\Windows\CurrentVersion\DeliveryOptimization\Settings], but I ran into a dead end when I thought I'd integrate it into the image just like the rest, because these SIDs are not present in the registry by default. There are none under HKLM\WIM_Users when I mount the image and import the registry. Is there any way to do this or do I have to do it post-installation?

This crap is killing me. I am installing a new notebook for my mother in law, and this garbage even somehow managed to install MsOffice onto the machine. I googled it up and while I did manage to find a way to do this (executing c:\Program Files (x86)\Microsoft\Edge\Application\<version number>\Installer\setup.exe -uninstall -system-level -verbose-logging -force-uninstall), it seems like the thing is reinstalled with each cumulative update. Powershell flat out refuses to do anything since it's part of the OS. There is also a folder in \Window\systemapps which some sources suggest to rename, but that didn't work either. I tried changing ownership and permissions of that folder but I don't think that will do anything. Does anyone know about a way of getting rid of this abomination? (and I thought the original Edge was bad - at least it didn't do anything)

https://docs.microsoft.com/en-us/windows-hardware/customize/desktop/unattend/ This document looks suspiciously empty to me. There's no chance nothing changed in this part of Windows customization in two years... Does anyone know anything more? Or is this document outdated? I can't google anything better up.

I have assorted registry tweaks I apply to my images. It has always worked for me since Windows 7. I've been testing something today after a long time, and after a few hours of trying to figure out WTF was going on, I came to the conclusion this part of the customization didn't work at all. Basically what I do is this: 1) mount the image 2) load the registry files from the image 3) apply some tweaks 4) unload registry 5) save and unmount the image When I mount the image back, the changed/added registry keys and values are there, so this part is correct. I know there are certain values that cannot be changed in this way and are always default after installation, however in this particular case, when I install the image, absloutely everything is as default as can be. Does anyone have any idea what might be going on? I am testing my images in Virtualbox, and thinking it could have been something in the last version of Windows, I went back to version 1903, but it doesn't work either (and I did install my PC with this some time ago), so that can't be the problem. I am out of ideas. edit: solved, user oversight, please delete

Pin to start doesn't work when done from within Total Commander. I think I reported this long time ago but nothing happened. I have no idea where the underlaying problem is, but I know it did work at some point in past. Long time ago, I don't know. edit: It seems like the SIB++'s own pin to start isn't recognized by TC.

I really regret not buying a notebook with Pro version instead. Lesson learned for future.

I googled a workaround up - you can defer upgrades even on Home edition if you set connection type to metered. Going to give it a try on another machine.

I've been mostly happy with Windows 10. Until today. My wife's notebook that runs Home edition was sneakily upgraded to version 1809 at some point, and I've just realized most/all registry tweaks in the customized image I created are GONE. I had an extremely handy extra options in the context menu of This PC and it's empty. Now I'm p***ed. A lot. A LOT.