|
Home »
Windows
» Windows Installation
Summary: You can move the I386 folder, but in order to keep Windows File Protection happy, you'll need to update a registry key as well.
I actually get variations of this question on a regular basis. Recently as I was cleaning up the hard disk on my primary machine I found myself asking the same question. The answer is that you can move I386, if you then also make another change deep in the Windows registry. • If it exists C:\I386 (the folder "I386" at the root of your "C:" drive) most likely contains an image of the installation copy of Windows. It's often placed on your hard drive as a way to avoid having to ask for a CD when Windows decides it needs some file that hasn't yet been installed. It's also used as one of the repositories for the original files used by System File Protection and the System File Checker. If Windows determines that one of its files has been replaced with an unrecognized copy, perhaps due to a virus, then the System File Checker will restore the file to its original version from C:\I386. (It actually uses additional repositories as well, in case service packs and other updates have legitimately updated the file.) In an attempt to answer the question "I wonder what happens if ...", I carefully backed up the contents of my C:\I386 folder, and then deleted it. The next morning I woke up to this error message:
".. you can move your I386 folder to wherever you like,
as long as it remains visible to your machine, and you make the registry update
to let Windows know where it is."
Windows File Protection had attempted to check my system files. I'm fairly certain that the error message it technically incorrect. No files had been replaced by unrecognized versions. Rather, the error was simply that the reference copy it expected in C:\I386 was no longer there. I restored the copy of my machine's C:\I386 folder to another machine, on a folder that had been shared and that was visible on my local network. The "trick" to telling Windows where to look turns out to be a simple registry setting. Specifically the key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\SourcePath. Firing up regedit, locate that key:
Note how it's set to "C:\" by default. The folder must be named I386, and this setting tells Windows where to find that folder. Double clicking on SourcePath, you can then change it to be the full path to the I386 folder:
Note that it doesn't include the "I386", it just points to where I386 can be found. In my case it's \\freenas\notenmax\machine_specific\leo\i386, but the registry setting is \\freenas\notenmax\machine_specific\leo. (In my case "freenas" is the server, "notenmax" is the share, and then "machine_specific" and "leo" are just folders within that share. I386 does not have to be at the root of the share.) Once updated, the setting does not take effect until you reboot. After rebooting I opened up a command prompt window and forced Windows File Protection to check all my files by running the System File Checker (SFC /scannow):
It completed normally, indicating that all files were good, and that the I386 folder had been accessed successfully from its new location. The bottom line: you can move your I386 folder to wherever you like, as long as it remains visible to your machine and you make the registry update to let Windows know where it is. Related:
Article 11718 | Posted August 2, 2007 |
Archives Advertisers |
|
•
Ok, I have found out that my sourcepath was pointed at my e drive which is my DVD burner/player. I changed it to my C: drive but not sure what else I need to do. I see in your example you have \\freenas\notemax\machine_specific\leo. How do I find out what my server and share are?
Posted by: Karen James at January 11, 2008 11:41 PM-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The location you specify is wherever you copied the I386
folder of your installation CD.
Leo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
iD8DBQFHinPpCMEe9B/8oqERApZSAJ9gViH1LTwofE/FRYK6rCtK8Ni+BACfV8rv
Posted by: Leo A. Notenboom at January 13, 2008 12:25 PM7pULe+TcIfYiCQExrJVsvmo=
=GP5t
-----END PGP SIGNATURE-----
I changed the sourcepath but it didn't work. I had to change ServicePackSource and Installation Sources. I changed them both at the same time so you may get by just changing one of them.
Posted by: PC Resolver at January 14, 2008 01:40 AMI cannot locate the I386 directory on my root C drive.
I reformatted my drive after a system crash and reinstalled windows and all software. But there is not I386 in the C root.
I tried sfc/scannow, but it won't run.
Anything I can/should do?
Jack Federhofer
Posted by: John Federhofer at February 9, 2008 04:32 AMI'm having problems with Explorer crashing about once a day. It happens at different times while running different programs. I want to use sfc/scannow but as I own a Gateway I only have a Recovery Disk not an actual Xp disk which scannow doesn't understand and won't use as is. How do I replace my (as yet unknown) corrupt system files using the disk I have and scannow? Is there another option short of the dreaded reinstall?
Posted by: Tracie at February 12, 2008 11:38 AMI've moved my I386 file from my C drive to my E drive (my second hard drive). Now whenever I try to copy the I386 file to a dvd, it won't let me. I haven't deleted the file from my C drive yet (basically I have an I386 on both my C and E drives), and neither will copy to a dvd. I get the message "Windows has encountered a problem when trying to copy this folder. What do you want Windows to do?" -Retry- -Skip- -Cancel- I don't want to delete it from my C drive until I have a physical copy, in case there was a problem. What can I do?
Posted by: Craig Davidson at March 22, 2008 11:40 AMThanks.
But it appears a reboot isn't necessary, once the registry entry has been changed.
After editing my registry, I immediately called "sfc /scannow" and it began running properly.
Posted by: Kim Fox at May 23, 2008 12:20 PMI have a somewhat related problem. I inserted a card into a hub/combo card reader and windows crashed and then rebooted. Since then, all my USB devices have been acting erratically. I've tested them with another computer and they work fine. My guess: some files were corrupted in the crash. I got the "Files that are required to run..." Windows properly error box that you reference above. However, it demands an XP Professional SP2 CD rom. I upgraded to SP2 over the web. I have no CD rom to give it. It doesn't care about my original windows Home disk.
I ran the system file checker and it too asked me to insert the SP2 Pro disk I don't have. So apparently there are some files that need to be fixed or replaced. But I have no way to do this.
Any tips, other than buying another copy of Windows? Thanks in advance.
Posted by: Mark S at June 8, 2008 07:48 AMI need to run sfc on a second hard drive installed in my system. The dribe is labeled f:. Is it possible to run sfc on the F drive?
-Leo
Posted by: PTabor at August 4, 2008 07:30 AM
Another web "author" that doesn't take the time to develop the site correctly. I went to print these instructions out and the right margin was clipped...can't do it right just get out of the business.
Perhaps what you're seeing is that the right navbar/column is intentionally not printed since you can't click links on paper. Ads are also not printed. I've spend some time crafting the print experience on the site. It ain't perfect, but its good.
If you're actually seeing clipping, then: Why is only the left hand part of my page printed?
-Leo
Posted by: John Jenkins at September 5, 2008 05:31 PM