Q: 'Files that are required for Windows to run properly must be copied to the DLL Cache' and prompting for XP SP3 CD when performing SFC scan. Files that are required for Windows to run properly must be copied to the DLL Cache.

XP HOME SP3 HP LAPTOP Hi all, I recently trıed to get sfc /scannow to work, thıs ıs the message ı receıve ' Files that are needed for Windows to run properly must be copied to the DLL cache' and ıt asks for the W. XP Home Edition SP3 Disc.(don't have a W.CD by the way). (ıt doesn't specify what.DLL eıther) I know thıs ıs a common problem for some users, and even though ı don't have any real problems wıth my laptop, ı would stıll lıke to get thıs to work,ıf possıble Regedit. HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows CurrentVersion Setup SourcePath is set to C: Any ıdeas as to what ı could do?

Thank you Edited by mysoul, 13 March 2012 - 04:10 AM. Follow the procedure here please it may be necessary to change the source path from C: as below.

IMPORTANT enable view of hidden files. You could try step 2 in the work around part of it and point it to the right drive. Or try pointing it at.C:Windows servicePackFiles servicePackFiles we are going to run System File Checker. To make sure all of your protected files are not corrupt. The scan will automatically replace any corrupt files that it finds. But first make sure that you can view protected files. My Computer.Tools.Folder Options.View.

Uncheck.Hide protected operating system files. Click Start.type in. Run At the prompt type sfc /scannow note that there is a single space between sfc and /scannow. A box should appear telling you how much longer the process should take..AS YOU do not have the CD scroll down to HOW TO WORK AROUND THIS for instructions. Once the scan is complete.Check for Windows Updates. After using the File Protection Service you will need to reapply some updates. Reboot and let me know how its running if everythings OK.

Rehide the protected files. My Computer.Tools.Folder Options.View. Check.Hide protected operating system files. ================== HOW TO WORK AROUND THIS Windows Protection Files are usually stored in:C:WINDOWS/System32/Dllcache C: in most cases is the root drive.yours may be different.

The dllcache folder is extremely important so Windows XP hides it from you. Folder Options. Hide protected operating system files. There is normally no need for the original XP CD to be inserted as your computer has a copy it can get hold of in this cache. If the Dllcache folder or part of it has become corrupted then you will be prompted for the XP CD. So your computer can get a clean copy.

Not ALL installations of Windows XP have ALL the system files cached into this folder. You may only have around 25-50MB of files in this folder under Windows XP depending on the settings in the registry. Note.mine has 433MB in it HOW TO WORK AROUND THIS borrow a friend or coworkers retail copy of xp.it has to be the same version that you have installed. Either home or pro.or have them put a copy of the I386 folder on a cd for you.then proceed to Step 1 As well as having a cache of all the system files on your PC, you should have the I386 folder from the XP CD installed on your hard drive. After doing this, it is quite simple to modify the registry to tell it the source path for these files.

This prevents 99% of requests for the the XP CD with Windows File Protection and the I386 folder also contains many other files that are sometimes needed by the operating system and this stops those requests for the XP CD. HOW TO PUT I386 ON YOUR ROOT DRIVE: Step 1 You will need to get your XP CD and locate the folder called: I386 This is a major folder and should be one of the first you see, now copy this onto your hard drive into the system root. For most of you that is going to be C: so you should end up with a folder that looks like: C:I386 Step 2 Your computer needs to know that you now have the necessary files on your PC. This is done by editing the registry. Here's how.type in regedit in the Run box on the start menu. By navigating to:HKEY_LOCAL_MACHINE SOFTWARE Microsoft /Windows/ CurrentVersion/ Setup You will see various entries here on the right hand side.

