If he means to modify and activate Trusted Store data.dat inside install.wim before installing OS, that is not possible
While I am not sure about the original Microsoft image, but you can achieve this goal by following my guide here and performing these additional steps: 1. Enter Audit Mode Install the Windows operating system. When the initial Out-of-Box Experience (OOBE) setup screen appears, press Ctrl + Shift + F3 to bypass the standard setup and boot directly into Audit Mode. 2. Install and Activate Software Install all required Microsoft software and any additional software you require. Ensure the system is connected to the internet, and utilize the MassGrave TSForge script to activate the installed products. (Note: Online activation is necessary at this stage, as newer Windows builds utilize a Static CID). 3. Backup Activation Tokens Navigate to the Software Protection Platform directory located at C:\Windows\System32\spp\store\2.0. Copy and securely back up the tokens.dat and data.dat files. 4. Choose Your Deployment Path At this stage, you have two choices depending on your deployment requirements: Path A: Standard Sysprep Capture If a strictly offline image is not required, you may proceed directly to executing Sysprep as mentioned in my guide. Run the Sysprep tool with the "Generalize" option to prepare and capture the image. Crucial: You must include the <SkipRearm>1</SkipRearm> tag within the <generalize> pass of your unattend.xml or autounattend.xml file. This ensures the activation state is preserved after deployment. Path B: Completely Offline Image Creation If you require a fully offline sysprep process, you must start fresh from Step 1 after formatting your partition again. Upon entering Audit Mode on the fresh installation, do not connect to the internet or run the activation script. Instead, paste the tokens.dat and data.dat files you backed up in Step 3 into the C:\Windows\System32\spp\store\2.0 directory, overwriting the existing files. Once replaced, execute Sysprep with the "Generalize" option and capture the image. As with Path B, you must also include the <SkipRearm>1</SkipRearm> tag in your answer file to maintain the activation state after deployement 5. Final Deployment When you deploy this captured image to any target computer, the system will successfully retain its activated status. Furthermore, because the image was generalized, each newly deployed machine will automatically generate its own unique Security Identifier (SID). =============================================== Alternatively, you may attempt to inject the activation tokens directly into the original Microsoft ISO without performing a full Sysprep capture. To achieve this, mount the original install.wim file offline using the Deployment Image Servicing and Management (DISM) tool. Once mounted, navigate to the \Windows\System32\spp\store\2.0 directory within the offline image and replace the existing tokens.dat and data.dat files with the copies you preserved in Step 3. Commit the changes and unmount the image. But you would still need <SkipRearm>1</SkipRearm> to preserve the activation. I don't know if this works as i have never done it to the original install.wim
Hi guys..i.ve windows server 2022 evaluation copy installed (can't be activated directly) n i cant connect to internet (so i can use dism online command to convert to full version n then activate it ) So is there an offline method to convert it to full version without internet ? Is tsforge reset can reset trial period of this version ? Thanks in advance
Why did you install an EVAL version anyway? You could convert to non EVAL and use KMS_VL_AL or TSForge to offline activate it after.
@Fed mo - I think you're misinterpreting the context here. "Online" in the DISM sense just means servicing the running OS itself ("offline" would be servicing another image). So, you can convert without Internet, by entering the key. Edit: Still typing too slow...
I am hoping that Microsoft will do this for 10 IoT 2021 (the last non-SSE4.2 version still supported) but since it already has 10 yrs of servicing, they may not. If they did that, it would give an old C2Q box (for example) still nearly 9 more yrs of monthly updates and I have some C2Q and Phenom boxes that I want keeping on as long a poss.