Welcome to MSDN Blogs Sign in | Join | Help

Help me help you if you have setup bugs

I've gotten some email questions from customers about setup failures that they've seen on their computers.  Some of them are 1935 errors that match some of the previous blog posts I've written, some are .NET Framework errors, and some are general problems getting some program installed.

I cannot guarantee that I will be able to help solve all setup-related problems you may encounter, but I can guarantee that I will take a look and try to help if I can.  In order to do so I would like to ask that you try to gather some detailed information and send it to me if you contact me via email to aid in troubleshooting and debugging:

  1. As much detail about the error message as possible, including the full text of any error messages
  2. Any troubleshooting steps that you have already tried, including links to any of my other blog posts that you've already tried 
  3. Most importantly - log files from the setup if at all possible

Most setups are Windows Installer MSIs.  For those products, you can enable verbose logging by setting a couple of registry values and then reproducing the problem.  Here are a set of steps you can use to gather a Windows Installer verbose log file:

Important note - some MSI-based setups, including the .NET Framework 2.0, 3.0, 3.5 and higher, will not create log files named %temp%\msi*.log even if using the instructions listed below.  Please see this blog post for more details about why that is the case and also for a list of some products that I know of that use different log file creation logic and the locations of the log files that they create.

  1. Click on the Start menu, choose Run, type cmd and click OK
  2. Run this command in the cmd prompt:  reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer" /v Debug /t REG_DWORD /d 7 /f 
  3. Run this command in the cmd prompt:  reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer" /v Logging /t REG_SZ /d voicewarmupx! /f
  4. Re-run the setup and let it fail one more time
  5. Go to your temporary folder (go to the Start menu, choose Run, and type %temp%)
  6. Locate a file named msi*.log (where * is a randomly generated set of letters and numbers)
  7. Zip the msi*.log file (because it tends to be very large but since it is text it compresses nicely)
  8. Run this command in the cmd prompt:  reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer" /v Debug /f
  9. Run this command in the cmd prompt:  reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer" /v Logging /f

<update date="3/27/2007"> Changed steps to enable/disable verbose logging to not require downloading .reg files from my file server </update>

<update date="2/27/2008"> Added a link to a new blog post with information about some products that create their own verbose log files and therefore do not create %temp%\msi*.log, even when the verbose logging policy is enabled on the system. </update>

 

Published Tuesday, March 29, 2005 8:54 PM by astebner

Comments

Tuesday, March 29, 2005 10:47 PM by Brant Gurganus

# re: Help me help you if you have setup bugs

I don't have a particular issue at the moment, but the most famous setup issue I have seen is the conflict between Acrobat Reader and Windows Journal Viewer such that launching Acrobat Reader triggers a reinstallation of Windows Journal Viewer. When the Journal Viewer was installed via Windows Update instead of separate download, this leads to a near infinite loop since the installation sources are unavailable. If you can shed detailed light on that issue, that'd be great.
Wednesday, March 30, 2005 10:02 AM by Aaron Stebner

# re: Help me help you if you have setup bugs

This type of reinstallation is a Windows Installer feature known as resiliency. Basically it has detected that some part of Windows Journal Viewer is broken and triggers a repair to fix it.

This is very similar to a situation I described in a post a while back regarding the .NET Framework - http://blogs.msdn.com/astebner/archive/2004/08/24/219764.aspx.

Just like Windows Journal Viewer, the .NET Framework is packaged as a self-extracting EXE that you install from the %temp% folder, and that the source location is deleted for after setup completes. So if a resiliency repair is triggered, the installation source is unavailable.

I describe how to locate the installation source for the .NET Framework in my previous post. For other products such as Windows Journal Viewer, you would need to re-download the setup package and save it to your machine and then figure out what command line switches to use to extract it to a local folder. Then you should be able to browse to that folder if a resiliency repair happens, and hopefully the repair will fix the issue.

I say "hopefully" because I have seen cases like this where the repair did not fix the underlying issue for one reason or another, and the machine was essentially stuck in this state. This happened to me recently - I have Windows Messenger since I am running Windows XP SP2, but then I also installed the MSN Messenger 7.0 beta. One of the recent critical updates tried to patch Windows Messenger but did not work correctly because I also had MSN Messenger installed. So I eventually found a Windows Messenger repair getting kicked off every time I tried to send an IM. I couldn't get it fixed by repairing Windows Messenger so I eventually had to uninstall both and then reinstall them.

