Octopuss

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?

Ah ok, I didn't have the update yet. I installed it, and the symbols failed to download. What should I do?

Nothing downloaded for me. Is it supposed to start automatically, with command prompt window and stuff?

Is it normal that the program takes up to ten seconds to start? If yes, what is it doing that it takes so long?

What do you mean by color of an active window? Do you mean the thin border around? And about all the sliders though? Color balance? What does that do?

I'm trying to integrate the last cumulative update to my image, and it just wouldn't work, always giving me this error: Processing 1 of 1 - d:\install\OS\Win10 updates\windows10.0-kb4346783-x64.msu: An error occurred while expanding the .msu package into the temporary folder, C:\TEMP\026C4C10-7AE8-42D3-9B97-9E49018383DF. Error: 0x8007000d Error: 13 The data is invalid. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log DISM log is equally useless 2018-08-31 13:43:48, Info DPX ProvideRequestedDataByFile: d:\install\OS\Win10 updates\windows10.0-kb4346783-x64.msu failed, Response file Name: ExtractFromCabInFile 2018-08-31 13:43:48, Info DPX Ended DPX phase: Apply Deltas Provided In File 2018-08-31 13:43:48, Info DPX DpxException hr=0x8007000d code=0x020201 2018-08-31 13:43:48, Info DPX Ended DPX phase: Resume and Download Job 2018-08-31 13:43:48, Info DPX DpxException hr=0x8007000d code=0x020217 2018-08-31 13:43:48, Error DISM DISM Package Manager: PID=1108 TID=4220 Failed to start the DPX job to extract MSU files. - CMsuPackage::Expand(hr:0x8007000d) 2018-08-31 13:43:48, Error DISM DISM Package Manager: PID=1108 TID=4220 Failed to expand the MSU file into temp folder C:\TEMP\026C4C10-7AE8-42D3-9B97-9E49018383DF. - CMsuPackage::Install(hr:0x8007000d) Are there any other updates I need to integrate first, or what's going on? Does anyone know?