Using SFC and DISM to Repair and Service Windows 7+ Installations | Tech Support | Forums

A A A

Please consider registering
guest

Log In Register

Register | Lost password?
Advanced Search

— Forum Scope —

  

— Match —

   

— Forum Options —

    

Minimum search word length is 4 characters - maximum search word length is 84 characters

Topic RSS
Using SFC and DISM to Repair and Service Windows 7+ Installations
System File Checker (SFC) and Deployment Image Servicing and Management (DISM Tools for Windows 7, 8 and 8.1
Topic Rating: 0 (0 votes) 
March 13, 2014
9:38 AM
JMJ
Novice
Forum Posts: 9
Member Since:
January 11, 2011
Offline

Continuing comments from Alihassan Mahdi’s dotTech.com article, dated March 12, 2014.

It appears that DISM servicing commands on a live system apply only to Windows 8 and above.  Some DISM commands can be executed on a live Windows 7 installation but the repair/replace commands do not work.  For Windows 7 and below, SFC and/or the Windows Update Readiness Tool can be tried.

March 13, 2014
11:43 AM
BearPup
Nerd
Forum Posts: 55
Member Since:
January 20, 2013
Offline
2
0

OK JMJ, where did the “Windows Update Readiness Tool” come from? Isn’t that the compatibility testing program for going from one version of Windows to another? I’ve never heard of that usage before. Does it really test every file for its presence and its ability to function properly? I’ve also never heard of the DISM command.

So lets assume I start to have trouble installing programs again (the ‘clue’ I got that something was “wrong” with my system), what should I have done before the problem surfaced again, and what should I do to recover from the ‘System Found Errors But Cannot Correct Them’ message? Answering these two question is the crux of the issue for me.

Talk with you later.

Regards,

BearPup

March 13, 2014
12:28 PM
JMJ
Novice
Forum Posts: 9
Member Since:
January 11, 2011
Offline

The Windows 7 Update Readiness Tool tests your Servicing Store Package to make sure that all files necessary to update Windows 7 are available and in uncorrupted form.  If errors are found in that Store, the Tool attempts to provide or replace them with good files.  SFC on steroids?  That Store (unlike in Windows 8) is the same that SFC references in trying to do its work.

SFC you are familiar with. 

The DISM Tool works with Windows 7 too but, as discussed by Alihassan,  is only available from Windows 8 onward.  That is why it would not work for the Windows 7 64bit system I tried it on.  It is, however, a very powerful tool that incorporates 4 older Microsoft tools and then goes further.  The drawback for neophytes like me is that it is a command-line only tool and learning the proper syntaxes is time consuming and fraught with potential errors, like typos for example.

In your particular instance, I would have done this:

1.  Do an SFC and, whatever the results and from the same Command window;

2.  Do a CHKDSK /r.   After rebooting and if there were any unrepaired files from the first SFC scan, I would re-run SFC.  If any corrupted or missing files still were found, I would proceed to

3.  Download and run the latest Windows 7 Update Readiness Tool which would output its log to ẄindowslogsCBSchecksur.log .  Then, I would

4.  Run SFC once more and, if there remained missing or corrupted files, I would go into the next phase of recovery; i.e., manually restoring said files from a CD/DVD or even a good Windows installation.  If you need assistance with this, especially after reading the Microsoft article linked to earlier, let me know.

The thing that troubles me in your case is that you encountered these issues even after a reformat and clean re-install.  That leads me to suspect that your hard drive may be failing or, less likely, that your installation media is corrupted.

 

March 13, 2014
5:30 PM
BearPup
Nerd
Forum Posts: 55
Member Since:
January 20, 2013
Offline
4
0

@JMJ: To begin with, the last two SFCs that I’ve run have come back clean. Here is what I suspect happened:  the original C:\ drive that was an old used drive exhibited signs of impending failure after doing two repair and clean installs failed to correct the SFC problem. I pulled that drive and installed a brand new hard drive, where I successfully installed Windows 7.

In the interim I had been in touch with a software developer that their software hadn’t warned me of the impending failure of my C: drive. They requested I send them the drive so they could see what had happened; I agreed to do this and placed it in an external USB enclosure to erase and reformat the drive prior to shipping it off. It was after that that the new drive started ‘acting up’, resulting in a failed SFC.

To hopefully correct this I reformatted the new C: drive and immediately installed Windows from my original installation DVD. Since then I’ve run every security scan I have, as well as running the SFC tool, and so far so good – everything has come up clean. Hence I’m convinced that whatever problem was causing the corrupted files was something related to the original (used) hard drive that I replaced. As I said, since the reformat and reinstall of the new drive, all scans have come back clean. I’m also hoping that the company that I sent the failed hard to will be able to diagnose what happened to that hard drive.

I suppose I could run the Windows Update Readiness Tool test, but I’m not sure what good it would do now. I’ll wait for your weighing in.

Regards,

BearPup

March 13, 2014
5:47 PM
JMJ
Novice
Forum Posts: 9
Member Since:
January 11, 2011
Offline
5
0

It appears that I misunderstood that you were exploring, for current or future reference, means for identifying and repairing/replacing files that SFC flagged but was unable to fix itself. 

I also was not aware that two, separate drives were involved.  If the new drive is functioning properly and this new Windows installation is behaving properly, I say, finis. 

The linked resources on proper use of the SCF Tool are there.  A simple online search for similar resources relating to DISM and the Update Readiness are a click away.

Best regards.

–JMJ

 

 

 

 

March 13, 2014
6:16 PM
BearPup
Nerd
Forum Posts: 55
Member Since:
January 20, 2013
Offline
6
0

Your understanding was correct. Having gone through replacing the drive and then having the new drive ‘act up’, I wanted to know how I could fix the problem, i.e., figure out what files were corrupt and how (where) to replace those files, short of doing a full reinstall.

Since that original post I’ve gotten the new drive to accept a Windows installation with the SFC successfully completing twice, with a backup taken each time a successful conclusion was reached. My search here is not merely academic. If / when I get another problem with not being able to complete SFC successfully I’d like to be able to resolve it without having to reinstall everything from scratch.

The links that I’ve garnered through this have been saved and are appreciated.

Best Regards,

BearPup

March 15, 2014
11:43 AM
BearPup
Nerd
Forum Posts: 55
Member Since:
January 20, 2013
Offline
7
0

Hey JMJ, I’ve got a problem! Its happened again, sort of. I tried installing Cyberlink’s PhotoDirector and it failed to install properly – no text anywhere and no terminating it except from the Task Manager. This is exactly where I entered this nightmare to begin with. This time however, when I ran SFC, I got the all clear – no corrupt system files.

That’s the good news. The bad news is that I don’t have the foggiest idea of what to do, where to look, etc. I’m about to run the Windows 7 Update Readiness Tool and see what info that might provide. And/but..I’ll post back here with those results.

Regards,

BearPup

March 15, 2014
12:51 PM
BearPup
Nerd
Forum Posts: 55
Member Since:
January 20, 2013
Offline
8
0

@JMJ: Well I ran the Tool,and here are the results:

 

=================================
Checking System Update Readiness
No errors detected
Binary Version 6.1.7601.22471
Package Version 23.0
2014-03-15 15:44
=================================

 

Great news, but I’m at a total loss as to what to do. Any ideas on your end?

Regards,

BearPup

March 15, 2014
1:42 PM
JMJ
Novice
Forum Posts: 9
Member Since:
January 11, 2011
Offline
9
0

Hi there, BearPup

A fresh OS reinstall AND clean bills of health from SFC and WURT points to CyberLink itself as the source of its installation failure.  Did it produce any installation logs?  What does Event Viewer say?  Windows, itself, does not throw up an error window or a post-fail dialog?

I’m sure you disabled all security software before trying the installation, right?

Is this the first time after OS reinstall that you tried to install PhotoDirector?

March 15, 2014
2:23 PM
BearPup
Nerd
Forum Posts: 55
Member Since:
January 20, 2013
Offline
10
0

@JMJ: A lot of questions, but no answers. There are no installation logs; the installation “completed successfully”; and, Event Viewer reports no errors, no warnings, no anything – I’ve never seen so many “0”. This is not the first time I’ve tried loading PhotoDirector, but the last time (which worked right after the fresh install of Windows), was from a different download. This install, a direct download from the developer’s site, seemed to install fine, except that there’s no text anywhere on the screen.

And before you ask, no I don’t have the previous (older) version of PhotoDirector :). Nor have I tried to install any other software since PhotoDirector; I installed several programs over the last week that I was trying out. There were no problems with any of them. All scans come up clean.

Your thoughts?

March 15, 2014
2:53 PM
JMJ
Novice
Forum Posts: 9
Member Since:
January 11, 2011
Offline
11
0

Strange but, at least, your System appears sound.

Okay.  If you monitored installation with something like Revo Uninstaller, do a Forced Uninstall, clean your Temp folder and try again.

If you did not monitor installation,  uninstall from Control Panel>> Programs and Features, if an entry for PhotoDirector appears there.  Then, cleanup any leftover references with Windows Installer Cleanup Utility, a copy of which is in my OneDrive, here: http://1drv.ms/OhYibP  with Instructions here: http://1drv.ms/1gnW68o .

Following whichever steps are appropriate, try installing PhotDirector again.

Btw, this is the version of I have installed: CyberLink PhotoDirector 5 Ultra 5.0.4728 . If you do not require a newer version, let me know.

March 15, 2014
3:58 PM
BearPup
Nerd
Forum Posts: 55
Member Since:
January 20, 2013
Offline
12
0

@JMJ: Followed your instructions:  IObit Uninstall PhotoDirector; reboot; install / run MSICUU; reinstall PhotoDirector. No change / same result – no text.

The version I’m trying to install (and the version my license is good for) is 4.0.4317 .

Thanks in advance for your help with this.

March 15, 2014
7:37 PM
JMJ
Novice
Forum Posts: 9
Member Since:
January 11, 2011
Offline
13
0

I am at a loss, however, CyberLink seems to have good resources to resolve these issues, including special Cleaner Tools:  http://www.cyberlink.com/support/product-faq-content.do?id=16640&prodId=211&prodVerId=-1

Given all the steps taken to verify your system’s integrity plus the very existence of such tools implies that your problem is CyberLink-related and not system related. 

Please, keep us informed. 

Good luck. Wink

– JMJ

 

 

 

 

 

 

 

Forum Timezone: America/Los_Angeles

Most Users Ever Online: wp_sferrorlog

Currently Online:
34 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

phoenix_rising: 899

karen: 878

Wheezer: 786

yourpalal: 647

PCbasics: 614

ebony: 548

Member Stats:

Guest Posters: 11

Members: 9777

Moderators: 0

Admins: 3

Forum Stats:

Groups: 3

Forums: 17

Topics: 2601

Posts: 16629

Newest Members: e4xlns, ed.vera.link@gmail.com, airkhamcrys, jaynaik, riviere, Skhandisa

Administrators: Ashraf: 1799, Locutus: 1886, amnesia: 270

Comments