Thursday, July 14, 2005 10:16 PM by Aaron Stebner's WebLog

# How to silently install MSDN to a non-default location

I got a question from a customer who is trying to use the instructions in this blog post to perform a...
Friday, July 22, 2005 3:37 PM by Jin

# re: Help me help you if you have setup bugs

The link http://astebner.sts.winisp.net/Tools/msidebug.reg.txt is broken 8^(
Tuesday, August 02, 2005 11:51 PM by Aaron Stebner's WebLog

# Visual Studio .NET 2003 and .NET Framework v1.1 log files

The following log files are produced during Visual Studio .NET 2003, .NET Framework 1.1 and J# redistributable...
Tuesday, August 02, 2005 11:52 PM by Aaron Stebner's WebLog

# Visual Studio .NET 2002 and .NET Framework v1.0 log files

The following log files are produced during Visual Studio .NET 2002 and .NET Framework 1.0 setup
Visual...
Saturday, August 13, 2005 5:40 PM by Aaron Stebner's WebLog

# How to log a bug for Visual Studio and .NET Framework setup

The Product Feedback web site can be used to report bugs in Visual Studio, the .NET Framework and other...
Saturday, August 13, 2005 5:56 PM by Aaron Stebner's WebLog

# How to report a bug to Microsoft for Visual Studio and .NET Framework setup

Microsoft has created what I think is a really cool mechanism for customers to report bugs and suggestions...
Tuesday, August 16, 2005 6:23 PM by Abi

# re: Help me help you if you have setup bugs

Hi,

I am having problems trying to install Nokia PC Suite, I receive the following error:
Error 1935
An error occurred during the installation of assemly 'Microsoft.msxmL2, publickeytoken='6bd6b9abf345378f".version="4.20.9818.0" type="win32" processor architechture ="x86" Please refer to help and support for more information. HRESULT: 0x80070002

Following this is get a nokia window pop up saying: Rolling back action

Followed by:
Error 1603 - fatal error during installation; Consult windows installer help msi.chm or MSDN.

I have tried to follow your instructions above but I seem to fail on step one. I don't get an option to select YES to add the keys to the registry. Please help!!

Friday, August 19, 2005 12:17 AM by astebner

# re: Help me help you if you have setup bugs

Abi - can you please try the workarounds for this error that are listed at http://blogs.msdn.com/astebner/archive/2005/02/01/364375.aspx and see if any of them resolve the issue that you are seeing?
Wednesday, August 24, 2005 3:47 PM by Sven

# re: Help me help you if you have setup bugs

I had the same problem. Everything went well after I turned off my spyware shield and firewall.
Tuesday, September 27, 2005 6:38 AM by Tim Whelan

# re: Help me help you if you have setup bugs

Hi,
I am a student beginning my final year dissertation and i am having trouble trying to install Visual Studio .Net 2003 on my NEW pc at home. I have taken a picture of the setup failed screen and the problems it has trying to find log files etc. I have also followed your steps to create a log of the errors when i try to reinstall it. I am just wondering if there is anyy wayi can send the log files to you to have a look at.Thanks in advance
Tim
Tuesday, September 27, 2005 6:41 AM by Tim Whelan

# re: Help me help you if you have setup bugs

my email address is tadhg88@gmail.com by the way..... thanks again
Wednesday, September 28, 2005 12:07 AM by astebner

# re: Help me help you if you have setup bugs

Hi Tim - I will contact you via email so you can send me your log files. I'm sorry you're running into this problem....
Sunday, October 09, 2005 12:45 AM by William

# re: Help me help you if you have setup bugs

I am caught in an infinite loop vortex of some sort, I have tried everything I can to fix my Adobe/Windows Journal Viewer problem and nothing works. I ALWAYS get the same error message even when I point the installer to the MSI file installed to a temp folder, can't fix, can't uninstall can't stand this any longer. Asside from scratching my whole HD, and dealing with Microsoft again about my keys, do you have any suggestions? BTW, your information has been, thus far, the BEST I have found on the entire internet. My compliments to you.
Wednesday, October 12, 2005 1:35 AM by astebner

# re: Help me help you if you have setup bugs

