Windows Installer 3.1 won't install

[Hum]

After reinstalling Windows XP Pro sp2, I can not get any Windows Updates due to not having Windows Installer 3.1 anymore. And it will not install from the Update site, nor from the downloaded WindowsInstaller-KB893803-v2-x86.exe file.

It is always stopped by the Windows File Protection process. Even in Safe Mode.

Anyone else been thru this ? Any ideas ?

[John Veteran]

Try running sfc /purgecache and then reinstall Windows Installer 3.1.

[Hum]

^ Thank you for your suggestion John. I just tried that, but I still get this msg when it stops installing:

I guess Windows File Protection would somehow need to be turned off long enough to install the update. Safe Mode install also fails.

I'm awaiting a response from Microsoft tech support. :unsure:

[John Veteran]

That isn't Windows File Protection. That's an error from the hotfix saying it was denied access to something. Look in the event viewer to find exactly what was denied access.

When exactly do you get that error? Immediately after it finishes extracting to the temporary folder? (C:\asdfblahblahblah) Do you click next a few times and then get the error? What happens, exactly?

Edited February 1, 2006 by John

[Hum]

:huh: Erm ... I'm not sure KB893803v2 is considered a hotfix -- it's Windows Installer 3.1 and required to get anymore Auto Updates from Microsoft.

This is all the Error log says:

The error occurs near the end of installing, when it tries to change some .dll (which starts with an M -- too fast to read). Then the 'Access is denied' occurs. From what I've read at the Microsoft support site, this is WFM prevent this installation from replacing a system file.

These seem to relate:

http://support.microsoft.com/?kbid=873148

http://support.microsoft.com/kb/898628

http://support.microsoft.com/kb/898715

"With the release of Windows Installer 3.1, this behavior has changed. In version 3.1, the silent installation process does not succeed and then rolls back the installation if the silent installation process cannot install the WFP-protected file."

"WFP prevents applications from overwriting system files. Windows Installer cannot overwrite WFP-protected files. To resolve this problem, obtain the Windows Installer 3.1 General Distribution Release update."

[John Veteran]

Check the permissions on your \windows\system32\dllcache folder. The Administrators group and System identity should both be allowed Full Control permissions.

Also, post your \windows\KB893803v2.log file for us to look at. It should give more insight as to where exactly it is being denied access to (Y)

[Hum]

:huh: OK, I will. Here is a more detailed log I found, only about half of it, starting after the setting of a Restore point:

41.770: PFE2: Not avoiding Per File Exceptions.

41.860: GetCatVersion: Failed to retrieve version information from C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Tmp.0.KB893803v2_wxp.cat with error 0x57

44.134: Copied file: C:\WINDOWS\system32\msi.dll

44.344: Copied file: C:\WINDOWS\system32\msiexec.exe

44.434: Copied file: C:\WINDOWS\system32\msihnd.dll

44.634: Copied file: C:\WINDOWS\system32\msimsg.dll

44.714: Copied file: C:\WINDOWS\system32\msisip.dll

44.724: DoInstallation: Installing assemblies with source root path: c:\5ef54e00eb13d20fd53a83a41ff13a\

44.754: Num Ticks for Copying files : 10384

44.965: DoRegistryUpdates:UpdSpInstallFromInfSection Failed for MSI.Reg.Install: 0x5

44.965: DoInstallation:DoRegistryUpdates failed

46.036: Access is denied.

50.563: Message displayed to the user: Access is denied.

50.563: User Input: OK

50.573: KB893803v2 installation did not complete.

Select 'OK' to undo the changes that have been made.

99.774: Message displayed to the user: KB893803v2 installation did not complete.

Select 'OK' to undo the changes that have been made.

99.774: User Input: OK

[Wilhelmus]

Have you tried doing the steps 2-3 from http://support.microsoft.com/kb/873148?

Step 2: Locate the specific registry key

As soon as you have verified that a registry permission failure has occurred, you must locate the correct registry key to change the permissions and enable Windows XP SP2 or Windows Server 2003 SP1 to install successfully. To do this, follow these steps:

a. Include registry information in the Setupapi.log file by enabling verbose logging. For more information about how to enable verbose logging, click the following article number to view the article in the Microsoft Knowledge Base:

