Help me help you if you have setup bugs

Article
03/29/2005

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:

As much detail about the error message as possible, including the full text of any error messages.
Any troubleshooting steps that you have already tried, including links to any of my other blog posts that you've already tried.
Most importantly - log files from the setup if at all possible. You can zip and upload log files to a file server of your choice and include a link to the log files when you contact me. My preference is https://skydrive.live.com because it is free, gives you a lot of storage space, and doesn't contain annoying ads to try to get you to pay for "premium" services like faster download speeds.

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.

If you are running Windows XP or older: Click on the Start menu, choose Run, type cmd and click OK
If you are running Windows Vista or newer: Click on the Start menu, choose All Programs, then Accessories, then right-click on the item named Command prompt and choose Run as administrator
Copy this command into the cmd prompt and press enter to run it: reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer" /v Debug /t REG_DWORD /d 7 /f
Copy this command into the cmd prompt and press enter to run it: reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer" /v Logging /t REG_SZ /d voicewarmupx! /f
Re-run the setup and let it fail one more time
Go to your temporary folder (go to the Start menu, choose Run, and type %temp%)
Locate a file named msi*.log (where * is a randomly generated set of letters and numbers)
Zip the msi*.log file (because it tends to be very large but since it is text it compresses nicely)
Run this command in the cmd prompt: reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer" /v Debug /f
Run this command in the cmd prompt: reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer" /v Logging /f
Upload the zipped log files to a file server such as https://skydrive.live.com

<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>

<update date="12/2/2010"> Added information about uploading log files to https://skydrive.live.com. </update>

<update date="11/17/2011"> Added clarifications to steps 2 and 3 to indicate that the commands need to be run separately, not as a single command. Also added a note about running as administrator on Windows Vista or later. </update>

Comments

Anonymous
March 29, 2005
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.
Anonymous
March 30, 2005
The comment has been removed
Anonymous
July 14, 2005
I got a question from a customer who is trying to use the instructions in this blog post to perform a...
Anonymous
July 22, 2005
The link http://astebner.sts.winisp.net/Tools/msidebug.reg.txt is broken 8^(
Anonymous
August 02, 2005
The following log files are produced during Visual Studio .NET 2003, .NET Framework 1.1 and J# redistributable...
Anonymous
August 02, 2005
The following log files are produced during Visual Studio .NET 2002 and .NET Framework 1.0 setup
Visual...
Anonymous
August 13, 2005
The Product Feedback web site can be used to report bugs in Visual Studio, the .NET Framework and other...
Anonymous
August 13, 2005
Microsoft has created what I think is a really cool mechanism for customers to report bugs and suggestions...
Anonymous
August 16, 2005
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!!
Anonymous
August 18, 2005
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?
Anonymous
August 24, 2005
I had the same problem. Everything went well after I turned off my spyware shield and firewall.
Anonymous
September 26, 2005
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
Anonymous
September 26, 2005
my email address is tadhg88@gmail.com by the way..... thanks again
Anonymous
September 27, 2005
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....
Anonymous
October 08, 2005
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.
Anonymous
October 11, 2005
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 :-)
Anonymous
October 31, 2005
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???
Anonymous
January 14, 2006
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
Anonymous
January 15, 2006
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.
Anonymous
February 21, 2006
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.
Anonymous
May 19, 2006
j# redistributlable install error just installing Vs net 2003
Anonymous
May 19, 2006
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?
Anonymous
July 17, 2006
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
Anonymous
July 17, 2006
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.
Anonymous
July 18, 2006
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
Anonymous
September 07, 2006
I received a mail from a customer this week regarding an installation failure that proved to be fairly...
Anonymous
February 01, 2007
PingBack from http://www.sharkfish.net/fish/?p=2035
Anonymous
April 06, 2007
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
Anonymous
April 06, 2007
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
Anonymous
August 08, 2007
Recently I started rebuilding my personal laptop and made the decision to see whether I could get away
Anonymous
February 27, 2008
A while back, I posted a list of instructions that can be used to enable Windows Installer verbose logging
Anonymous
February 27, 2008
A while back, I posted a list of instructions that can be used to enable Windows Installer verbose logging
Anonymous
March 07, 2008
A while back, I posted a set of instructions that can be used to try to resolve .NET Framework installation
Anonymous
March 07, 2008
A while back, I posted a set of instructions that can be used to try to resolve .NET Framework installation
Anonymous
April 08, 2008
The comment has been removed
Anonymous
April 09, 2008
The comment has been removed
Anonymous
April 30, 2008
A while back, I posted a list of possible log files for .NET Framework 3.5 and Visual Studio 2008 setup
Anonymous
June 16, 2008
The comment has been removed
Anonymous
June 17, 2008
The comment has been removed
Anonymous
June 18, 2008
The comment has been removed
Anonymous
June 20, 2008
Question: I am attempting to automate the installation of the Visual Studio 2008 SDK , but have not been
Anonymous
November 08, 2008
The comment has been removed
Anonymous
November 08, 2008
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.
Anonymous
November 08, 2008
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.0Installerf6931.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
Anonymous
November 09, 2008
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?
Anonymous
November 10, 2008
hi realy thx for your time i upload some fils www.twisterflasher.net/neterrors.rar
Anonymous
November 10, 2008
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:ProgrammeReference AssembliesMicrosoftFrameworkv3.0System.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!
Anonymous
November 13, 2008
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
Anonymous
November 14, 2008
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?
Anonymous
November 21, 2008
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
Anonymous
July 02, 2009
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?
Anonymous
July 06, 2009
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
July 27, 2009
The comment has been removed
Anonymous
July 28, 2009
The comment has been removed
Anonymous
December 16, 2009
The comment has been removed
Anonymous
December 21, 2009
The comment has been removed
Anonymous
December 23, 2009
Hi Aaron, I posted the question above. I guess you are away for the holidays or just busy. Anyway, just to let you know, I am going to post this question elsewhere for now. I can post a link here if I do find a solution. Merry Christmas, Mike
Anonymous
December 28, 2009
Hi MikeMio - I replied to your original question before I left for a holiday vacation last week. Did the information I provided help at all?
Anonymous
January 03, 2010
Hi Aaron, Sorry, I somehow missed your post before I posted the second time. Not sure how but there you go... Anyway, thank you for the reply. I really do appreciate it. I have been in holiday mode lately and haven't been following but I will read your article, rethink the problem and let you know what I come up with. Hope you had a happy, restful holiday and have a happy and prosperous new year ahead. Cheers, Mike
Anonymous
January 07, 2010
Hi Aaron, Ok, well I have followed your posts and links and I think I know (just barely) what to try next but I wanted to run it by you first if you don't mind. (I have included log snippets below where the installation log timestamp's sync with the cbs.log.) So, reviewing the logs I see that I have the hresult 0x8007371B in both the installation log and the cbs log. 0x8007371B tranlates to: ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE - One or more required members of the transaction are not present. This error is in the list that System Update Readiness Tool says it may fix. So... the next step would be to have the user install and run the System Update Readiness Tool with the hope that that will fix the problem. As I understand it, the Readiness Tool should apear in the Windows update list if the user has an error it can fix but he can manually download and install if it isn't there. Does that sound about right? Is there anything I should do before that? or after? Thanks again for all your help. Cheers, Mike

Start installation log snippet - Vista 64 bit

MSI (s) (F0:04) [09:47:29:931]: Note: 1: 1935 2: {68B7C6D9-1DF2-54C1-A01F-C8B3B9A1E18E} 3: 0x8007371B 4: IAssemblyCacheItem 5: Commit 6: policy.8.0.Microsoft.VC80.MFC,type="win32- policy",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86" MSI (s) (F0:04) [09:47:29:931]: Assembly Error (sxs): To get more diagnostic information, enable the Component Based Servicing Log. MSI (s) (F0:04) [09:47:29:931]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (20:E8) [09:47:29:934]: Note: 1: 2262 2: Error 3: -2147287038 DEBUG: Error 2835: The control ErrorIcon was not found on dialog ErrorDialog The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2835. The arguments are: ErrorIcon, ErrorDialog, Error 1935. An error occurred during the installation of assembly 'policy.8.0.Microsoft.VC80.MFC,type="win32- policy",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"'. Please refer to Help and Support for more information. HRESULT: 0x8007371B. assembly interface: IAssemblyCacheItem, function: Commit, component: {68B7C6D9-1DF2-54C1-A01F-C8B3B9A1E18E} MSI (s) (F0:04) [09:47:33:223]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (F0:04) [09:47:33:223]: Product: SiteSpinner V2 -- Error 1935. An error occurred during the installation of assembly 'policy.8.0.Microsoft.VC80.MFC,type="win32- policy",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"'. Please refer to Help and Support for more information. HRESULT: 0x8007371B. assembly interface: IAssemblyCacheItem, function: Commit, component: {68B7C6D9-1DF2-54C1-A01F-C8B3B9A1E18E} Action ended 9:47:33: InstallFinalize. Return value 3.