Hi William - I would suggest trying to use the MSI Cleanup Utility to forcibly uninstall the program that is popping up tihs error message asking for the original MSI file in the temp directory (I can't tell from your description whether the broken program is Adobe or Windows Journal Viewer from your description above).

You can find the MSI Cleanup Utility at http://support.microsoft.com/default.aspx?scid=kb;en-us;290301.

After using this tool to uninstall, you should be able to install the product again and hopefully this infinite repair loop will be broken and things will work correctly.

Let me know how it goes for you please. Also, thanks for your feedback on my blog, it is comments like this that keep me going :-)
Monday, October 31, 2005 10:35 AM by Winnie

# re: Help me help you if you have setup bugs

sorry.mine is error 1603 also.but when i was checking my PC,the error also was said that cannot access the net work error 1603.what can i do???
Saturday, January 14, 2006 1:55 PM by Jody

# Link in page problem

After saving msidebug.reg it is saved as a note pad file and there is no option to add it to the reg - I have not worked with regedit in a long time and do not want to make a mistake editing what to do
Sunday, January 15, 2006 5:22 PM by astebner

# re: Help me help you if you have setup bugs

Hi Jody - I have to save the files as text files because my file server will not allow me to save files with the .reg extension. You will need to save the file to your desktop and then rename it from msidebug.reg.txt to msidebug.reg. After you rename it, you will be able to double-click on it and add it to your registry.
Tuesday, February 21, 2006 11:31 PM by Keller

# re: Help me help you if you have setup bugs

The Debug logfile on the XP SP2 workstation I was troubleshooting was WIXTEXT.log instead of MSIxxxx.log. Turned out to be some issue with a German Office XP language pack causing issues with other MSI installed software after the German Office 2003 language pack was installed.
Friday, May 19, 2006 12:25 PM by Alma Rosa

# re: Help me help you if you have setup bugs

j# redistributlable install error just installing Vs net 2003
Friday, May 19, 2006 9:21 PM by astebner

# re: Help me help you if you have setup bugs

Hi Alma - Can you please gather the J# log files listed at http://blogs.msdn.com/astebner/articles/447004.aspx and send them to me at Aaron.Stebner (at) microsoft (dot) com so I can try to take a look and see if I can figure out how to fix this issue on your system?
Monday, July 17, 2006 3:20 PM by johnywhy

# Please Help - Setup Hangs

Hi

Setup hangs about 80% through "Loading installation files"

You can retrieve my log file here:
http://rapidsharing.com/download.php?id=AAA96B60
or
http://tinyurl.com/gqkta

thx
Monday, July 17, 2006 7:03 PM by astebner

# re: Help me help you if you have setup bugs

Hi Johnywhy - I took a look at the log file and I can't find anything in there to indicate why setup is hanging like that.  You are entited to a free technical support case for setup-related issues such as this, so I would suggest contacting Microsoft technical support for further troubleshooting assistance.  I'm sorry I'm not able to be more helpful here.
Tuesday, July 18, 2006 3:03 PM by johnywhy

# Support Incident?

hi
i checked microsoft online support, and only the full paid versions are listed as eligible for support.
http://support.microsoft.com/select/?LN=en-us&x=9&y=9&target=assistance&c1=501
or
http://tinyurl.com/j5eo7

johny
Friday, September 08, 2006 1:26 AM by Aaron Stebner's WebLog

# Case study: How I approach debugging and fixing a setup failure

I received a mail from a customer this week regarding an installation failure that proved to be fairly...
Friday, February 02, 2007 2:25 AM by sharkfish.net » links for 2007-02-02

# sharkfish.net &raquo; links for 2007-02-02

PingBack from http://www.sharkfish.net/fish/?p=2035

Friday, April 06, 2007 12:13 PM by Aaron Ruckman's Web Log

# How to help us help you - link to Aaron Stebner's blog

To collect the logs please follow the steps found on aaronste’s blog: http://blogs.msdn.com/astebner/archive/2005/03/29/help-me-help-you-if-you-have-setup-bugs.asp

Friday, April 06, 2007 12:17 PM by Aaron Ruckman's Web Log

# How to help you help me

To collect the logs please follow the steps found on aaronste’s blog: http://blogs.msdn.com/astebner/archive/2005/03/29/help-me-help-you-if-you-have-setup-bugs.asp

Wednesday, August 08, 2007 8:46 PM by Nick's .NET Travels

# Visual Studio 2008 Beta 2 Installation Issue with Team Explorer

Recently I started rebuilding my personal laptop and made the decision to see whether I could get away

Wednesday, February 27, 2008 9:18 PM by Aaron Stebner's WebLog

# Scenarios where enabling Windows Installer verbose logging does not appear to work

