Corrupted System File SFC Can't Fix

Layback Bear said:

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 said:

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 said:

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

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.

NoelDP said:

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.

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