Solved Corrupted System File SFC Can't Fix

[tjg79]

OK, the solution for me to get to the "Repair my Computer" Command Prompt is to boot from the Windows 7 Professional x64 DVD.

In the "Repair my Computer" Command Prompt mode, my boot drive is E:\. However, I don't see the tjgaa folder and the system indicates the directory as "not found." I checked C:\, but that is my 100MB Reserved Partition. I checked D:\ and that appears to be my Disk 1 E:\ drive.

I looked for the extracted tjgaa folder on my C:\ drive when I first extracted all (tjgaa.zip) to C:\. I didn't see it, but I know it's there, because I did a second extract all and I got several pop-ups that asked if I wanted to replace the existing tjgaa folder and the files inside.

After I extract the tjgaa.zip file, extract all, to the C:\, should I be able to see the tjgaa folder on my C:\ directory?

Thanks for the assistance.

Regards

 

[tjg79]

OK, It appears that when I extract the tjgaa.zip file to the C:\, it produces a folder named amd64_microsoft-windows-security-spp-ux_31bf...

I see two options: 1. Use the folder the extract all command produces or 2. Create a new folder named tjgaa during the extract all process and extract all to that folder.

If I use the folder produced by the extract all command, then:

Should I be using the XCOPY E:\amd64_microsoft-windows-security-spp-ux_31bf... E:\windows\winsxs /y /i /s /v /h

for the final command?

Thanks for your assistance.

Regards

 

[Slartybart]

I will again defer to Noel on this.

edit: Sorry, just read your post again, do #2 when you extract
2. Create a new folder named tjgaa during the extract all process and extract all to that folder.


But I think you want to copy the tjgaa folder that you extracted not the subfolder.

XCOPY E:\tjgaa E:\windows\winsxs /y /i /s /v /h​

Noel then says to run the command... I'm not sure if he meant the xcopy or there's another command to run.

Best to review the instructions in #52 and wait for Noel.

Bill
.

 

[tjg79]

I will again defer to Noel on this.

edit: Sorry, just read your post again, do #2 when you extract
2. Create a new folder named tjgaa during the extract all process and extract all to that folder.


But I think you want to copy the tjgaa folder that you extracted not the subfolder.

XCOPY E:\tjgaa E:\windows\winsxs /y /i /s /v /h
​

Noel then says to run the command... I'm not sure if he meant the xcopy or there's another command to run.

Best to review the instructions in #52 and wait for Noel.

Bill
.

OK, thanks.

I think I'll try creating a new folder named tjgaa during the extract process and then checking to ensure the contents doesn't include a subfolder. If it does contain a subfolder, I move the contents of the subfolder to the tjgaa folder.

I hope I'm not screwing this up.

Thanks guys for all the assistance.

Regards

PS

It was easier just to create a new tjgaa folder on C:\ and move the contents from the amd64... folder to the new tjgaa folder.

Regards

 

[tjg79]

I've uploaded a file - tjgaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\tjgaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\tjgaa
or
DIR E:\tjgaa



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\tjgaa <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
C:\Windows\system32>sfc /scannow
Beginning system scan.  This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
C:\Windows\system32>

View attachment 327848

 

[tjg79]

XCOPY E:\tjgaa E:\windows\winsxs /y /i /s /v /h

Noel then says to run the command... I'm not sure if he meant the xcopy or there's another command to run.

I wasn't sure what he meant by "run the command" also. I thought it could have two meanings: 1. hit the enter key after typing the string, or 2. run the "slui.exe" command file.

I did both by typing "E:\tjgaa\slui.exe" at the command prompt, and hit "enter" after I did number 1. I didn't see anything unusual.

Regards

 

[Slartybart]

All you had to do was extract all, create a new folder during the extract.

Right click on noel's tjgaa.zip file, select extract all
the default destination folder is the same name but it is not compressed.
When you complete the extraction you have two folders named tjgaa
One is compressed (.zip) and the other is a regular folder

​

I'm not sure of two things
1) Did the folder you copy contain all of the files necessary to complete the task
2) What Noel meant by the run statement - was it the xcopy or was there another command

All you're doing is moving a folder to winsxs, I'm sure Noel will provide further instructions on how to repair slui.dll - there might be changes required to permissions. Do the move and wait for Noel.

Pease extract the files from the tjgaa compressed folder to a regular folder named tjgaa again (replace the existing folder). You need all of the files Noel provided to make this work.

Then Xcopy the regular folder tjgaa to windows\winsxs per Noel's instructions.

No harm, no foul.

 

[tjg79]

Success!

If there was only one way to screw it up out of a million choices, I would find it.

Apparently, the subfolder in folder tjgaa is important. When I copied the files to the C:\tjgaa folder the first time, I omitted the subfolder that is a product of the extraction.

I repeated the instructions, but this time ensured I had the subfolder with its contents in the C:\tjgaa folder.

I just hit enter after I typed the XCOPY command.

The result was a successful system file checker scan.

It doesn't appear that the slui.exe file is corrupted at this time.

A copy of the CBS.log file and sfc /scannow results are:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
C:\Windows\system32>sfc /scannow
Beginning system scan.  This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\Windows\system32>

View attachment 327877

If I don't get another activation pop-up in the next few days, I think the issue is resolved.

Thanks for all the support.

Regards

 

[Layback Bear]

Hang in there tjg79. Noel will probably want to take a look at things again and see results.
Even if your fixed Noel likes to see the results. It can help him on the next problem computer.

I went through this type of thing about a year ago on one of my computers.
Because people like me do it seldom it can get taunting.

 

[tjg79]