A while back, I posted a list of instructions that can be used to enable Windows Installer verbose logging

Wednesday, February 27, 2008 9:59 PM by Noticias externas

# Scenarios where enabling Windows Installer verbose logging does not appear to work

A while back, I posted a list of instructions that can be used to enable Windows Installer verbose logging

Friday, March 07, 2008 7:54 PM by Aaron Stebner's WebLog

# Updated: what to do if other .NET Framework setup troubleshooting steps do not help

A while back, I posted a set of instructions that can be used to try to resolve .NET Framework installation

Friday, March 07, 2008 8:18 PM by Noticias externas

# Updated: what to do if other .NET Framework setup troubleshooting steps do not help

A while back, I posted a set of instructions that can be used to try to resolve .NET Framework installation

Wednesday, April 09, 2008 6:33 AM by sba

# re: Help me help you if you have setup bugs

I'm hit by the transient resiliency repair window...

All I get in the verbose MSI log is:

=== Verbose logging started: 2008/04/09  11:55:45  Build type: SHIP UNICODE 3.01.4000.4039  Calling process: I:\PROGRA~1\MI1933~1\OFFICE11\WINWORD.EXE ===

MSI (c) (E4:70) [11:55:45:223]: Resetting cached policy values

MSI (c) (E4:70) [11:55:45:223]: Machine policy value 'Debug' is 7

MSI (c) (E4:70) [11:55:45:223]: ******* RunEngine:

          ******* Product: {9AE192E3-7B50-4EF0-9993-3B3280240AD2}

          ******* Action:

          ******* CommandLine:  ADDDEFAULT=_MainFeature

MSI (c) (E4:70) [11:55:45:238]: Client-side and UI is none or basic: Running entire install on the server.

MSI (c) (E4:70) [11:55:45:238]: Grabbed execution mutex.

MSI (c) (E4:70) [11:55:45:801]: Cloaking enabled.

MSI (c) (E4:70) [11:55:45:801]: Attempting to enable all disabled priveleges before calling Install on Server

MSI (c) (E4:70) [11:55:45:847]: Incrementing counter to disable shutdown. Counter after increment: 0

MSI (s) (5C:4C) [11:55:46:160]: Grabbed execution mutex.

MSI (s) (5C:04) [11:55:46:160]: Resetting cached policy values

MSI (s) (5C:04) [11:55:46:175]: Machine policy value 'Debug' is 7

MSI (s) (5C:04) [11:55:46:175]: ******* RunEngine:

          ******* Product: {9AE192E3-7B50-4EF0-9993-3B3280240AD2}

          ******* Action:

          ******* CommandLine:  ADDDEFAULT=_MainFeature CURRENTDIRECTORY="H:\" CLIENTUILEVEL=2  CLIENTPROCESSID=4580

MSI (s) (5C:04) [11:55:46:175]: Machine policy value 'DisableUserInstalls' is 0

MSI (s) (5C:04) [11:55:46:207]: MainEngineThread is returning 1605

MSI (c) (E4:70) [11:55:46:222]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

MSI (c) (E4:70) [11:55:46:222]: MainEngineThread is returning 1605

MSI (c) (E4:C8) [11:55:46:285]: Entering MsiProvideComponentFromDescriptor. Descriptor: ']gAVn-}f(ZXfeAR6.jiHandWritingFiles>Wz_B='plK=LZgdoVXdYG, PathBuf: 127A0C, pcchPathBuf: 127A08, pcchArgsOffset: 127968

MSI (c) (E4:C8) [11:55:46:285]: Machine policy value 'DisableUserInstalls' is 0

MSI (c) (E4:C8) [11:55:46:378]: MsiProvideComponentFromDescriptor is returning: 0

=== Verbose logging stopped: 2008/04/09  11:55:46 ===

Any clue? How do I determine why that product is "needed" by e.g. Word and how to remove that dependency?

P.S. msiexec /x '{9AE192E3-7B50-4EF0-9993-3B3280240AD2}' tells me the product is not installed

Wednesday, April 09, 2008 11:11 AM by astebner

# re: Help me help you if you have setup bugs

Hi Sba - For resiliency repairs like this, I typically look at the application event log first.  There should be 2 warnings logged at the time that you see this repair pop up on your system.  They will be from the source named MsiInstaller.  They should list the product code of the MSI being repaired.  One of the warnings should list the exact component GUID of the component that is being accessed that initiates the health check and the other warning should list the exact component GUID and resource that is missing that triggers the repair.