The one we want is called: SourcePath It probably has an entry pointing to your CD-ROM drive,(usually D:) and that is why it is asking for the XP CD. All we need to do is change it to: C: Now, double click the SourcePatch setting and a new box will pop up allowing you to make the change to the drive letter of your root drive, probably C: HERE at this stage if it AGAIN does not work having enabled view of protected operating system files, then change the source path to 1. Service pack files and/or the i386 folder if you have that on the C drive or in the recovery partition. The path for the i386 folder is C: on its own. As SFC automatically checks that folder if it is on C drive Now restart your computer and try sfc /scannow again Posted with acknowledgement to my colleague happyrock.

Edit by paws: it looks as though I must learn to type a little quicker, Macboatmaster has beaten me to it! Hi mysoul, Sorry to hear of the difficulties you are experiencing.

The fact that SFC has asked you to insert your Microsoft Windows XP Home Edition SP3 Installation disc, indicates that damaged, missing or incorrectly located Windows Protected System Files have been found. SFC tries to locate good copies of the required files from elsewhere within your computer, however if good copies cannot be found then it asks for the Win XP Home SP3 installation disc to be inserted so that the required files can be copied from it to the dll cache.

If you do not have the required disc then an easy solution is to borrow one from a chum.for the purpose of SFC this is perfectly Ok for you to do. You will need one with SP 3 included in it, so try and obtain the correct one, sometimes it is possible to use a disc with only SP2 included in it.but if this doesn't work then you can burn your own installation disc by slipstreaming SP3 into it. Regards paws. Thank you for the reply Mac, Ok lets get things in order here as ı'm a lıttle confused., 1.Show Hidden operatıng Files are always enabled on my laptop. C:WINDOWS/System32/Dllcache,(mine has 179 MB of files in it) 3.Can NOT borrow a W.XP CD from anybody here.. The I386 is on the ROOT DRIVE:C: 5.:HKEY_LOCAL_MACHINE SOFTWARE Microsoft /Windows/ CurrentVersion/ Setup SourcePath is set to C: In 'My Computer' CD ROM İS E: So with all that ın mınd,HOW do ı proceed??

Thank you Edited by mysoul, 13 March 2012 - 03:23 AM. HERE at this stage if it AGAIN does not work having enabled view of protected operating system files, then change the source path to C:Windows servicePackFiles servicePackFiles If that does not work then the final attempt is to check this and ensure the source path is the same You still keep being prompted for the XP CD There is another setting in the registry that may be causing the problem. Navigate to: HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows NT CurrentVersion SourcePath Make sure the entry here is the same path to the i386 folder as used above. C: if the i386 folder is on the root of C drive. If neither work then despite the fact that all apears Ok the dll.cache, the service pack files and indeed the i386 folder are corrupted. It may of course be only one fragment of one file. When it asks for the CD, click Try again, sometimes it then finds it without asking you a second time.

If Try again does not work, click ignore and see if still repeats the request. If that does not work try a chkdsk /r andf then check the results and ensure no bad sectors and then repeat the scannow If still no good you are I am sorry to say going no further without the CD and it will have to include SP3. Are you sayıng that ın HKEY_LOCAL_MACHINE SOFTWARE Microsoft /Windows/ CurrentVersion/ Setup SourcePath THAT ıs set to C:/ ı should set ıt to say C:Windows servicePackFiles servicePackFiles Is that correct? And what do you mean EXACTLY by your LAST SENTENCE: 'You still keep being prompted for the XP CD There is another setting in the registry that may be causing the problem.

Navigate to: HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows NT CurrentVersion SourcePath Make sure the entry here is the same path to the I386 folder as used above.' I usually don't have any problems followıng ınstructıons,however you're not beıng clear enough to me. But thank you for your effort. Well I am sorry - that you find the instructions in any respect unclear. Many Many people have used therm and NOT found them unclear. What exactly is it that you are having difficulty understanding. Normally sfc /scannow looks to the CD if it cannot find what it needs in various places on the hard drive.

