Solved Clean install Windows 7 32 bit and I have a Program Files x86 folder.

[DavidE]

Actually I'm not all that worried about it. Since if I'm not mistaken the fact that is was created
when the disks were stamped( July 13, 2009)means that folder is in fact on my cd it comes with my
installation of Windows .
I already have a SP1 burned DVD. I downloaded the iso file and burned it sometime after I installed SP1
and since I have cloned my ssd to my old Seagate drive as a backup I could take my SP1 dvd and do a repair install to it. I don't think a repair install would touch either of those folders though.

I agree, but only you would know if a repair install would make a difference.

From post #1

Is this normal?

I think everyone trying to help you does not see what you do, so the answer is "No, it is not 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).

 

[ShoTTaS]

The best thing to do is to follow the Clean Installation Process.

 

[ManyBeers]

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

I ran sfc /verify only
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

 

[AddRAM]

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.

 

[ManyBeers]

Actually I'm not all that worried about it. Since if I'm not mistaken the fact that is was created
when the disks were stamped( July 13, 2009)means that folder is in fact on my cd it comes with my
installation of Windows .
I already have a SP1 burned DVD. I downloaded the iso file and burned it sometime after I installed SP1
and since I have cloned my ssd to my old Seagate drive as a backup I could take my SP1 dvd and do a repair install to it. I don't think a repair install would touch either of those folders though.

I agree, but only you would know if a repair install would make a difference.

From post #1

Is this normal?

I think everyone trying to help you does not see what you do, so the answer is "No, it is not 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).

Hey it might be normal for an Upgrade DVD set vintage Oct. 2009 which is when I received mine. For all I know that folder was there from the getgo and I just never paid it no mind figuring it was just another Windows folder.

 

[gregrocker]

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.

 

[Slartybart]

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
.

 

[ManyBeers]

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.

I installed the DVD I showed you to my ssd with two formatted ntfs partitions (one System reserved and the other the rest of the disc). By definition that is a clean install.

When was your Program Files folder created?

 

[AddRAM]

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.

 

[DavidE]

In Post #43

That is the only issue which I knew would be because yesterday using resource hqacker I replaced

I'm going back to eating popcorn !

 

[ManyBeers]

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
.

I realize this. I just happened to be reading a thread somewhere and found out that most people maybe all people don't have the Program Filesx86 folder unless they are running 64 bit. But I do.
But I don't know how many of you in here have a 2009 Upgrade DVD like mine and are running it.
So that folder may be part of a default install for my disk and vintage.
Besides my computer currently runs great. This is not a functionality issue but more investigative.
Plus I have just spent several days getting my box right and to ask me to just rip it out and
start over....well i don't know. If I was experiencing some kind of issues that were making my computer unusable or something maybe then. But that is not the case here.

Thanks

 

[AddRAM]

Enjoy

 

[ManyBeers]

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.

Ok I'll mark it solved But is the bolded good or bad for me?
Incidentally the folders In my root were Created on July 13,2009 Not Modified.
My thinking is any folders on the DVD were Created when the disk was pressed.

 

[DavidE]

Enjoy

:roflmao:

 

[ManyBeers]

In Post #43

That is the only issue which I knew would be because yesterday using resource hqacker I replaced

I'm going back to eating popcorn !

So you didn't like the picture I posted. I think it looks pretty cool like that. I like the transparent look.
Resource Hacker is fine for the small changes I make.

 

[AddRAM]

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.

Ok I'll mark it solved But is the bolded good or bad for me?

We all told you the disc is old and we wouldn`t use it.

 

[DavidE]

In Post #43

That is the only issue which I knew would be because yesterday using resource hqacker I replaced

I'm going back to eating popcorn !

So you didn't like the picture I posted. I think it looks pretty cool like that. I like the transparent look.
Resource Hacker is fine for the small changes I make.

I don't have a problem with the picture.
Your post #43 shows you have System File errors, and you are using "resource hqacker".

I don't know what resource hacker is or does ... discussing it or helping you may be against forum rules

 

[Layback Bear]

Okay AddRAM brought the pop corn; who is going to bring the beer so we can continue to chat about a problem that doesn't exist. Bring lots of beer because it's going to take me a long time to understand resource hacker.

 

[AddRAM]

Okay AddRAM brought the pop corn; who is going to bring the beer so we can continue to chat about a problem that doesn't exist.

We are done with this issue, it`s Miller time

 

[ManyBeers]

In Post #43
I'm going back to eating popcorn !

So you didn't like the picture I posted. I think it looks pretty cool like that. I like the transparent look.
Resource Hacker is fine for the small changes I make.

I don't have a problem with the picture.
Your post #43 shows you have System File errors, and you are using "resource hqacker".

I don't know what resource hacker is or does ... discussing it or helping you may be against forum rules

It will open compiled binaries and other types of files to modify components within. In fact Brink
has several tutorials on this site that does just that. Look up "Change Windows Startup sound" or
something like that and you will have to hack imageres.dll to do so, using Resource Hacker or
something similar. Lots of people customize their box.
Yes I have one system file error...... ehres.dll has been modified by me. Which is the exact file I replaced the default Windows Media Center .PNG file with a .PNG file of my desktop. It does not effect WMC or anything else negatively. Windows was simply telling me that the file is not the way it should be.
I already knew that.