Hopefully this helps you narrow this down further.

Wednesday, April 30, 2008 8:23 PM by Aaron Stebner's WebLog

# Where to find .NET Framework 2.0 SP1, .NET Framework 3.0 SP1 and .NET Framework 3.5 setup log files

A while back, I posted a list of possible log files for .NET Framework 3.5 and Visual Studio 2008 setup

Tuesday, June 17, 2008 7:09 AM by Nicol@s

# re: Help me help you if you have setup bugs

Hi Aaron,

I'm trying to install a Win32 Shared assembly using IS12. I've got Error 1935.An error occurred during the installation of assembly component.

The HRESULT is 0x800736B5 (The manifest file contains one or more syntax error). I have also a line with "MsiProvideAssembly is returning: 1607"

Regards

Tuesday, June 17, 2008 12:44 PM by astebner

# re: Help me help you if you have setup bugs

Hi Nicol@s - This sounds like a problem with the files that you are adding to your setup and/or a problem with the authoring of your MSI.  I'd suggest checking the syntax of your Win32 assembly manifest first.  Also, error code 1607 means "the component identifier is not registered."  I don't have enough familiarity with InstallShield to know what to suggest to try to resolve that type of error, but it sounds like something with the way you are authoring your components.  Maybe they have an FAQ on their site that could help suggest some fixes, or maybe someone on their forums would be able to suggest some things for you to check in your setup authoring.

Wednesday, June 18, 2008 9:12 AM by Nicol@s

# re: Help me help you if you have setup bugs

Hi Aaron,

I'm not sure there was a syntax error in my manifest. I solved my problem renaming the manifest file (it was not the same name as in the manifest file itself) and changing the publicKeyToken value (it was a wrong value, because I have 3 chained certificates, I do not execute the pktextract on the good one).

Regards

Friday, June 20, 2008 6:06 PM by Aaron Stebner's WebLog

# Mailbag: How to install the Visual Studio 2008 SDK in silent mode

Question: I am attempting to automate the installation of the Visual Studio 2008 SDK , but have not been

Saturday, November 08, 2008 8:22 AM by koksi

# re: Help me help you if you have setup bugs

hi

i try now xx hours to install vcs btw net framework 3.5 sp1

error:

[11/07/08,22:51:43] Microsoft .NET Framework 3.0 SP2 x86: [2] Error: Installation failed for component Microsoft .NET Framework 3.0 SP2 x86. MSI returned error code 1603

i open now dd_dotnetfxinstall and search for value:3

i found that

[11/08/08,03:02:29] Setup.exe: GetGlobalCustomProperty - Property: {2B7DE335-914B-476F-AF77-E9EF03938188} - PropertyName: Component Number - Value: 3

[11/08/08,03:02:29] Setup.exe: GetGlobalCustomProperty - Property: {2B7DE335-914B-476F-AF77-E9EF03938188} - PropertyName: Component Number - Value: 3

i have them around 20times

i olso look on file called MSIdc507 but here i dont find a value 3