HOWEVER on XP that search of locations on the hard drive is not as exhaustive as it is on Vista and 7 where system file check hardly ever asks for the CD/DVD You have already yourself altered the source path on one of the registry keys - providing you have done that correctly - there is nothing more to do with that key - in the first instance.,HAVING enabled the view of normally hidden files and folders. If the computer was one where the XP CD had been copied to another partition on the hard drive, as is frequently done, to circumvent the chance of the CD being lost or damaged when it is required, then instead of the source path, being the CD drive or in this case as you do not have the CD being the root of C Drive, then the source path would be the partition on which the CD has been copied to. As you do not have the CD copied to another partition you must, as you have, change the source path to the root of C drive. That means you simply point it to C: As that has you say NOT worked you follow the suggestion to point it to the Service Pack files, where many of the system files are retained in the Service Pack files. If that does not work and the CD is still asked for then you follow the suggestion to change the source path on the OTHER key as well. TO THE SAME PATH as is currently in use on the first key. The copy and paste of the instructions on to your topic is from, as I said a very frequently used item on this site and as I said I do not have knoweldge of it previously causing problems with people NOT being able to understand it.

THAT is not to say that it has always worked for the reason that I gave you - corruption of your files Have you tried the chkdsk / r that I recommended and then the repeat of the system file check IF after you have done this you are still having difficulty undertsanding my advice please post back and we will re- issue the guidance with images for you. Does this make it easier for you to follow Also, look for these other values in your registry and make sure they are correct: [HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows Curr entVersion Setup] SourcePath=C: [HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows NT CurrentVersion] SourcePath=C: [HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows Curr entVersion Setup] ServicePackSourcePath=C: WINDOWS ServicePackFiles The same rules apply to these other paths as well, in that they have to stop one short of the i386 folder in each case.

The third value is important if you have installed any service pack updates since installing from the original cd. If you have copied the i386 folder from the cd to the root of the system drive then, I have found that, all three must be correct to avoid error messages from sfc.exe, asking you to install the cd-rom again. Direct to: Riyad202 Please start your own topic Although your issue may seem similar there can be other factors that may need to be resolved. By bumping on someone's topic especially one that is over a year old it makes it confusing for the tech to understand who they are helping. This can in turn cause the wrong support to be given and can cause instability or worse to happen to your system.

Please post more information as to your exact issue in your topic. Include any error messages you get as well as your system specs. This will help us to assist you more efficiently. Thank you for your cooperation.

When you install an application only to have it crash Windows, there's a good chance the crash occurred because the application overwrote critical Windows system files. The results are unpredictable any time that system files are overwritten. The system may run fine with the modified files, or the system may operate erratically or fail completely. Fortunately, Windows 2000, XP, and Server 2003 use a mechanism called Windows File Protection (WFP) to prevent critical system files from being overwritten.

In this article, I'll explain what WFP is and how it works. I'll go on to show you how to modify or override WFP's behavior. (Note: Although WFP works almost identically on Windows 2000, XP, and Server 2003, this article's information, including the registry entries and SFC syntax, was written specifically for XP.) How Windows File Protection works WFP is designed to protect the contents of the Windows folder. Rather than preventing any modifications to the entire folder, WFP protects specific file types, such as SYS, EXE, DLL, OCX, FON, and TTF. Registry entries control the file types that WFP protects. When an application attempts to replace a protected file, WFP checks the replacement file's digital signature to see if Microsoft signed the file and to see if the file is the correct version. If both of these conditions check out, then the replacement is allowed.

Normally, the only types of files that are allowed to replace system files are those included with Windows service packs, hot fixes, and operating system upgrades. System files can also be replaced by Windows Update or by the Windows Device Manager/Class Installer. If the two conditions are not met, the protected file will be replaced by the new file, but will soon be overwritten by the correct version. When this happens, Windows pulls the correct version of the file either from the Windows installation CD or from the computer's DLLCache folder. Windows File Protection doesn't just protect files against modification—it also protects them against deletion. To see WFP in action, navigate to the WINDOWS SYSTEM32 folder and rename the CALC.EXE file to CALC.OLD.

