Octopuss

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.

I am about 85% happy with 1803, but I'll be damned if I'll install 1809 sooner than in a few months after what they did since the original launch.

What do I need to backup in order to transfer settings to new Windows installation?

The opacity slider in "Glass color" doesn't do anything. What is it supposed to do? Similarly, I don't understand the "accent color". It doesn't do anything either. Oh and in the accent tab, the checkbox doesn't work. When I uncheck it and click save, it gets reverted to checked state.

No, I get lines over the desktop.

After several weeks to a few months after finally deciding to bite the bullet and installing v1803, I can say I got used to it. Even the lack of pure Win7 Aero (couldn't find any suitable AeroGlass theme I'd like). I don't see any performance improvement, but it seems more stable. Some minor annoyances I disliked on Win7 are fixed here. I guess it's ok.

The integration is basically dism /Mount-image /ImageFile:"<path>\install.wim" /index:<number> /MountDir:"<where to mount>" /Optimize /CheckIntegrity dism /image:c:\mount /add-package /packagepath:"<path to the folder with the servicing update" dism /Unmount-image /MountDir:"<path>" /Commit /CheckIntegrity And then again the same thing, only you have to specify different folder where the actual CU is (not sure if you can point to specific files, probably yes, but I prefer not to edit the d*** batch file over and over).

That's partially why I couldn't figure it out! The servicing stack updates are sometimes mentioned at the bottom of the cumulative updates' page, like here. There doesn't seem to be any kind of centralized info/download page for the servicing updates.

In case anyone ever runs into the same problem: I managed to figure it out - purely accidentally. It turned out there IS a prerequisite to integrating this - it's called "servicing stack" and these KBs are released more or less along with the cumulative updates (sometimes like once per two CUs). Of course, this is not explained anywhere (the connection and dependency). The other catch is that when you try to integrate all this, you have to do it twice. WTF. So you have to mount the image, do whatever customizations you have prepared, then integrate the servicing stack, THEN unmount and save the image, AND THEN mount it again and finally integrate the large update. This is almost as annoying as booting into safe mode in Windows 10 compared to Windows 7. just-pure-WTF

Does anyone have Win7-ish atlas for version 1803, and with reduced borders ideally? Everything I've seen in the forum thus far either doesn't work or looks bad.

Noone? Really? Noone does custom images in W10 anymore?