906485 (http://support.microsoft.com/kb/906485/) How to enable verbose logging on a Windows XP-based computer

Note By default, registry keys are not recorded in the Setupapi.log file.

After you enable verbose logging, install Windows XP SP2 or Windows Server 2003 SP1 again to capture the registry key.

b. Open the Setupapi.log file. By default, this file is located in the C:\Windows folder. To open the Setupapi.log file, click Start, click Run, type %windir%\setupapi.log, and then click OK.

c. Press CTRL+END to scroll to the end of the Setupapi.log file.

d. On the Edit menu, click Find.

e. In the Find what box, type Error 5: Access is denied under Direction, click Up, and then click Find Next.

The found entry in the Setupapi.log file should be similar to the following example:

#-007 Deleting registry key HKCR\vnd.ms.radio

#E033 Error 5: Access is denied.

Note The line before the "Access is denied" entry indicates the registry key in question. In this case, HKCR stands for the registry hive that is labeled "HKEY_CLASSES_ROOT." "vnd.ms.radio" is one subkey that is located under that registry hive.

Back to the top Back to the top

Step 3: Reset the registry permissions

As soon as you have found the registry subkey that has the incorrect permissions, update the permissions for that subkey.

To update the permissions of the registry subkey, follow these steps:

a. Click Start, click Run, type regedit, and then click OK to start Registry Editor.

b. Locate and right-click the registry subkey that you noted in Step 2d, and then click Permissions.

c. Under Group or user names, click Administrators.

d. Under Permissions for Administrators, make sure that the Allow check box for the following entries is selected:

? Full Control

? Read

e. Click Apply, and then click OK.

f. On the File menu, click Exit to quit Registry Editor.

[Hum]

:) Thanks for the suggestions. Microsoft gave me some complcated scheme to follow, which I used in part. Apparently all that was really needed is to right-click on HKEY_CLASSES_ROOT in regedit, and add my user name in Special permissions.

It was one of those weird experiences where I half-guessed what to change, and I'm not completely sure just what I did.

I don't really understand why this was needed -- since I am the only user and Administrator. I guess it was some side-effect of doing the in place Service Pack 2 upgrade. Some old and some new settings were mixed ?

All is well now, except either the Registry tinkering or some of the new patches messed up a few programs that were already installed. Fortunately I had some needed files saved to CD and reinstall took care of the rest. :laugh:

[Timba]

Hum, thank you! Thank you! I've been trying to help a friend get her computer running right, and having a terrible time with the update installer. I had done a 'repair installation' of XP Home with SP2, and although it activated just fine, the installer wouldn't work no matter what type of fix I tried. After reading your last post in this thread, I just added her account name, making no other changes anywhere. It all works perfectly now. I really wanted to avoid using her oem recovery discs because that would have wiped out all her settings and programs. Thanks again.

[GuidoZ]

I'd like to 2nd what Timba had to say - worked like a charm to just add the Registry permissions!

Had a mobo fry on a customers system. Replaced it, then Windows was unhappy. Performed a Windows reapir (with our OEM disk w/ SP2) and all was well. Went to go do updates and ran into this problem. After trying *EVERYTHING* from the friggin KB555175 page, I finally ran across this thread. Thanks for coming back and providing the solution that worked for you!! Nothing M$ said to do worked. Had I only tried the Reg hack 5 hours ago... :rolleyes:

--

Peace. ~G

[blagov]

After reinstalling Windows XP Pro sp2, I can not get any Windows Updates due to not having Windows Installer 3.1 anymore. And it will not install from the Update site, nor from the downloaded WindowsInstaller-KB893803-v2-x86.exe file.

It is always stopped by the Windows File Protection process. Even in Safe Mode.

Anyone else been thru this ? Any ideas ?

I had the same problem and spent a lot of time on Web. I found a lot of the same questions and no solutions.

After that I found solution for my computer myself. May be my way will help to somebody else.

Follow next:

Click Start/Run Type regedit click OK. Click any -sign to+ to see only HKEY_--- tables.

Right click HKEY_Classes_Root in fulldown menu click Permission select Secure table. In Group or User names box

should be Administrator or Administratos with name of computer. If you do not see it click Add button.

In open "Enter the object names to select" box type: Administrator, Name of your computer will add automaticaly.

Click Apply/Ok.

Check and Repeat it to all HKEY_

Close regedit and try to install Windows Installer 3.1. It worked on my computer succesfuly. Try the same

blagov

[BrokenWindows]