End ss.log snippet

Start cbs.log snippet

2010-01-06 09:47:18, Info CBS Loaded Servicing Stack v6.0.6002.18005 with Core: C:Windowswinsxsamd64_microsoft-windows- servicingstack_31bf3856ad364e35_6.0.6002.18005_none_676975d87cc9b6e6cbscore.dll 2010-01-06 09:47:18, Info CSI 00000001@2010/1/6:17:47:18.785 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7feec618c85 @0x7feec8753ae @0x7feec843ed1 @0xffd049a8 @0xffd030c9 @0xffd03578) 2010-01-06 09:47:18, Info CSI 00000002@2010/1/6:17:47:18.803 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7feec618c85 @0x7feec8b86cf @0x7feec8925d9 @0x7feec843feb @0xffd049a8 @0xffd030c9) 2010-01-06 09:47:18, Info CSI 00000003@2010/1/6:17:47:18.805 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7feec618c85 @0x7fef20a838d @0x7fef20a84ba @0xffd04207 @0xffd03125 @0xffd03578) 2010-01-06 09:47:18, Info CBS NonStart: Checking to ensure startup processing was not required. 2010-01-06 09:47:18, Info CSI 00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x133fae0 2010-01-06 09:47:18, Info CBS NonStart: Success, startup processing not required as expected. 2010-01-06 09:47:18, Info SXS Install Assembly from C:WindowsWinSxSInstallTemp20100106094707699.0x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.4053_x- ww_b77cec8e.manifest 2010-01-06 09:47:18, Info SXS Submitting stage transaction with 6 operations 2010-01-06 09:47:18, Info CSI 00000005 Performing 6 operations; 6 are not lock/unlock and follow: Stage (1): flags: 8 app: [Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral]) comp: Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral man: @0x3d06a8 StageFile (2): flags: 8 app: [Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral]) comp: Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral file: [ml:22{11},l:20{10}]"mfcm80.dll" srcfile: @0x3d07c8 StageFile (2): flags: 8 app: [Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral]) comp: Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral file: [ml:22{11},l:20{10}]"mfc80u.dll" srcfile: @0x3d08e8 StageFile (2): flags: 8 app: [Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral]) comp: Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture 2010-01-06 09:47:18, Info CSI neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral file: [ml:20{10},l:18{9}]"mfc80.dll" srcfile: @0x3b9bb8 StageFile (2): flags: 8 app: [Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral]) comp: Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral file: [ml:24{12},l:22{11}]"mfcm80u.dll" srcfile: @0x3b9c48 AddCat (14): flags: 0 catfile: @0x3b9d68 2010-01-06 09:47:18, Info CSI 00000006 Creating NT transaction (seq 1), objectname [6]"(null)" 2010-01-06 09:47:18, Info CSI 00000007 Created NT transaction (seq 1) result 0x00000000, handle @0x220 2010-01-06 09:47:20, Info CSI 00000008@2010/1/6:17:47:20.248 CSI perf trace: CSIPERF:TXCOMMIT;497347 2010-01-06 09:47:20, Info SXS Submitting install transaction 2010-01-06 09:47:20, Info CSI 00000009 Performing 1 operations; 1 are not lock/unlock and follow: Install (5): flags: 0 tlc: [Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral]) ref: ( flgs: 00000000 guid: {27dec61e-b43c-4ac8-88db-e209a8242d90} name: [l:0]"" ncdata: [l:62{31}]"C: Windowssystem32msiexec.exe") thumbprint: [l:128{64}]"57d5c1e17d3b003378ace5418d822c42353f8141380788c095a600def44f4913" 2010-01-06 09:47:20, Info CSI 0000000a Component change list: 2010-01-06 09:47:20, Info CSI 0000000b Creating NT transaction (seq 2), objectname [6]"(null)" 2010-01-06 09:47:20, Info CSI 0000000c Created NT transaction (seq 2) result 0x00000000, handle @0x29c 2010-01-06 09:47:21, Info CSI 0000000d@2010/1/6:17:47:21.080 CSI perf trace: CSIPERF:TXCOMMIT;733104 2010-01-06 09:47:21, Info CSI 0000000e Creating NT transaction (seq 3), objectname [6]"(null)" 2010-01-06 09:47:21, Info CSI 0000000f Created NT transaction (seq 3) result 0x00000000, handle @0x238 2010-01-06 09:47:21, Info CSI 00000010@2010/1/6:17:47:21.514 CSI perf trace: CSIPERF:TXCOMMIT;439235 2010-01-06 09:47:21, Info SXS Install Assembly from C:WindowsWinSxSInstallTemp20100106094710140.08.0.50727.4053.policy 2010-01-06 09:47:21, Info SXS Submitting stage transaction with 2 operations 2010-01-06 09:47:21, Info CSI 00000011 Performing 2 operations; 2 are not lock/unlock and follow: Stage (1): flags: 8 app: [policy.8.0.Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral]) comp: policy.8.0.Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral man: @0x3b9bb8 AddCat (14): flags: 0 catfile: @0x3bb8f8 2010-01-06 09:47:21, Info CSI 00000012 Creating NT transaction (seq 4), objectname [6]"(null)" 2010-01-06 09:47:21, Info CSI 00000013 Created NT transaction (seq 4) result 0x00000000, handle @0x228 2010-01-06 09:47:21, Info CSI 00000014@2010/1/6:17:47:21.830 CSI perf trace: CSIPERF:TXCOMMIT;264532 2010-01-06 09:47:21, Info SXS Submitting install transaction 2010-01-06 09:47:21, Info CSI 00000015 Performing 1 operations; 1 are not lock/unlock and follow: Install (5): flags: 0 tlc: [policy.8.0.Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral]) ref: ( flgs: 00000000 guid: {27dec61e-b43c-4ac8-88db-e209a8242d90} name: [l:0]"" ncdata: [l:62 {31}]"C:Windowssystem32msiexec.exe") thumbprint: [l:128{64}]"81bffdab9f49ea0cc7eea7633b89d1381a501f384fb6e2698d6143ba4951cc8f" 2010-01-06 09:47:21, Info CSI 00000016 Changelist shadowed missing its manifest - policy.8.0.Microsoft.VC80.MFC, Version = 8.0.50727.762, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral 2010-01-06 09:47:21, Error CSI 00000017@2010/1/6:17:47:21.851 (F) d:longhornbasewcpcomponentstorecsd_winners.cpp(953): Error STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE originated in function OriginateManifestsMissingError expression: (null) [gle=0x80004005] 2010-01-06 09:47:26, Error CSI 00000018 (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3162# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd0150024] 2010-01-06 09:47:26, Error CSI 00000019 (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3161# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd0150024] 2010-01-06 09:47:26, Error CSI 0000001a (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3160# from CCSDirectTransaction::ExamineTransaction(...)[gle=0xd0150024] 2010-01-06 09:47:26, Error CSI 0000001b (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3159# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...) [gle=0xd0150024] 2010-01-06 09:47:26, Info CSI 0000001c Changelist shadowed missing its manifest - policy.8.0.Microsoft.VC80.MFC, Version = 8.0.50727.762, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral 2010-01-06 09:47:26, Error CSI 0000001d@2010/1/6:17:47:26.813 (F) d:longhornbasewcpcomponentstorecsd_winners.cpp(953): Error STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE originated in function OriginateManifestsMissingError expression: (null) [gle=0x80004005] 2010-01-06 09:47:29, Error CSI 0000001e (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3315# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd0150024] 2010-01-06 09:47:29, Error CSI 0000001f (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3314# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd0150024] 2010-01-06 09:47:29, Error CSI 00000020 (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3313# from CCSDirectTransaction::GenerateComponentChangeList(...)[gle=0xd0150024] 2010-01-06 09:47:29, Error CSI 00000021 (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3312# from Windows::COM::CPendingTransaction::ExtractInformationFromRtlTransaction(...)[gle=0xd0150024] 2010-01-06 09:47:29, Error CSI 00000022 (F) HRESULT_FROM_WIN32(ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE) #3050# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x8007371b] 2010-01-06 09:47:29, Error SXS Analyze Transaction failed with 0x8007371b 2010-01-06 09:47:38, Info SXS Uninstall Assembly: policy.8.0.Microsoft.VC80.MFC,type="win32- policy",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86" 2010-01-06 09:47:38, Info SXS Submitting uninstall transaction

End cbs.log snippet

Anonymous
January 08, 2010
Hi MikeMio - Yes, I'd suggest trying to download and run the System Update Readiness Tool as a next step here. In some cases, that tool will be able to automatically fix this type of issue. In other cases, it will report the root cause of the problem but may not be able to fix it, and you may need to try to manually fix things by using the log file that this tool creates (located at %windir%logscbschecksur.log). As far as I know, Windows Update will not automatically offer the System Update Readiness Tool if it detects a problem that requires it, so it will have to be downloaded manually. In fact, some of the cases I've seen where this tool is needed can cause Windows Update to not offer any updates at all on a system. Step 3 in the blog post at http://blogs.msdn.com/astebner/archive/2009/01/09/9303167.aspx describes some steps I've used in the past to manually find and fix errors reported by the System Update Readiness Tool, so hopefully this might be helpful to you as well.
Anonymous
January 14, 2010
The comment has been removed
Anonymous
May 14, 2010
We have a program installer made using Wix 3.0 and have recently run into an error on one particular end user's computer, where the install fails when trying to run a MS run time library merge module custom action (SxSInstallCA). The merge modules we include are: "microsoft_vc90_crt_x86.msm" "microsoft_vc90_mfc_x86.msm" "policy_9_0_Microsoft_VC90_CRT_x86.msm" "policy_9_0_Microsoft_VC90_MFC_x86.msm" The funny thing is that this end users computer and install has successfully run other installers which included these merge modules as well. An excerpt of the verbose log output just before and up to the first "return value 3" is as below. I have hunted around and haven't been able to find any clues on how to debug the issue further from here. Any assistance you can provide would be greatly appreciated. -----------start of log excerpt -------------- ... MSI (s) (2C:88) [13:02:29:500]: Doing action: InstallInitialize MSI (s) (2C:88) [13:02:29:500]: Note: 1: 2205 2: 3: ActionText Action 13:02:29: InstallInitialize. Action start 13:02:29: InstallInitialize. MSI (s) (2C:88) [13:02:29:500]: Machine policy value 'AlwaysInstallElevated' is 0 MSI (s) (2C:88) [13:02:29:500]: User policy value 'AlwaysInstallElevated' is 0 MSI (s) (2C:88) [13:02:29:500]: BeginTransaction: Locking Server MSI (s) (2C:88) [13:02:29:500]: Machine policy value 'LimitSystemRestoreCheckpointing' is 0 MSI (s) (2C:88) [13:02:29:500]: Note: 1: 1715 2: CCU 2.4.2 MSI (s) (2C:88) [13:02:29:500]: Note: 1: 2205 2: 3: Error MSI (s) (2C:88) [13:02:29:500]: Note: 1: 2228 2: 3: Error 4: SELECT Message FROM Error WHERE Error = 1715 MSI (s) (2C:88) [13:02:29:500]: Calling SRSetRestorePoint API. dwRestorePtType: 0, dwEventType: 102, llSequenceNumber: 0, szDescription: "Installed CCU 2.4.2". MSI (s) (2C:88) [13:02:33:593]: The call to SRSetRestorePoint API succeeded. Returned status: 0, llSequenceNumber: 904. MSI (s) (2C:88) [13:02:33:593]: Server not locked: locking for product {E67C9725-A794-4BD2-B0EA-986AC036158B} Action ended 13:02:33: InstallInitialize. Return value 1. MSI (s) (2C:88) [13:02:33:640]: Doing action: SxsInstallCA MSI (s) (2C:88) [13:02:33:640]: Note: 1: 2205 2: 3: ActionText Action 13:02:33: SxsInstallCA. Action start 13:02:33: SxsInstallCA. MSI (s) (2C:88) [13:02:33:640]: Creating MSIHANDLE (14) of type 790542 for thread 3720 MSI (s) (2C:40) [13:02:33:640]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI1C.tmp, Entrypoint: CustomAction_SxsMsmInstall MSI (s) (2C:40) [13:02:33:671]: Closing MSIHANDLE (14) of type 790542 for thread 3720 Action ended 13:02:33: SxsInstallCA. Return value 3. -----------end of log excerpt --------------
Anonymous
May 25, 2010
Hi Edgroc – I can’t tell from the verbose log what the problem is in this case, but since it only happens on one computer, I’m guessing there is something wrong with that computer that is causing the VC++ runtime files custom actions to fail and that this problem isn’t specific to your setup package. I would expect to see the standalone VC++ runtime redistributable to fail in the same way, so you may want to have the customer try that to double-check that. If that also fails, then they will likely need to repair their OS to try to resolve this issue. What version of Windows is this error being seen on?
Anonymous
May 26, 2010
Thanks for the feedback. While your blog was undergoing "upgrades", we managed to determine that the .MSI file that the end user was running from was in fact corrupted! This certainly explains why a previous installer with the same VC++ runtime merge modules worked fine and the one in question failed. I thought the MSI files themselves were internally checksummed and this type of error would be caught by the installer engine, but I guess not.
Anonymous
January 03, 2012
when I install Python 2.7 on Windows 7 32 bit, the installation failed and I got this error An error occurred during the installation of assembly 'Microsoft.VC90.CRT, version="9.0.21022.8",publicKey Token="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32". Please refer to Help and Support for more information.
Anonymous
January 03, 2012
Hi Sarhat - For installation issues with Win32 assemblies (like the Visual C++ runtime files) on Windows 7, I suggest using the troubleshooting information and links at blogs.msdn.com/.../9904471.aspx.
Anonymous
May 02, 2012
Hi Aaron, I was pointed to your post on "How to locate the cause of error code 1603 in a verbose MSI log file", and in that post it lead me to this post. I'm wondering if the registry keys and values you mention on this post, are still relevant for Windows 2008 R2 Web Servers?
Anonymous
May 02, 2012
Hi Rod at Work - Yes, these registry keys are applicable to any version of Windows Installer on any version of Windows. They should work fine on Windows Server 2008 R2.
Anonymous
May 11, 2012
Thank you, Aaron.
Anonymous
June 12, 2012
Hi Aaron, I am using C# dll deferred custom action in my setup and it creates below entry in msi log files and writes all properties with 'Ignoring CustomActionData substring' <>, Can you please suggest if there is a way to hide this as this contains password entry as well. Log is added below for your reference.

MSI (s) (1C:34) [00:01:36:125]: Executing op: CustomActionSchedule(Action=cs_CreateService,ActionType=11265,Source=BinaryData,Target=,CustomActionData=) MSI (s) (1C:CC) [00:01:36:140]: Invoking remote custom action. DLL: C:WindowsInstallerMSI21F3.tmp, Entrypoint: m5 InstallShield: Attempting to load through CLR 4 APIs... InstallShield: Getting meta host... InstallShield: Loaded CLR successfully InstallShield: Ignoring CustomActionData substring "C:Program Files (x86)TEST|C:||5|True|False|True|VM134|TEST_DB_CD16|||0|||||2012/06/12 10:29:28||||Testdomainadmin|admin123|||1|1||" InstallShield: Deferred action requested property MsiHiddenProperties not provided by CustomActionData InstallShield: Loading assembly DLPInstall from resource 4097 InstallShield: Calling method with parameters [(System.IntPtr)424, (System.String)TestManager]

Thanks in advance for your help & suggestion. Manish Jain manish1979@gmail.com

Anonymous
June 14, 2012
Hi Manish - The MsiHiddenProperties property is used to control whether or not to show sensitive information in the MSI log file - msdn.microsoft.com/.../aa370308.aspx. I'd suggest taking a look at that documentation to see if that will help you in this scenario.
Anonymous
January 04, 2013
http://sdrv.ms/134Sdm4 there is the file. please help Aaron :/
Anonymous
January 07, 2013
Hi Volkan - Your log looks like it is from an attempt to install the .NET Framework 1.1 on Windows 7. This is the exact error that I see in your log: 1: ERROR: Process returned non-0 value! CMDLINE: "C:windowssystem32URTTEMPregtlib.exe" "C:windowsMicrosoft.NETFrameworkv1.1.4322mscorlib.tlb" I'm not sure what the root cause is for that type of error though. It might help to try the technique described at saranspot.blogspot.com/.../installing-dotnet-framework-11-on.html. If that doesn't help, then I'd suggest posting a question about this issue on the .NET Framework setup forum and hopefully someone there will have some additional suggestions for you to try. You can find this forum at social.msdn.microsoft.com/.../threads.
Anonymous
March 26, 2016
The comment has been removed
- Anonymous
  March 28, 2016
  The comment has been removed

Share via