When you do, you'll see a message indicating that changing the file's extension may make the file unusable. Acknowledge the warning by clicking the Yes button. Now, wait a few minutes and press the F5 key to refresh your view of the file system. It can take some time for the replacement to be made. When the file is eventually replaced, Windows will let you know by making an entry into the Event Logs. An interesting side note about WFP is that it actually works closely with the Windows installer program.

Any time that the Windows Installer needs to install a protected file, it hands the file off to WFP rather than attempting to install the file itself. WFP then makes the judgment call as to whether to allow the installation. System File Checker While automatic file replacement does save time, there are situations that may require manual intervention.

For example, you may not want to wait around for WFP to detect that a protected file has been replaced. Fortunately, there is a tool called the System File Checker (SFC) that you can use to manually control WFP. SFC is a command line tool that should be run from the Command Prompt window.

The syntax looks like this: SFC [/SCANNOW] [/SCANONCE] [/SCANBOOT] [/REVERT] [/PURGECACHE] [/CACHESIZE=x] The /SCANNOW switch tells SFC to scan all protected files right now. If an incorrect file version is detected during the scanning process, the incorrect version will be reverted back to the official Microsoft version. Of course, this may sometimes mean that you must have the Windows installation CD or the latest service pack or hot fix available. The /SCANONCE parameter tells WFP to scan the protected system files the next time that the machine is booted. During the scan, any incorrect files will be replaced with the proper versions. As the parameter's name implies, this type of scan will only happen once.

Subsequent system boots will occur normally without SFC running. The /SCANBOOT parameter is similar to the /SCANONCE option. The difference is that while SCANONCE scans the protected files the next time that Windows boots, the SCANBOOT parameter scans the system files every time that Windows boots. Both of these commands replace incorrect system files as necessary and may require you to provide copies of the correct file versions. The /REVERT switch is used to turn off SFC. For example, suppose that you used the SCANBOOT option to scan all protected files every time that the system boots.

As you can imagine, this would really increase the amount of time that it takes the computer to boot up. Eventually, you may get tired of these long boot times and want to disable the SFC. To do so, you'd simply use the SFC /REVERT command, which will prevent SFC from running at boot up. The /PURGECACHE switch is one to be careful with.

Earlier I explained that Windows uses a cache folder to store backup copies of the correct version of the various system files. If you run the SFC /PURGECACHE command, though, the cache will be emptied and the backup files will be erased. This command will also cause Windows to start scanning the various protected files and will rebuild the cache while doing so. Of course, this may mean that you'll have to provide Windows with the Windows installation media or copies of updated system files.

The last SFC command switch is the /CACHESIZE=x switch. There is actually a lot of contradictory information about the default cache size. While researching this article, I found three different Microsoft Knowledgebase articles that specified three different default cache sizes. One article suggested that the default cache size was 50 MB, while another suggested that the size was 300 MB.

Still another indicated that the size was unlimited. The default size doesn't really matter, though, because you can use the CACHESIZE switch to change the size of the cache to meet your needs.

To use the CACHESIZE switch, you must enter the command SFC /CACHESIZE=x, where x is the desired number of megabytes that you want to dedicate to the cache. After specifying the new cache size, you must reboot the system and then run the SFC /PURGECACHE command.

Beamng Serial Key. Controlling WFP and SFC through the registry Earlier, I explained that the registry controlled the general behavior of WFP. There are several different registry keys that you can modify in order to control the behavior of WFP. Some of these keys are directly manipulated every time you run SFC. Others have lower-level functions, such as specifying the location of the file cache or of the installation files. Modifying the registry can be dangerous. If you make an incorrect modification, it can destroy Windows and/or your applications.

Therefore, I strongly recommend creating a full backup before attempting any of the techniques outlined in this section. To access the SFC registry keys, enter the REGEDIT command at the Run prompt. This will open the Registry Editor.

Now, navigate through the registry tree to this key: HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows NT CurrentVersion WinLogon Normally, the WinLogon portion of the registry is used to control various boot options. Since many of the SFC options control whether SFC is run on boot up, however, Microsoft has placed the SFC-related registry keys in this location.