Hi, Im having a nightmare trying to get this to work. I think I have tried everything listed above but still no joy. Here is my log file if anyone can help. There seems to be so many errors Idont know where to start...

0.140: 2007/12/28 11:45:32.234 (local)

0.140: g:\0797be65586d454786c05f203b809b74\UPDATE\update.exe (version 6.1.22.4)

0.140: Hotfix started with following command line:

1.719: In Function TestVolatileFlag, line 11660, RegOpenKeyEx failed with error 0x2

1.719: In Function TestVolatileFlag, line 11692, RegOpenKeyEx failed with error 0x2

1.719: DoInstallation: CleanPFR failed: 0x2

1.734: SetProductTypes: InfProductBuildType=BuildType.IP

1.734: SetAltOsLoaderPath: No section uses DirId 65701; done.

1.797: DoInstallation: FetchSourceURL for g:\0797be65586d454786c05f203b809b74\update\update_wxp.inf failed

1.797: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed: 0xe0000102

1.797: BuildCabinetManifest: update.url absent

1.797: Starting AnalyzeComponents

1.797: AnalyzePhaseZero used 0 ticks

1.797: No c:\windows\INF\updtblk.inf file.

1.797: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102

1.797: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102

5.000: CreateUninstall = 0,Directory = C:\WINDOWS\$MSI31Uninstall_KB893803v2$

13.328: SetupVerifyInfFile failed with error 0x490 for oem9.inf of device PCI\VEN_1033&DEV_00E0&SUBSYS_00322027&REV_02\3&61AAA01&0&4A

20.047: Third Party Provider = VIA Technologies, Inc. for PCI\VEN_1106&DEV_3177&SUBSYS_00000000&REV_00\3&61AAA01&0&88

22.156: SetupVerifyInfFile failed with error 0x490 for oem14.inf of device ROOT\ACRONISDEVICES\0000

22.484: Failed to query DriverPath of ROOT\LEGACY_AFD\0000 0x2

22.484: Failed to query DriverPath of ROOT\LEGACY_AVG7RSW\0000 0x2

22.484: Failed to query DriverPath of ROOT\LEGACY_AVGCORE\0000 0x2

22.484: Failed to query DriverPath of ROOT\LEGACY_AVGFSH\0000 0x2

22.484: Failed to query DriverPath of ROOT\LEGACY_BEEP\0000 0x2

22.484: Failed to query DriverPath of ROOT\LEGACY_BTKRNL\0000 0x2

22.484: Failed to query DriverPath of ROOT\LEGACY_BTSERIAL\0000 0x2

22.484: Failed to query DriverPath of ROOT\LEGACY_BTSLBCSP\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_DMBOOT\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_DMLOAD\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_FIPS\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_GPC\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_HTTP\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_IP6FW\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_IPNAT\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_IPSEC\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_KSECDD\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_MNMDD\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_MOUNTMGR\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_NDIS\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_NDISTAPI\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_NDISUIO\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_NDPROXY\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_NETBT\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_NTSIM\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_NULL\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_NWLNKIPX\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_NWLNKNB\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_NWLNKSPX\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_PARTMGR\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_PARVDM\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_RASACD\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_RDPCDD\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_RDPWD\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_SDR2EPPB\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_SIFILTER\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_TCPIP\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_TCPIP6\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_TDPIPE\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_TDTCP\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_TFFSPORT\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_TMPREFLT\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_VGASAVE\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_VIAAGP\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_VOLSNAP\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_WANARP\0000 0x2

22.500: Failed to query DriverPath of ROOT\LEGACY_WS2IFSL\0000 0x2

24.984: SetupVerifyInfFile failed with error 0x490 for c:\windows\inf\oem25.inf of device ROOT\NET\0000

25.234: SetupVerifyInfFile failed with error 0x490 for c:\windows\inf\oem25.inf of device ROOT\NET\0002

25.594: SetupVerifyInfFile failed with error 0x490 for c:\windows\inf\oem26.inf of device ROOT\PORTS\0000

25.922: SetupVerifyInfFile failed with error 0x490 for c:\windows\inf\oem26.inf of device ROOT\PORTS\0002

26.234: SetupVerifyInfFile failed with error 0x490 for c:\windows\inf\oem26.inf of device ROOT\PORTS\0003

38.172: SetupVerifyInfFile failed with error 0x490 for oem15.inf of device USB\VID_066B&PID_400B\5&14B326C8&0&2

