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.
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.
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
I have already advised not to use this method since the ToolKitHelper will not completely remove the changes made by the CU. Use it at own your risk and there won't be any support for it.
MSMG: you sure mapcontrol is all thats needed for maps? nothing else? maps still autoclosing for me, am trying to figure out what it is
Thank you guys I will try it! Never before has this issue. It started to show up with 9.4.x and above! I will come back and reply after I try from C drive. Thanks again. I always use Start.cmd sometimes as admin sometimes not! I know it is not necessary to run as admin...
@Feartamixg, @scaramonga Unfortunately, error 183 is still there after removing the folder to C:\MSMG Toolkit... Can anyone help me how to solve the error 183 situations?
I know that. I do not have a space in name/path I just want to emphasize that I copied MSMG Toolkit folder to C:\drive