Tried all posible way but the sources are not found... I am noot sure how you achieve that? I copy install.vim to C: try online try mounting the disk alway same answer, dont find sources.
I have had some problems. I hope it will solve my problems. Now it is scanning... EDIT: Now my OS is more stable. Even though you don't have problems, I think it is better to scan:
Ran it myself and looked at the logs. SFC fails due to Windows Component Based Store corruption (WinSxS folder). DISM "RestoreHealth" repairs the WinSxS corrupted components which are always two items from the Windows Unified Telemetry Client (Asimov) which is the new part of Windows 10 TP to collect all the detailed feedback data. Some quick research shows this "issue" with SFC/DISM and the UTC files goes back to build 9879. So it seems like either this is broken, or SFC/DISM are detecting a false positive since this component likely updates shortly after install based on what it is and how it works. At least that's what it seems like to me.
Thank you Jackalito fyi it worked for me also after rebooting and "Windows Resource Protection did not find any integrity violation" after shutdown/restart Oldish hardware testbox: Gigabyte Socket 775 EP45UD3L rev. 1.1, Intel® Core(τm)2 Duo CPU E8500 @3.16GHz 3.17GHz, Corsair 4.00 GB DDR2, Gigabyte HD4850 1GB GDDR3, WD Blk SATA HDD 650GB, LiteOn DVD+R DL. Testbox quad boot: WXPSP3, Win7 Ulti refresh. Win8.1, WXP ProfessionalSP3 x86, WIN7 Ultimate SP1 x64, WIN8.1 x64, Win10 Pro build 10041 works as expected using legacy boot menu at startup. (Win7default) via EasyBCD 2.2.0.182. just sayin Jackalito after the next restart & or shut down had to run step 4.1 again then, sfc worked as expected!
Finally got it working after creating an new install.wim from esd Made an iso with the same esd but that didn't work after mounting en specify path to install.wim I think it has something to do with compression or so !! Greetz Base
I found that mounting the file Windows 10 preview then right click then open , the install was quick, seamless and thus far no bugs or glitches. When using mounted I so gotberroe files corrupted.
I am stuck here failling to find sources and I tried many things: DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess Any posible solutions? Thank you
Copy the ISO to a usb flash drive. Notice the Drive letter. Substitute the flash Drive letter for X and hit enter. It worked for me
Update - did an absolutely clean install. Immediately ran SFC /scannow... failed at 18%. Ran the steps per the guidance here... success. SFC /scannow fixed damaged system files. And I too believe the system is now a bit more responsive. Will attempt to do some of things I could not do before and see if they now work. THANKS!
What happens if we just type "sfc /scannow" without the previous commands? Won't that also fix the system?
My last install failed to boot after repairing system files??? Downloaded the 10041 iso directly from Microsoft. This time, using the downloaded iso, SFC got to 28% before failing. Repair procedure again worked and this install has booted several times since the repairs were made.
I do not use the normal method to install 10041. but even this method is sfc can not work proper/ 1.download the Official Release of 10041.iso 2. remove the install.wim and add to USB. 3. also leave install.win in D:\wim\install.wim 4. Open GImageX locate D:\wim\install.wim 5. Apply to G: 6. after total apply to G:\ 7. open EasyBCD and add G:\WINDOWS\system32\winload.exe 8. save 9. Reboot an select G:\ as boot and let it continue to finish setup. all this and still SFC /scannow (every possible method Fails) 10. You can use v10041 and most things work. but no matter what is done you can not SFC and fix the errors... ea enough to hash the iso, validated and you can hash the install.wim validated so for those that can not make this WORK. it is due to MS releasing a F***up Beta release to the Public. I also make sure the Partition I install all Win 10 is a different HDD than my Main OS. so when all else fails, unplug the Win10 HDD.