I agree, but only you would know if a repair install would make a difference.
From post #1I think everyone trying to help you does not see what you do, so the answer is "No, it is not normal".Is this normal?
I do agree an SFC is a good idea, it's best to run that periodically just to make sure there are no issues ...
It can't hurt, but may find problems you don't even know about (yet).
2015-01-22 16:46:41, Info CSI 00000080 [SR] Beginning Verify and Repair transaction
2015-01-22 16:46:42, Info CSI 00000082 [SR] Cannot repair member fileI ran sfc /verify onlyCode:[l:18{9}]"ehres.dll" of Microsoft-Windows-ehome-ehres, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2015-01-22 16:46:45, Info CSI 00000084 [SR] Cannot repair member file [l:18{9}]"ehres.dll" of Microsoft-Windows-ehome-ehres, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2015-01-22 16:46:45, Info CSI 00000085 [SR] This component was referenced by [l:172{86}]"Microsoft-Windows-MediaCenter-Package~31bf3856ad364e35~x86~~6.1.7601.17514.MediaCenter" 2015-01-22 16:46:46, Info CSI 00000088 [SR] Could not reproject corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\ehome"\[l:18{9}]"ehres.dll"; source file in store is also corrupted
That is the only issue which I knew would be because yesterday using resource hqacker I replaced
the Windows Media Center startup image in ehres.dll with my desktop image so media center appears to run transparently. And I did not want to repeat the process.Picture
Anyways I noticed that every folder in Local Disk (c was created on July 13, 2009
If this is true then you did not do a clean install, as per your title.
Do you have performance problems at all? If not then you could keep it the way it is.
If so then the next step would be a Repair Install. The OS is reinstalled while all files, programs and most settings are kept in place. This can however pass through bad settings so it's effectivess is somewhat limited.
Thus I'd compare the install you have now with the perfect install compiled in Clean Reinstall Windows 7 as you may not yet be experiencing Win7's native perfect performance until you delete all partitions and folllow those steps, tools and methods.
For example the millions of users who stick with factory-installed Win7 never experience the native performance of the OS as long as they do. Having a modded OS with such an obvious and unprecedented file mishap would make the install suspect enough to me to reinstall just to be sure you've got native Win7 performance.
Manybeers,
No one knows what's on that disc. Your install is odd after using that disc. Members have advised you to get fresh install media and pointed you to a tutorial that will get you a very nice Windows 7 install on your machine.
I wish you luck figuring out why that disc did what it did. It is impossible to do forensics on a machine in a remote environment.
How you go forward is up to you.
Bill
.
The only folder that says Date modified 7/13/2009 on the install I did 1 hour ago is PerfLogs, Common Files, MSBuild, Reference Assemblies, Windows NT and there are 4 others modified 11/20/2010.
Every other folder shows todays date. The Program Files folder has todays date on it.
So it must be your disc, so you can mark the thread solved.
Last edited by AddRAM; 22 Apr 2015 at 17:47.
In Post #43
I'm going back to eating popcorn !That is the only issue which I knew would be because yesterday using resource hqacker I replaced
Quote