I think I'm back to where I was just before I contacted Microsoft Genuine Advantage and Microsoft Support three days ago. The system file checker shows no issues, but I still get the pop-up suggesting that my Win 7 is not genuine.

I'll start a new thread under Windows Updates & Activation to try to sort that issue out.

My error at following the instructions that NoelDP posted in post #52 was that I extracted the zip file to C:\ when I should have extracted the file to C:\tjgaa. I thought that since the zip file was named tjgaa.zip, it would unzip in the C:\ directory as tjgaa. It didn't.

This was a good thread for me. I learned about several good malicious software removal tools.

Thanks again to everyone for all the help and support. And, thank you NoelDP for your assistance and putting that system repair package together.

Best Regards to everyone.

 

[tjg79]

Hang in there tjg79. Noel will probably want to take a look at things again and see results.
Even if your fixed Noel likes to see the results. It can help him on the next problem computer.

I went through this type of thing about a year ago on one of my computers.
Because people like me do it seldom it can get taunting.

Yes, I know that my system issue is not entirely resolved. I still get the not genuine Windows pop-up.

I only run into major issues about once a year. Hopefully it will be less now that I've got a Smart-UPS. It's so infrequent, that I have trouble remembering everything I learned during my past troubleshooting episodes.

I did a complete disc clean-up and deleted all the old restore points. I'll do the same for my system back-ups and system images. I've rebooted in excess of ten times and run the system file checker about four times. Everything seems solid with the exception of the non-genuine Windows issue. Noel may see something in the CBS.log file, but as of right now, I think the systems files are good.

Regards

 

[Layback Bear]

Do you have all but the Windows 7 (C) drive disconnected? I'm thinking cross contamination when in Raid.
Just a thought.
Well I will stop having thoughts and let Noel and others do the thinking.
Don't do anything until the others get back to you.

 

[tjg79]

Do you have all but the Windows 7 (C) drive disconnected? I'm thinking cross contamination when in Raid.
Just a thought.
Well I will stop having thoughts and let Noel and others do the thinking.
Don't do anything until the others get back to you.

There really isn't any type of cross-contamination issues with Intel RST Desktop RAID. I run the RST utility weekly to check the media and clean up parity errors. If you start noticing significant numbers of parity errors, it time to check and test the hdds thoroughly; S.M.A.R.T and the disk media (SeaTools Long & Short Tests). Parity errors can be a warning flag for disk failure.

All RAIDs are not the same. I'm running Intel Rapid Storage Technology (RST) RAID5. My BIOS is set to RAID and once the RAID Volume is established, you can't remove it from RAID. My RAID5 is a three SATA 500GB hdd volume that displays as an approximate 1TB disk in the system. I can remove one hdd from the volume, but if I remove a second, the volume fails.

There were a few posts about RAID and Windows 7 and I think there is a lot of bad information out there. I don't know about other RAIDs, but the Intel RST Desktop RAID works great. It worked great with Win XP as well. Intel RST RAID 0, 5, & 10 actually improves the hdd performance. There's data security in RAID 1, 5, & 10, but none in RAID 0. RAID 0 is for performance only. I can have one hdd fail and I don't lose anything in RAID5. The Intel RST RAID5 is completely transparent to Windows 7. Win 7 just sees a 1TB disk. My RAID5 volume has three partitions; 100MB System Reserve, C:\ (Win 7 boot) & D:\ (nothing at the moment, but I plan to make D:\ a Win XP partition). I have the Intel RST write-cache buffer flushing disabled for performance. This configuration has more risk if the power fails, but I'm on a Smart-UPS now. I wasn't until about three months ago and I used to have some minor issues related to parity errors when the power failed. I would have to run the verification utility or the rebuild utility in such cases. It was the equivalent of running Windows Defender while your using your computer. You might notice some performance issues momentarily, but everything is resolved in a few hours.

 

[Layback Bear]

You have this thread marked as Solved. I would suggest marking it as Unsolved.

I know very little about Raid. Just the information of others having problems.
Just thought it might be worth thinking about. Witch you have so no harm done.

I will just sit back and wait for the big boys.

 

[tjg79]

You have this thread marked as Solved. I would suggest marking it as Unsolved.

I know very little about Raid. Just the information of others having problems.
Just thought it might be worth thinking about. Witch you have so no harm done.

I will just sit back and wait for the big boys.

OK, I'll change to unsolved until I get a go from the experts.

Thanks

 

[NoelDP]

SFC is clear - and there aren't any other errors in the CBS.log

There's no reason you should be seeing any further non-genuine notifications.

 

[gregrocker]

I'm not saying RAID can never work well with Win7, just that it's never been reported here that I've seen except in cases like this with intractable problems that were resolved when it was abandoned.

With backup imaging and lightning fast SSD's coming down in cost, there are better alternatives.

May I suggest you do a test install to a HD or SSD connected alone and wiped clean first? I would be very surprised if that doesn't solve your issue which is why I proposed it at the beginning of this marathon thread.

 

[tjg79]

SFC is clear - and there aren't any other errors in the CBS.log

There's no reason you should be seeing any further non-genuine notifications.

I've seen two non-genuine notifications since my post #68. SFC was clear just before I contacted MS with this issue.

I think the subject issue of this thread has been resolved. Thank you for the fix. I've never had an SFC issue like this before with Win 7.

I'll mark this thread as solved. I've started a new thread under Windows Updates & Activation for the non-genuine Windows indications.

 

[riddlemeright]

NoelDP - I am running into similar problems and would love to discuss with you. Any chance you have a bit of time?

 

[NoelDP]

Please start a new thread of your own, and...

...follow the Windows Update Posting Instructions and post the requested data

If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)