MSMG ToolKit

Emmm, the same experience which I had met. I can't install updates at first time if I use that.

In 2016, we can install updates if the update packages don't contain the components we removed. (Windows 10 LTSB 2016)

But today, Windows component store can be corrupted easily without using any third-party tools. Recently, I tried to fix my 1809 and 1903 images and 1903 succeed, but 1809 failed because the corruption of BITS component which causes the CBS can't download and fix the corrupted components from Microsoft Update server, lol.

Here is some inside news about Windows 10: Microsoft cooperates with its partners, want to reduce the failure of Windows update packages installation. mingkuang told me that the success rate of Windows 7 update installation is 70% and Windows 10 is 30% because Windows 10 uses the cumulative updates and more changes to the component store, more corruptions it can cause. Microsoft want mingkuang's company to help it improve that situation.

mingkuang shown me he can write a automatic tool to fix Windows component corruptions via download from Microsoft server directly, because my WIndows 10 version 1809 image corrupted in 2018 and call mingkuang for help, he changed the registry manually and fix it successfully, lol. But mingkuang never finish that today because he told me he is lazy, though I know he is busy.

There are more evidences can prove the guys which maintain Windows Componentization Platform or call it Windows Servicing Stack in Microsoft don't know its design. The Windows Vista day's Servicing Stack or call it CBS has many excellent features, but Windows 10's delta update which enabled defaultly because of the cumulative updates is too big to download uses something s**t instead of original excellent features, and cause us can't use ResetBase safely because today's update installation relies on old version of components. (Microsoft loves using rollback components in cumulative updates and installation of a Windows component is rollbacking before updating. You know what I mean, lol.)

Kenji Mouri

 

MS going to outsiders to fix their s**t

 

But we know most of us can only suffer with Windows.

macOS is more bugs because they use the similar way and less users to help them test.

Linux, emmm, I think there is more s**t in their package managers which manages the operating system components. Several years ago, I accidently removed the entire ubuntu via installing a package because I add the debian repo in APT. I am an old linux user because I use linux since 2008, and I use the Red Hat 9 derivative in that days, when I was in grade 4 in the primary school. Fortunately, I didn't use btrfs, and use the most stable file system implementation in linux called ext series instead. (One of my friends, the one of the authors of Ext3Fsd, the successor of ext2fsd, can't suffer with linux even he uses linux for seven years, flees to FreeBSD and uses ZFS happily.)

Kenji Mouri

 

I couldnt use Debian for a workstation, yet, but its good enough for web stuff. Debian live is very handy though.

 

Hey Guys, I have one question or better one Problem. When I click on Apply and Save and creating after that a Iso everything works fine. I can install my new created Windows and updating is also possible. But when I first click "cleaning" and then save and apply and create a Iso I will get some errors during the updating Process of Windows.
Is the option "cleaning" important?

 

Thanks for the fast respond
So, the best fix is no cleaning . Are there any other Programs for cleaning after tweaking, or isn't cleaning necessary?

 

What I can tell ya is, don't feel afraid to learn powershell. It's not as difficult as it may appear. I've not mastered it but with a positive mindset I was able to write more complex scripts with it than I ever could with cmd. The real issue is knowing the inner workings and components of the OS, which M$ seems to be intentionally or unintentionally making such difficult for one to meddle with.

I'd be more than pleased to see the troubles we face as a driving force for Linux to overtake M$ in the desktop side of things.

 

hasnt happened wont happen, too many people pulling in too many directions, how many distro's?

i havnt come across a tweak i need that uses powershell so i dont need to learn it at the moment.

 

For technicians and developers it has happened at least for most but for casual users it is difficult for Linux to become a viable alternative. The status quo speaks louder. And even for those who prefer Linux it's hard not to use Windows while the vast majority of users keep using it.

 

if i get a laptop for interweb stuff im sticking debian live on it.

 

Yea, you can always cook up a new ISO and install it as an update overtop of your current setup if anything changes in the tool. It's pretty painless once you have your package list and registry imports how you want them.

 

