I recommend you to continue using: https://forums.mydigitallife.net/th...1803-1903-19h2-1909-20h1-and-ltsc-2019.80038/ and leave us here alone. Thank you for the kindness
Have you tried on another partition. Check how many Gb you have before starting the image servicing. It has to be about 30gb to be at the limit. But also, I suspect that you have to run a chkdsk c: /X /F or chkdsk c: /X /R /F
It is correct. I'm migrating from 19044 to 220000 and on to 22621. I'm confirming the integrity of my ISOs to perform an inplace update. And I think I'm going to start experiencing the problems that people are experiencing in w11. What ISO are you using? When you are doing the conversion do you close the File Explorer? I've had read/write problems simply from being open in the toolkit folder. Then the message appears that the file being serviced on is being used in another process.
19045.2311. My File Explorer is closed. Yes, but in both screenshots, I also get the message Failed to decompress data and The WIN contains invalid compressed data.
Well, I for one am certainly highly interested. Much of the stuff is too complicated for me too, but that just makes it more interesting. No one would accuse me of being "highly specialized" Don't always get answers to my questions, but I usually find a solution in the end.
invalid compressed data - may be caused by a read failure because it is being used in another process. It could also be due to data corruption. If you have already downloaded the ISO again, this possibility can be ruled out. Maybe Windows Defender up and running checking the files being worked on. When we forget anti-malware enabled... It's a disgrace. It's always a waste of time.
Yes, already downloaded the ISO again, so this possibility can be ruled out. My Windows Defender has been removed completely..!! I don't use third-party antivirus..!! I don't understand what's happen.
With that you've exhausted my assumptions. Any tweaks that might have broken something with regards to running scripts? There is a Protection Policy against executing PowerShell scripts, there is also one for Batch Scripts. I don't remember at the moment. There was a time that I disabled the Null service and the scripts were crap, I don't even know if they worked or not. I just remember that all the errors that occurred while running the Toolkit were displayed on the screen. It took me some time to find out which Tweak I had applied that gave this. Code: rem value 1 Default "Null" - Note: Disabling this Service causes CLI and Scripts issues reg.exe add "HKLM\TK_SYSTEM\ControlSet001\Services\Null" /v "Start" /t REG_DWORD /d "1" /f >nul 2>&1 I left the line of this tweak commented so I never forget it, hehehehe
WindowsDefender error. Code: 20348.1.210507-1500.FE_RELEASE_SERVERSTANDARD_OEMRET_X64FRE_EN-US.iso\install.wim Results: Microsoft Windows [Version 10.0.19041.1] (c) 2019 Microsoft Corporation. All rights reserved. C:\Program Files\PowerRun>C:\ToolKitHelper.exe D:\ WindowsDefender MSMG ToolKit Commandline Helper Version: 1.1.1404.0 Image Version: 10.0.20348.1 Component : WindowsDefender Removing Package files... Modifying Package files... Loading Image Registry... Modifying Package Registry... --------------------------- --------------------------- System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object. at (Object , String ) at .(Object , String , ) at ..(String , String ) at .(String , String , ) at ..(String , String ) at .(String , String , ) at ..Main(String[] args) --- End of inner exception stack trace --- at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at _._.___() --------------------------- OK ---------------------------
WindowsDefender error. Code: 20348.1.210507-1500.FE_RELEASE_SERVERSTANDARD_OEMRET_X64FRE_EN-US.iso\install.wim Microsoft Windows [Version 10.0.19041.1] (c) 2019 Microsoft Corporation. All rights reserved. C:\Program Files\PowerRun>C:\ToolKitHelper.exe D:\ WindowsDefender MSMG ToolKit Commandline Helper Version: 1.1.1296.0 Image Version: 10.0.20348.1 Component : WindowsDefender Removing Package files... Modifying Package files... Loading Image Registry... Modifying Package Registry... --------------------------- --------------------------- System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object. at (Object , String ) at .(Object , String , ) at ..(String , String ) at .(String , String , ) at ..(String , String ) at .(String , String , ) at ..Main(String[] args) --- End of inner exception stack trace --- at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at _._.___() --------------------------- OK ---------------------------
Man, the Path is long. You have to run all commands as admin. You have to learn how to mount a wim image. * forum research You have to learn how to mount the registry images with the command: reg.exe load When you are going to mount a registry image, you will give a name to the image that was mounted, this mounted image is called "hive", in this case I put your Nick. So you will have to adapt your registry file to be imported properly. You have to know the path of the registry images inside the mounted wim image. Code: reg.exe load HKLM\NathanIT_COMPONENTS "%~1\Windows\System32\config\COMPONENTS" >nul reg.exe load HKLM\NathanIT_DEFAULT "%~1\Windows\System32\config\default" >nul reg.exe load HKLM\NathanIT_NTUSER "%~1\Users\Default\ntuser.dat" >nul reg.exe load HKLM\NathanIT_SOFTWARE "%~1\Windows\System32\config\SOFTWARE" >nul reg.exe load HKLM\NathanIT_SYSTEM "%~1\Windows\System32\config\SYSTEM" >nul where %~1 is the mount point you set. For w11 boot.wim Bypass TPM (Hardware Requisites), you must mount index 2 and mount the hive reg.exe load HKLM\NathanIT_SYSTEM "%~1\Windows\System32\config\SYSTEM" >nul So, you integrate your reg file. You have to use the command: reg.exe import filename.reg. Finally, you have to unmount the hive with the command: reg.exe unload Code: for %%h in ( COMPONENTS DRIVERS DEFAULT NTUSER SCHEMA SOFTWARE SYSTEM ) do ( reg.exe unload HKLM\NathanIT_%%h ) >nul 2>&1 or: Code: for /F "tokens=* delims=" %%h in ('reg.exe query "HKLM" ^| findstr.exe "{"') do reg.exe unload "%%h" >nul 2>&1 reg.exe unload HKLM\NathanIT_COMPONENTS >nul 2>&1 reg.exe unload HKLM\NathanIT_DEFAULT >nul 2>&1 reg.exe unload HKLM\NathanIT_NTUSER >nul 2>&1 reg.exe unload HKLM\NathanIT_SOFTWARE >nul 2>&1 reg.exe unload HKLM\NathanIT_SYSTEM >nul 2>&1 Same thing. More information about reg.exe open cmd and: reg.exe /? For each index that you want to apply to your files you have to repeat these steps. That said: You already have where to start studying. But the easiest way is to use the tools, open them with notepad++ and read the sequence of commands. After all, a script is nothing more than putting in a text the commands that we use via the command line, and taking advantage of the resource of making them executable.