Windows 10: Announcing Windows 10 Insider Preview Build 15025 for PC Insider
There is a large difference in size between the install.esd generated ISo and the downloaded ISO form MS:
1st one is generated via ESDtoISO tool. 2nd one is downloaded from MS. I guess the difference is the downloaded one has Home and Pro in it? Or ...
Thanks, Fafhrd. I first tried SFC /scannow and it didn't find anything. I was ready to try DISM when I inadvertantly closed the thread, and when I found it, of course, It was way past the point where your post was; in fact, I saw TC's post. Since I'm generally one to take the easiest path first, and TC's path although not promising, was simple enough to try. So I did, and lo and behold! It worked. I am no longer getting the runtime error. Doesn't mean I won't tomorrow, but for not, it seems to be solved.
It worked, TC! For now, no more runtime errors.
In my experience, SFC hasn't ever picked much up since the days of XP - there is now just so much internal redundancy in the winsxs that everything that gets corrupted gets corrected by background maintenance. Since DISM...RestoreHealth is a last resort before an in-place upgrade repair and then a clean install, I'd rather cut out the middlemen to save time.
I've been checking out Tweaking.com windows repair,which basically puts back in place what should be there, using the catalog files, component store and and DISM, but invariably it finds problems with the Windows NTFS file structure, even with systems that are running nominally OK - broken simlinks and junctions - reparse points - that few people really bother about, or understand.
It seems to think that 15019 x86 is a little bit broken with:
"These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 1)J:\WINDOWS\servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~x86~~10.0.15019.1000.mum
1 Combined Problems were found with the packages files, these files need to be replaced (These mainly only effect installing Windows Updates.)
│ The SFC (System File Checker) doesn't scan and replace some of these files, so you may need to replace them manually."
This bears out the non-availability of a 15025 upgrade for 15019 x86 version.
It's always been the case that the best cure for most of Windows' ills is a shutdown, a cup of coffee (and a
fag "quick drag" in days long ago) then a reboot.
There were 4 engineers in a car that was chugging along on the verge of breaking down. They were arguing from their own fields of expertise and speculating about the problem.
The chemical engineer considered that the fuel mix was probably wrong, the electrical engineer that the alternator, plugs and distributor needed attention, and the mechanical engineer that it was wear on the bearings due to dirty oil, but the computer engineer considered the cure was simple, because he came across the problem every day.
He said that all that was required was to close all the windows, turn everything off and wait for a few minutes, then start it up again, open the windows and everything would be fine.
The old'uns are the best!
Last edited by Fafhrd; 04 Feb 2017 at 01:29.
Trying to reproduce the asterisk error for feedback screenshot. Sometimes I get*asterisks instead of space in my messages.
The asterisks seem to occur when backspaces or overtyping is used for correcting errors.
For the nice ol' ISOs?
My ESD generated ISO for Windows Pro 64-bit is 4,235,124,736 bytes which is very close to what MS is sharing.
Source: Announcing Windows 10 Insider Preview Build 14366 Mobile Build 14364 | Windows Experience Blog
Source: Announcing Windows 10 Insider Preview Build 14257 | Windows Experience Blog
UPDATE: November 9th 2015
Microsoft Releases PC build 10565 to Insiders in the Slow ring today.