Windows 10: Announcing Windows 10 Insider Preview Build 15025 for PC Insider

Page 46 of 66 FirstFirst ... 36444546474856 ... LastLast
  1. Ztruker's Avatar
    Posts : 4,558
    Windows 10 Pro X64 14393.576
       3 Weeks Ago #451

    There is a large difference in size between the install.esd generated ISo and the downloaded ISO form MS:

    Click image for larger version. 

Name:	15025ISOs.jpg 
Views:	87 
Size:	31.2 KB 
ID:	119785

    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 ...
      My System SpecsSystem Spec

  2. Wynona's Avatar
    Posts : 12,128
    Windows 10 Insider Preview
       3 Weeks Ago #452

    Fafhrd said: View Post
    Wynona: from : Microsoft Visual C++ Runtime Library Runime Error! Program: C:\WINDOWS\explorer.exe

    This user, Nat C., found that event logs had recorded this as .NET origins. However, others with the error weren't successful with this fix.
    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.
      My System SpecsSystem Spec

  3. Wynona's Avatar
    Posts : 12,128
    Windows 10 Insider Preview
       3 Weeks Ago #453

    f14tomcat said: View Post
    Wynona, I got the one time. Did a cold shutdown and let the caps drain (i.e. - let it sit for a minute), powered back up and never saw it again.

    You could yank the battery, or for desktop, push and hold power button several times with it unplugged....but probably not necessary.
    It worked, TC! For now, no more runtime errors.
      My System SpecsSystem Spec

  4. Fafhrd's Avatar
    Posts : 1,311
    Windows 10 x86 14383 Insider Pro and Core 10240
       3 Weeks Ago #454

    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; 3 Weeks Ago at 01:29.
      My System SpecsSystem Spec

  5. slicendice's Avatar
    Posts : 254
    Windows 10 Pro IP Build 15031
       3 Weeks Ago #455

    Trying to reproduce the asterisk error for feedback screenshot. Sometimes I get*asterisks instead of space in my messages.
      My System SpecsSystem Spec

  6. Fafhrd's Avatar
    Posts : 1,311
    Windows 10 x86 14383 Insider Pro and Core 10240
       3 Weeks Ago #456

    The asterisks seem to occur when backspaces or overtyping is used for correcting errors.
      My System SpecsSystem Spec

  7.    3 Weeks Ago #457

    Thanks M$
      My System SpecsSystem Spec

  8. Fafhrd's Avatar
    Posts : 1,311
    Windows 10 x86 14383 Insider Pro and Core 10240
       3 Weeks Ago #458

    martyfelker said: View Post
    Thanks M$
    For the nice ol' ISOs?
      My System SpecsSystem Spec

  9. jyusa's Avatar
    Posts : 724
    Windows 10 Pro x64 Build 15031
       3 Weeks Ago #459

    Fafhrd said: View Post
    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!
      My System SpecsSystem Spec

  10. slicendice's Avatar
    Posts : 254
    Windows 10 Pro IP Build 15031
       3 Weeks Ago #460

    Ztruker said: View Post
    There is a large difference in size between the install.esd generated ISo and the downloaded ISO form MS:

    Click image for larger version. 

Name:	15025ISOs.jpg 
Views:	87 
Size:	31.2 KB 
ID:	119785

    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 ...

    My ESD generated ISO for Windows Pro 64-bit is 4,235,124,736 bytes which is very close to what MS is sharing.
      My System SpecsSystem Spec


 
Page 46 of 66 FirstFirst ... 36444546474856 ... LastLast

Related Threads
UPDATE 2: 764169017733025792 UPDATE 1: 764153098935922692 763865659079925760
UPDATE: 742889757512867840 Source: Announcing Windows 10 Insider Preview Build 14366 Mobile Build 14364 | Windows Experience Blog
695034380524216320 Source: Announcing Windows 10 Insider Preview Build 14257 | Windows Experience Blog
UPDATE: November 9th 2015 663817978471804928 663818555217985536 662328639673864192
UPDATE 3: Microsoft Releases PC build 10565 to Insiders in the Slow ring today. 655071954639020032 UPDATE 2: Download: https://www.tenforums.com/tutorials/9230-windows-10-iso-download.html#option3
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 04:12.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums