Yes, I'm running the script(s) in a VM on QEMU/KVM running the unmodified Windows 10 IoT LTSC 2021. I now see some DISM failures in the log that I didn't catch before, so if a VM would cause those, that's good to know. Is it also possible that I didn't disable Windows Defender well enough (turned off realtime protection only)? My most recent attempt used that version (SD10v202_10.2), but I accidentally clobbered my log file when I started my current test (testing a default config). I lost my log from SD10v202_10.2, but I do still have a log file from an earlier attempt on a slightly earlier version (SD10_v2_02_6 from July 16th or so). This attempt did not integrate DaRT or do cleanup, and it used a slightly different config, due to fewer options in SD10_v2_02_6: Code: set ReplaceStartMenuWithOpenShell=1 set DisableInternetConnectionChecking=1 set DisableDefender=0 set EnableStore=1 set IncludeWindowsRegulatedPackagesInLTSC=1 set CreateISO=1 I don't think I can attach the log as a file as a low-post-count member, but I'll post some interesting sections in spoilers below. It turns out there WERE some non-interrupting errors in it that I didn't expect, and they might indeed be responsible for the failure: Spoiler: DISM Error: 0x800f0806 ============================================================ Cleaning up the WinSxS Folder ============================================================ Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.19044.4651 Error: 0x800f0806 The operation could not be completed due to pending operations. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Spoiler: DISM Error: 2 ============================================================ Adding default app associations settings... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.19044.4651 Error: 2 Could not save C:\Users\SoForgetful\Desktop\Slimdown10\hotfixes\AppAssociations.xml as the OEM default assocations file in the image. For more information, refer to the help. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Spoiler: Get-WInfo Error: 47 ############################################### Get-WInfo ############################################### [ERROR] Can't open "C:\Users\SoForgetful\Desktop\Slimdown10\DVD\sources\install.wim" read-only: No such file or directory ERROR: Exiting with error code 47: Failed to open a file. Spoiler: Final Lines Stale mount entry pointing to C:\Users\SoForgetful\Desktop\Slimdown10\mount removed Scanning drive C for stale files The operation completed successfully. The syntax of the command is incorrect. The system cannot find the path specified. The system cannot find the path specified. I no longer have that particular dism.log to dig any deeper, but I can check it if my current attempt fails the same way.
Brother I have tested the script by doing a clean install in my system and the windows search isn't working. Also it doesn't contain Windows_Update_Medic_Service which is needed for HWID activation by MAS, Win RAR shell integration not working, its like context menu is corrupted. For windows search, I have done SFC and DISM restore health commands which tell me my system contains corrupted files and errors. I am attaching the windows and script log for your reference
I didn't actually have the enormous log file problem (the log I took the above excerpts from was about 242 kB), but I did notice that the PSF file was missing from my baseless cab, which might point to another silent failure of some sort (not sure): Spoiler: PSF Is Missing ============================================================ Extracting files from update cabinets (.cab)... *** This will require some disk space, please be patient *** ============================================================ 1/8: Windows10.0-KB5007401-x64.cab 2/8: Windows10.0-KB5011048-x64.cab [NetFx] 3/8: Windows10.0-KB5015684-x64_PSFX.cab [Enablement] 4/8: Windows10.0-KB5032906-x64.cab [Setup DU] 5/8: Windows10.0-KB5034232-x64.cab [SafeOS DU] 6/8: Windows10.0-KB5039893-x64-NDP481.cab [NetFx] 7/8: Windows10.0-KB5040427-x64.cab [Combined] 8/10: Windows10.0-KB5040427-x64-baseless.cab / PSF file is missing 9/10: Windows10.0-KB5039336-x64_inout.cab [SSU] 10/10: Windows10.0-KB5040427-x64_inout.cab [LCU] My current test is still running (forgot to prompt it forward into the update integration until a moment ago), but I'll find out soon if config made a difference.
As I said before, everything went well in the test, except for the baseless file, which was not found. Since the hfixes_ltsc.txt file was not updated with the new version, it downloaded the previous version, but did not recognize it for extraction. But in general, the script is working well. The error in Get-WInfo may be due to the lack of some tool. Check if you have the BIn folder inside Slimdown10 and if it contains the files/folders as in the attached image. EDIT: I just ran a new test, with hfixes_ltsc.txt updated to version 4717 and everything went without errors. See the attached LOG file.
Hi I've done a lot of testing today, but I haven't been able to figure out which service is preventing activation via HWID. Since the script was written for Windows 10, some things aren't very reliable on Windows 11. I'll keep trying to see if I can figure out the problem... For Windows Search to work, you need to change the initial setting from 1 to 0. it should look like this: set DisableWindowsSearch=0
It turns out that running SD10v202_10.2 from my VM creates a perfectly working ISO if I use the default config and runtime settings (except CreateISO=1). I didn't even need to use the new hfixes files, and there were no baseless cab errors, so those must be dependent on config or settings. (Thank you for the hfixes files though; I'll use them for future tries!) I do still get the wimlib info error at the end, but I'm not concerned about that one. For what it's worth, the contents of my Bin folder match your image. To summarize where things are with me: Running the script with my desired config from my VM had various DISM errors, and the resulting ISO hanged on install Running the script with my desired config worked for you on bare metal Running the script with a default config (except CreateISO=1) worked from my VM, and the resulting ISO installs just fine This seems to imply that my DISM errors and install problems are coming from some interaction between my VM setup and my desired script config/settings. I'll have to start gradually modifying the default config toward my desired config to find the culprit.
How to setting adjust desktop size and position. I can't use nvidia control panel. I want to play cs2 with 4:3 not have blackbar.
You are right, creating iso from the script is resulting in errors, its better to make iso yourself until @SunLion bro resolves it
That's not quite what I meant: Creating the ISO with CreateISO=1 actually worked fine for me. What I meant was that, in the case where it worked fine, the only change I made from the default configuration was to automatically create the ISO. Some other config (or setting) change (not CreateISO) is triggering the problems for me. That said, it's also possible that CreateISO is combining with the other (yet unknown) trigger to cause the problem...
I don't have any problems on Windows 10. But on Windows 11 this setting doesn't work... I'm doing more tests...
Firefox is garbage now. The head devs are morons who decided a couple years ago, that they could switch to Rust for critical components, with the wrong assumption that you don't have to worry about pointers or memory leaks anymore, and you can be a lazy donut eating programmer. Except, that's not how Rust works. Rust might gracefully handle the broken pointers, so it doesn't crash the program, but the pointers are still never released. You can't garbage collect them. Then it gets slower, until the program runs out of reserved memory and crashes. They f**ked up the entire codebase. There's no fixing it now. I switched to Brave and Chromium, it's all that's left.
Unfortunately, Edge has more telemetry than Windows. People keep finding it, and Microsoft just quietly places it somewhere else. You can't trust Microsoft. Bing only exists because they copied Google searches from IE for over 10 years. They literally reverse engineered Google. Microsoft almost blindly force released that AI assistant (spyware) that tracks everything you do. They pulled it out after everyone critically panned the stupid idea, but it will be back in the next feature update, just wait. Because Windows always had that tracking built in, they thought, why not feed the log data to AI? Let's make it easy to record and summarize everything you do on your PC, for "productivity." You really want to watch what you did on your computer yesterday? That's not for you, that's for others. That's for AI to compile what you do for the Corporate overlords. Office and government surveillance is going to be bleak in the future.