Well but I see on the Picture that the source file could not be found. Btw i thought the index was the one its reparing, guess I got it wrong there
Thank you for let me know. I dont experience any problems so am not going to do reinstall as EVERYTIME there are some corrupted files RIGHT after new clean installation - tested myself on Win10 Pro several times. MS should figure out what the hell is going on here and do something about, because this is just unbelievable that any verison of W10 has corrupted files right after installation.
It's likely not a programming issue, but a quirk with hardware or driver timing or something that is causing the issue. I always think MS should take longer than they do to polish up their os before releasing them, but in the last few years they haven't been.
Thanks again, Murphy78, for this handy script. Today i've tested several win 10 indexes and i only have a syswow64 error on x64 versions but sfc was able to repair them this time. x86 versions where all okay
I've noticed this in win8 as well. I just figured it was data corruption or something. I guess it's just a bug that's been around since then. I've re-integrated a lot of releases because I didn't want to risk it. In the future I'll likely just re-attempt the install and re-check. If it doesn't duplicate the error I'll likely chalk it up to this install error. It seems to happen more in x64 versions.
Tomorrow i begin making 8.1, i always test all indexes and will pay extra attention to sfc when testing
I wonder what's the correct command to use LOCAL DISK'S SWM ( i.e WIM SPLITTED files ) to restore-health... Is the following correct ? Code: DISM /Online /Cleanup-Image /RestoreHealth /source:"F:\Sources\Install*.swm:1" /LimitAccess I'm not sure this works from my offline SWM files, as I suspect it falls-back to internet health-restoring. P.S - the script convert any splitted SWM back into WIM file - I DO NOT want to do that since I want to use the SWM as-is from a mounted ISO.
Afaik, that can't work, the split wim files don't contain all needed data in one .swm, so it needs to be merged before it can be used. Once the script ran the merge part, it will use the wim for the repairs.
Thank for the reply. is that true even when ALL the swm parts sit in the same "\sources\" dir within windows installation ISO ?