38.500: SetupVerifyInfFile failed with error 0x490 for oem15.inf of device USB\VID_066B&PID_400B\9A8A67

38.844: SetupVerifyInfFile failed with error 0x490 for oem15.inf of device USB\VID_066B&PID_400B\9A8ACD

43.219: C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem57.CAT trusts inf c:\windows\inf\oem57.inf of device USB\VID_0BB4&PID_0B01\5&14B326C8&0&1

43.609: C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem57.CAT trusts inf c:\windows\inf\oem57.inf of device USB\VID_0BB4&PID_0B01\5&14B326C8&0&3

44.015: C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem57.CAT trusts inf c:\windows\inf\oem57.inf of device USB\VID_0BB4&PID_0B01\5&A63631E&0&1

46.734: SetupVerifyInfFile failed with error 0x490 for oem9.inf of device USB2\ROOT_HUB20\4&275894C5&0

51.687: OEM file scan used 49890 ticks

51.750: AnalyzePhaseOne: used 49953 ticks

51.750: AnalyzeComponents: Hotpatch analysis disabled; skipping.

51.750: AnalyzeComponents: Hotpatching is disabled.

51.750: AnalyzePhaseTwo used 0 ticks

51.750: AnalyzePhaseThree used 0 ticks

51.750: AnalyzePhaseFive used 0 ticks

51.765: AnalyzePhaseSix used 15 ticks

51.765: AnalyzeComponents used 49968 ticks

51.765: Downloading 0 files

51.765: bPatchMode = FALSE

51.765: Inventory complete: ReturnStatus=0, 49968 ticks

51.765: Num Ticks for invent : 49968

51.765: Allocation size of drive C: is 4096 bytes, free space = 7050510336 bytes

51.765: Drive C: free 6723MB req: 5MB w/uninstall 0MB

51.765: CabinetBuild complete

51.765: Num Ticks for Cabinet build : 0

51.765: DynamicStrings section not defined or empty.

51.765: FileInUse:: need to restart already, turn off

51.765: FileInUse:: Add to list - Service Name: msiserver

51.765: StopServices: OpenService failed :0x424

52.781: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed: 0xe0000102

65.906: System Restore Point set.

65.984: PFE2: Not avoiding Per File Exceptions.

66.172: DoInstallation: Installing assemblies with source root path: g:\0797be65586d454786c05f203b809b74\

66.172: Num Ticks for Copying files : 14407

66.172: Num Ticks for Reg update and deleting 0 size files : 0

66.172: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is empty; nothing to do.

72.140: RebootNecessary = 0,WizardInput = 0 , DontReboot = 1, ForceRestart = 0

Any help greatly recieved with the seasons best wishes!

[charleyjr]

:) Thanks for the suggestions. Microsoft gave me some complcated scheme to follow, which I used in part. Apparently all that was really needed is to right-click on HKEY_CLASSES_ROOT in regedit, and add my user name in Special permissions.

It was one of those weird experiences where I half-guessed what to change, and I'm not completely sure just what I did.

I don't really understand why this was needed -- since I am the only user and Administrator. I guess it was some side-effect of doing the in place Service Pack 2 upgrade. Some old and some new settings were mixed ?

All is well now, except either the Registry tinkering or some of the new patches messed up a few programs that were already installed. Fortunately I had some needed files saved to CD and reinstall took care of the rest. :laugh:

[datababe]

I joined here just now specifically to say !THANK YOU! - the clues I found in this thread helped solve the same issue on a client's computer that's had us chasing our tails all morning.

I've no doubt I will find more lifesavers here ;-) and hope at some point I can give back at least a little.

Should have guessed a fix would wind up involving my least favorite registry branch (how do I hate thee HKCR, let me count the ways...).

DB

[+Frank B. Subscriber²]

I joined here just now specifically to say !THANK YOU! - the clues I found in this thread helped solve the same issue on a client's computer that's had us chasing our tails all morning.

I've no doubt I will find more lifesavers here ;-) and hope at some point I can give back at least a little.

Should have guessed a fix would wind up involving my least favorite registry branch (how do I hate thee HKCR, let me count the ways...).

DB

You'll find a lot of valuable technical information on these forums. Welcome.

[jason13524]

Use Windows installer 4.5

http://support.microsoft.com/kb/942288