thx i realy end of my power about this :(

Saturday, November 08, 2008 1:13 PM by astebner

# re: Help me help you if you have setup bugs

Hi Koksi - The file dd_dotnetfxinstall35.txt is not a verbose MSI log, so searching for "return value 3" in that log won't help.  You will need to look at the verbose log file for the .NET Framework 3.0 SP2.  .NET Framework setup configures verbose logging by default, and the logs will be in the locations listed in the blog post at http://blogs.msdn.com/astebner/archive/2008/04/30/8445569.aspx.

Specifically, you will want to look for a log named %temp%\dd_net_framework30*.txt, and then search for "return value 3" in that log.

Hopefully this helps.

Saturday, November 08, 2008 5:29 PM by koksi

# re: Help me help you if you have setup bugs

so now i should have correct file

dd_NET_Framework30_setupFB

at least i saw in that log "Verbose logging stopped"

MSI (s) (7C:8C) [05:12:58:171]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.

MSI (s) (7C:8C) [05:13:07:343]: Note: 1: 2262 2: Error 3: -2147287038

MSI (s) (7C:8C) [05:13:07:343]: Transforming table Error.

from them i have many

MSI (s) (7C:8C) [05:13:07:359]: Attempting to delete file C:\WINDOWS.0\Installer\f6931.msp

MSI (s) (7C:8C) [05:13:07:359]: Unable to delete the file. LastError = 32

(i try to locate this file but could not find them)

i copy them out what i think that could be intresting

exactly that i not find value 3 or value:3

btw i olso tryed msciuu2 cleaning tool and dotnetfx_cleanup_tool olso without success :(

thx for your time

Sunday, November 09, 2008 5:21 PM by astebner

# re: Help me help you if you have setup bugs

Hi Koksi - Could you please zip your .NET Framework log files and post them to a file server (such as skydrive.live.com), and then post a link back here so I can download them and take a look to see if I can figure out what is causing this installation failure on your system?

Monday, November 10, 2008 4:23 PM by koksi

# re: Help me help you if you have setup bugs

hi

realy thx for your time

i upload some fils

www.twisterflasher.net/neterrors.rar

Monday, November 10, 2008 8:21 PM by astebner

# re: Help me help you if you have setup bugs

Hi Koksi - Thanks for posting these log files.  It looks like you're running on a German version of Windows, so you cannot search for the string "return value 3" because that text gets translated in non-English log files.  In your logs, I had to search for "Rückgabewert 3" instead.

Here is the exact error that is causing the failure on your system:

Fehler 1321. Installer besitzt keine ausreichenden Berechtigungen, um diese Datei zu verändern: C:\Programme\Reference Assemblies\Microsoft\Framework\v3.0\System.IdentityModel.dll.

This means that there is some kind of permission problem to one of the folders on your system.  I'd suggest trying the steps listed at http://blogs.msdn.com/astebner/archive/2006/09/04/solving-setup-errors-by-using-the-subinacl-tool-to-repair-file-and-registry-permissions.aspx to try to fix this issue.

Hopefully this helps!

Friday, November 14, 2008 1:43 AM by llhk186

# re: Help me help you if you have setup bugs

Hi Aaron,

I encountered a error when installing the dotnet framework 3.0. I can't find any "return value 3" string in my log file. Would you please take a look on my log file? You can access it from the following link:

http://www.geocities.com/llhk186/MSIbae0f.zip

Many Thanks,

Regards

Friday, November 14, 2008 11:39 AM by astebner

# re: Help me help you if you have setup bugs

Hi Llhk186 - Some products create their own verbose logs by default, and when they do that, using the steps in this blog post to create verbose logs won't work.  There is a link at http://blogs.msdn.com/astebner/archive/2008/02/27/7927123.aspx that you can use to find the names and locations of the log files created by .NET Framework 3.0 setup.  Can you please gather those logs and post them to your file server, then reply back here with a link to the logs so I can take a look and see if I can figure anything out?

Friday, November 21, 2008 4:09 PM by koksi

# re: Help me help you if you have setup bugs

hi

SubInACL tool olso not help me

so i try now to install from a DVD and i could not believe now it work :)

only some error with sql2005 server.. but this i dont need at moment

thx for help

Friday, July 03, 2009 7:16 AM by lulu24

# re: Help me help you if you have setup bugs

Hey there. Can you help?

I'm on Vista SP1, trying to install OpenOffice 3.1 (or any for that matter) and always seem to receive the error "error occurred during installation of assembly 'policy 9.0.Microsoft.VC90.CRT,publicKeyToken=!1fc8b3b9a1e18e3b",version="9.0.21022.8",processorArchitecture="x86",type="win32policy"

I don't quite know what any of this means... I only JUST reinstalled Vista so it can't be a severe problem :|

Any advice?

Monday, July 06, 2009 8:06 PM by astebner

# re: Help me help you if you have setup bugs

Hi Lulu24 - Do you have a full log file from this installation failure?  There are a lot of possible causes for a 1935 error, and the full log usually includes more detailed error information to help narrow down the problem.

This assembly that you list in your error is a VC runtime assembly.  The VC runtime assemblies are Win32 assemblies as opposed to managed assemblies, and on Windows Vista and later, Win32 assemblies are installed by the same infrastructure and engine as OS updates and hotfixes.  This type of error typically means that there is something wrong with the OS update installation engine on the system.

I have posted some information about how I typically go about narrowing down OS update installation problems on Windows Vista and higher in the following blog posts:

http://blogs.msdn.com/astebner/archive/2009/03/12/9472695.aspx

http://blogs.msdn.com/astebner/archive/2009/01/09/9303167.aspx

Hopefully this information will be helpful for you as well.

Anonymous comments are disabled
 
Page view tracker