Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Windows File Protection and the DLL Cache

Updated: 12 Sep 2007 | 4 comments
WiseUser's picture
0 0 Votes
Login to vote

Windows® File Protection (WFP) prevents the replacement of essential system files installed as part of Windows. Applications should not overwrite these files because they are used by the system and other applications. Protecting these files prevents application and operating system failures.

Protected File List

WFP protects files with the following extensions that are installed by Windows: .dll, .exe, .ocx, and .sys. In addition, the TrueType fonts Micross.ttf, Tahoma.ttf, and Tahomabd.ttf are also protected.

At the end of the Windows installation, WFP runs a scan of all protected files to ensure they have not been modified by applications installed through unattended installation. WFP also copies verified versions of these system files to the cache directory. When an application attempts to replace a protected file, WFP can restore the original file from the cache directory.

The default value is %systemroot%\system32\dllcache. To specify a different location for the cache, create the following registry value.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SFCDllCacheDir

This must be a local path. Using a network path creates a single shared network source for cache files, provided all clients using the share are running the same service packs and hotfixes.

The default size of the cache is unlimited. To change the size of the cache, use the following registry setting:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SFCQuota

If the value is SFC_QUOTA_ALL_FILES, all system files will be cached in the cache directory.

Due to disk space considerations, it may not be desirable to maintain cached versions of all system files in the cache directory. Depending on the size of the cache, WFP will store verified file versions in the cache directory on the system hard drive. WFP will add files to the cache until the size of the cache directory reaches the specified limit.

When an application attempts to replace a protected file that is not in the cache, WFP attempts to restore the original file from the installation source, prompting the user if necessary.

Comments

Harsh Mokal's picture
17
Sep
2007
0 Votes 0
Login to vote

So what is the resolution

So what is the resolution if we want to repackge a software which is upgrading WPF?
Is that going to be scripted for installation?
Windows wont allow to install WPF through MSI.

Regards
Harsh

R-Vijay's picture
17
Sep
2007
0 Votes 0
Login to vote

Solution for WRP/WFP

One solution to deploy/replace WRP/WFP files would be a hotfix or a service Pack.

As Harsh says, a MSI will not be able to do it.

Microsoft MVP [Setup-Deploy]
Weblog: www.msigeek.com

WiseUser's picture
17
Sep
2007
0 Votes 0
Login to vote

Solution for WRP/WFP

Yes, as Vijay.Raj says , only solution could be using a hotfix or service packs.

Usually Microsoft releases hotfix or service pack to upgrade the Windows protected files .

Wiseuser
Altiris Certified Professional

Harsh Mokal's picture
19
Sep
2007
0 Votes 0
Login to vote

In install folder?

Okies I agree with Vijay that hotfix or a service Pack is one solution.
But KV says it is the only solution. That seems I am bounded with microsoft. That means I need to wait for Microsoft's Hotfix and Service pack to get release and then only I can package the application.
The simple solution what I can think is isolation of that file to install directory and to check if it works. Don't you think its fairly possible? Correct me if I am wrong.

Thanks.