Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


Forums › Microsoft Windows › Overcoming Windows 10 corrupted files
OldGeek

989 posts

Ultimate Geek
+1 received by user: 409

ID Verified
Lifetime subscriber

#208812 28-Feb-2017 16:56
Send private message

I have a PC at home running 10 PRO 1511.  The Anniversary Update install fails because of 'corrupted files' and a Google search typically reveals the need to run SFC /scannow followed by DSIM commands.  I have also tried a SFCFix utility.  All fail with the same corrupted files error.  I would provide screen shots but the problem does not appear on this PC.

 

One option I am not able to try is the DSIM command with a SOURCE operand.  There is no clear indicator as to what must be specified in the SOURCE path but I did read that a Windows 10 ISO created by the Media Creation tool is NOT one of them.

 

Is there anyone in GZ who has used DSIM with a SOURCE operand that has successfully repaired corrupt Windows 10 files?  I would welcome the opportunity to point DSIM to a usable SOURCE path!!

 

 

 

Thanks in anticipation.

Create new topic

This is a filtered page: currently showing replies marked as answers. Click here to see full discussion.

OldGeek

989 posts

Ultimate Geek
+1 received by user: 409

ID Verified
Lifetime subscriber

  #1747712 25-Mar-2017 20:58
Send private message

A resolution for anyone interested.

 

The PC involved was a 'barebones' PC offering from a local retailer, bought in October 2016.  While all the hardware was low-spec it was  basically a case, with low-spec motherboard, processor and memory package.  The mobo in particular was therefore a post-Win10 design.

 

I got to the point were the anniversary update install, from an ISO that included it, would fail with this error:

 

"0xC-1900101-0x30018

 

The Installation failed in the FIRST_BOOT phase with an error during SYSREP operation."

 

So - on to Microsoft Support.  They tried 3 times via remote support to get the anniversary update to install from the latest ISO image they had downloaded.  All failed with the same error.  In the end a second-level support tech referred me back to the 'manufacturer' as this error is 'most likely caused by incompatible hardware' that cannot be detected by the installer software.

 

In desperation I went back to Google and found a reference to this error resulting from the use of AVG antivirus software - which I have installed.  I uninstalled the AVG software (including the security software, tune-up and Zen products).  I then ran the install again from the ISO image that MS support had downloaded and IT WAS SUCCESSFUL.  I subsequently reinstalled the AVG package without any problem.

 

The moral to this story is to find and contact MS support in the first instance and never to give up when they admit defeat by falling back to the 'manufacturer-support' routine.  MS still use the hardware-compatibility excuse when the going gets tough.  At no time did the MS techs attempt diagnosis through the event viewer or any other form of diagnostics - they simply persisted with install attempts.

 

 

 

 

 

 

 

 

 

 

Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.


Updates »

Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.








RSS feeds
Main feed
Forums feed
Copyright
©2002-2026 Geekzone®
Site features
Geekzone BI dashboard
Geekzone Badges
Geekzone Status Page

 

Site Information
Subscribe to Geekzone
Privacy Statement
Forum Usage Guidelines (FUG)
Advertising
Trademark and copyright