Windows 10 Version 1903 (OS Build 18362.357)

Code:

2019-09 updates:

Adobe Flash KB 4516115
.NET KB 4514359
SSU KB 4515383
Cumulative KB 4522016

windows10.0-kb4516115-x64_1a640406e356d564d40121700fed9adc048b87e9.msu
windows10.0-kb4514359-x64_9c7a50db81b8b842e1f68eb69b386f0b3612823c.msu
windows10.0-kb4515383-x64_33a465dd17f198241e23e286ee7565c3c28b2f9d.msu
windows10.0-kb4522016-x64_c348c949121cdc6c4defacee70d6060ebb0d8442.msu

Version Hack:
Update install.wim to 18362.357, then set Build 18362.357 to Build 18362.1 and ToolKitHelper.exe will works just fine.
After using ToolKitHelper.exe set Build back to 18362.357.

 

How?

 

1. Mount install.wim
2. Select option 8 (Tools)
3. Select option 3 (Options)
4. Select option 4 (Load Image Registry)

The registry will be loaded in your system's registry, as follows:

Loading Image Registry...
[HKEY_LOCAL_MACHINE\TK_SOFTWARE] -> [HKEY_LOCAL_MACHINE\SOFTWARE]
[HKEY_LOCAL_MACHINE\TK_SOFTWARE\Classes] -> [HKEY_CLASSES_ROOT]
[HKEY_LOCAL_MACHINE\TK_SYSTEM] -> [HKEY_LOCAL_MACHINE\SYSTEM]
[HKEY_LOCAL_MACHINE\TK_NTUSER] -> [HKEY_CURRENT_USER]
[HKEY_LOCAL_MACHINE\TK_DEFAULT] -> [HKEY_USERS\.Default]
Loading Image Registry Complete...
===============================================================================
Press any key to continue . . .

You can access the image registry with regedit under CMD (execute as administrator)

We are interested in this: [HKEY_LOCAL_MACHINE\TK_SOFTWARE]

So follow the path: [HKEY_LOCAL_MACHINE\TK_SOFTWARE\Microsoft\Windows NT\CurrentVersion]

When you click on CurrentVersion, go to the right pane and scroll all the way down. You will see the key labelled UBR

Double click the key and change the number there to 01 or 1E. If you're on build 357, you'll see 165 (165 is hexadecimal for 357 in decimal)

After the change, repeat option 3 and select option 4 to unload the registry. Make all your changes on your wim file. Then repeat the entire process to change back to build 357. Save and unload wim.

This is how UBR looks like. I'm on build 356 (164 in hex)

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\TK_SOFTWARE\Microsoft\Windows NT\CurrentVersion]
"SystemRoot"="X:\\Windows"
"BaseBuildRevisionNumber"=dword:00000001
"BuildBranch"="19h1_release"
"BuildGUID"="ffffffff-ffff-ffff-ffff-ffffffffffff"
"BuildLab"="18362.19h1_release.190318-1202"
"BuildLabEx"="18362.1.amd64fre.19h1_release.190318-1202"
"CompositionEditionID"="EnterpriseN"
"CurrentBuild"="18362"
"CurrentBuildNumber"="18362"
"CurrentMajorVersionNumber"=dword:0000000a
"CurrentMinorVersionNumber"=dword:00000000
"CurrentType"="Multiprocessor Checked"
"CurrentVersion"="6.3"
"EditionID"="EnterpriseN"
"EditionSubManufacturer"=""
"EditionSubstring"=""
"EditionSubVersion"=""
"InstallationType"="Client"
"InstallDate"=dword:00000000
"ProductName"="Windows 10 Enterprise N"
"ReleaseId"="1903"
"SoftwareType"="System"
"UBR"=dword:00000164

 

@qommonsense Some mounted registry keys may be protected so i run them from Power Run incase.

 

These are not.

 

others are.

 

OMG!
This solves the main problem. I will try.
@MSMG