SFCDisabled This registry key controls whether SFC is enabled or disabled. There are actually four different options that you can set just by changing the DWORD value. The default DWORD value is 0. This setting enables SFC. Normally you won't want to change this value.

However, you can change the value from 0 to 4 to leave SFC enabled but to disable the popups. You may only disable SFC if you have a kernel debugger hooked up. If you are using a kernel debugger, you can change the registry key's DWORD value to 1, which will disable SFC and then prompt you on all subsequent boots as to whether you want to reenable it. You can also disable SFC by changing the DWORD value to 2. This option disables SFC at the next boot only. There is no option to reenable SFC, because SFC will automatically be reenabled on the following boot.

SFCScan Earlier, I showed you the SCANONCE, SCANBOOT, and REVERT options for the SFC. Any time that you use any of these options, SFC is actually modifying the SFCScan registry key. You can modify this key by changing its assigned DWORD value. The default value is 0. This value indicates that protected files should not be scanned at boot up. This setting is equivalent to running the SFC /REVERT command.

Changing the assigned DWORD value to 1 indicates that protected files should be scanned on every boot. Setting the SFCScan value to 1 is equivalent to running the SFC /SCANBOOT command. Finally, setting the DWORD value to 2 tells SFC to scan the protected files on the next boot, but not on subsequent boots. This is the equivalent to running the SFC /SCANONCE command. SFCQuota The SFCQuota registry key is used to control the SFC cache size.

As you may recall, earlier when I talked about the SFC /CACHESIZE= x command, I indicated that there was a lot of inconsistent information regarding the default cache size. Prasanth Hits Tamil Songs Free Download. On my system though, the DWORD value assigned to the SFCQuota registry key was 0xffffffff.

According to the Microsoft Knowledge Base, this translates into a 300-MB cache size. The same knowledgebase article indicates that you can cache all protected system files by changing this value to FFFFFFFF. SFCDllCacheDir Earlier, I explained that Windows uses the DLLCACHE folder as the location for storing cached copies of system files. Normally, this folder exists in the WINDOWS SYSTEM32 folder. However, by modifying the SFCDllCacheDir registry key, you can actually control the cache location. Cached files will always be placed in the DLLCACHE folder, but by using this registry key, you can control the folder's location.

The only catch is that you must specify a location that exists on a local hard drive. In Windows 2000, you could specify a network share as the DLLCACHE location, but this option does not exist in Windows XP. SFCShowProgress Yet another registry key related to SFC is the SFCShowProgress key. This registry key allows you to set its DWORD value to either 0 or 1. The default value is 0, which disables the SFC progress bar. Setting the value to 1 causes SFC to display the progress bar.

Source File Location Earlier, when I was explaining how WFP and SFC worked, I indicated several times that you may have to supply the Windows installation media or copies of valid source files under some conditions. By modifying the registry though, it is actually possible to point Windows to a set of source files rather than having Windows ask you for those files.

This registry key is found in a different part of the registry. To access it you must go to this key: HKEY_LOCAL_MACHINE Software Microsoft Windows CurrentVersion Setup Once you arrive at this location, you can specify the location of the Windows system files by using either a drive letter and path or a UNC. The only real gotcha associated with using this command is that you must place the files within a folder called I386.

For example, if your Windows system files were in a folder named C: I386, then you would only specify the C: portion of the path within the registry because Windows assumes that the I386 folder will exist. Likewise, if you were to use a UNC share, the I386 folder must exist beneath the share point. For example, if you were to share a folder called FILES, you would want to place the I386 folder inside of the FILES folder. You could then tell Windows to look at server_name FILES for the shared files. Windows would then look for the system files within server_name FILES I386. Additional reading For more information on Windows File Protection and System File Checker, check out these Microsoft Knowledge Base and Microsoft Developer Network articles: • • • • • • Related Topics.