Sysprep is a mess sometimes and I still love your work I'll try some installs and see what happens. Regular install over LAN leaves the files intact. no MRP-folderr in C:\Windows yet tho even exclusion is added. removed already?
Once mrp has completed, or crashed it should clean up the work folder/scripts. When the run once entry been used the os auto deletes the reg entry it uses, well it should. Will have to find time to deploy a os in other ways and see if i can make mrp do its work.
Majority of code at least for the branding side is still the original code, i have only updated it to be more efficient such as for hp/compaq and the newer brands. My code for the options is all new, also the msdm routine that was revamped to be more responsive and not just insert a oem-dm key if it not for the edition installed. Plus the limited server branding etc, that was fun and games, but it's almost perfect, but as servers act different to client os's some bits not work in same way.
A deploy over network (Deployment Toolkit, Deployment Server) applies MRP to the admin user. I checked "transfer to new user" which woorks pretty good. After MDT is done I usually join the pc to the domain and be on with it. Yesterday I rebooted the VM before doing so and the runinvisible.vbs was removed. Not before a reboot. The cleanup process removes it perhaps but something calls the script when I login with a new user
When a signout/reboot cycle is done after the desktop appears then a clean-up process is done via 'runonce' so it tidies up any last bits of MRP. However RunInvisible.vbs is not one that is removed - i checked and no reference to a DEL command for that file is done,, it used to before on v134 and earlier, but on the latest i made sure it was not removed. I am thinking that somehow the vbs is not being copied over during deployment which is odd if MRP is copied over to the scripts folder as the project will auto-create it in <SystemDrive>\Windows if it not already there.
What i might do is alter the clean up to not use that vbs, so there may be a window appear that shows the clean up process on slower devices. At least then there should be no errors shown I can send you a link via PM to a modified v135 without the invisible clean up script if you wish?
OK -- Just finishing editing (REM'ing out certain parts and adjusting so it not calling the vbs)... Be about 5 mins.
Latest version I have on my pc is WinterBlues_M133.F2-BL_Refresh_Compiled_26th_Jan_2021 . Remember the password?