Discussion in 'Windows 10' started by MonarchX, Mar 23, 2017.
You need to login to view this posts content.
The files are exactly the same, only UUP iso's lack the boot index2.
It should not matter which source is used, if it runs 100% now, it could be coincidental, i haven't tried yet.
When this obsession with SFC and RestoreHealth is going to end?
it's like some users download new builds just to execute these two overrated commands and then complain
My UUP version and the original ESD version DO differ slightly - there's a couple different packages in the UUP version, one related to ieframe, another related to the migration functionality. The file dates differ by 7 minutes on these newer packages. (17:55 instead of 17:48).
what is the significance of lacking boot index 2?
It'll end when people stop wanting to check the integrity of their system files.
Thank you very much.
1st scenario: Your Windows is f***ed up but sfc /scannow says no problem found. But you know something is wrong.
2nd scenario: Your Windows is working normally yet sfc /scannow finds errors and is unable to correct them
SFC and RestoreHealth commands do nothing to fix problems.
Wasn't the problem with all 10240 x64 editions that sfc /scannow couldn't be used, we all survived
^^ Iirc was a hickup in components store, missing info regarding new files compression. Was fixed soon after.