recently installed windows 7 pro x64 on a brand new computer that I built myself. My computer has two separate drives: A 64GB Kingston SSD used as a boot drive and a 500GB WD HDD. I installed windows 7 on the SSD and intend to use this drive (C: just to store the operating system). I want everything else stored of the HDD which I labeled as my E: drive. To avoid program files from being installed on my C: by default ( Like microsoft office, which does not ask you the location where you wish to instal) I changed the default instalation diretion in the registration. Here is exactly what I did
- run regedit from cmd
-changed ProgramFilesDir PATH from C:\Program Files to E:\Program files ( which I created myself), along with several other default paths
-Rebooted to allow changes to take affect
When the computer rebooted I tried to run regedit again and an error notification came up that says:
Windows cannot find C:\Windows\regedit.exe. Make sure you typed the name correctly, and then try again.
Im assuming I made a mistake when entering the new path names but I can no longer view the registry to see ifthat is the case because no matter what I do I cannot get regedit to run. I have been looking around everywhere for a solution.
here are a list of solutions/possible causes that I have found, but that do not work in my case
-Malware, I understand this problem is most commonly caused by malware or some virus. But my computer is brand new and I have yet to connect it to the internet, and I am the only one who has used it ( im working on a different pc right now)
-tried running regedt32 or regedit32 or REGEDIT or pretty much any other combination of the words 'reg' 'edit'
- Yes the regedit.exe does exist in the system. When I open C:\Windows I can see the regedit application, and yes it is stored as an application, and yes regedit32.exe is stored in C:\Windows\system32
I would realy like to find a solution to the problem that does not involve re-instaling windows or regedit, there has to be a way because liek I said it was probably cause by some typo and I know that the file is not corrupt or damaged.