I have an application that needs to upgrade itself, so it runs an MSI that installs the application while the application is still running. For years that has worked successfully, despite the .exe's, .dll's and other things being in use the installer works without a problem. However I am now installing the CEF browser component and this is causing me trouble.
This is an example from the installer log:
*** the file is scheduled for removal
MSI (s) (9C:7C) [11:44:06:372]: Executing op: FileRemove(,FileName=cef.pak,,ComponentId={AEDD9CDD-C5CB-4260-A5D5-A7C13011CC97})
MSI (s) (9C:7C) [11:44:06:374]: Verifying accessibility of file: cef.pak
MSI (s) (9C:7C) [11:44:06:374]: Verifying accessibility of file: cef.pak
MSI (s) (9C:7C) [11:44:06:374]: Using source file security for destination.
MSI (s) (9C:7C) [11:44:06:375]: Note: 1: 2318 2: C:\Config.Msi\144c57.rbf
MSI (s) (9C:7C) [11:44:06:390]: Note: 1: 2329 2: 32 3: C:\xxxx\cef.pak
MSI (s) (9C:7C) [11:44:06:390]: Verifying accessibility of file: cef.pak
MSI (s) (9C:7C) [11:44:06:393]: Executing op: FileRemove(,FileName=cef_100_percent.pak,,ComponentId={AEDD9CDD-C5CB-4260-A5D5-A7C13011CC97})
Info 1903. Scheduling reboot operation: Deleting file C:\xxxx\cef.pak. Must reboot to complete operation.
*** The file is not overwritten and it sees the files as the same
MSI (s) (9C:30) [11:44:09:050]: Executing op: FileCopy(SourceName=cef.pak,SourceCabKey=cef.pak,DestName=cef.pak,Attributes=512,FileSize=1961473,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPart1=885556701,HashPart2=2067920947,HashPart3=-336625845,HashPart4=-1380829775,,)
MSI (s) (9C:30) [11:44:09:056]: File: C:\xxxxcef.pak; Won't Overwrite; Won't patch; Existing file is unversioned and unmodified - hash matches source file
So the installer tries to remove the file, knows it is in use and schedules a remove after the reboot. But then it sees if it should install the file, sees it is already there (it hasn't been removed yet) and decides to not do anything. So after the reboot the file is gone and the application fails.
I tried setting the installer to always replace the file with:
<Property Id='REINSTALLMODE' Value='amus'/>
On Windows 7 this produces the desired behaviour, the file is seen as being in use, the new one is copied to a temporary location and a rename scheduled for after a reboot and delete.
Line 1525: MSI (s) (CC:64) [12:19:41:201]: The file represented by File table key 'cef.pak' has no eligible binary patches
Line 2618: MSI (s) (CC:64) [12:19:41:775]: Executing op: FileRemove(,FileName=cef.pak,,ComponentId={AEDD9CDD-C5CB-4260-A5D5-A7C13011CC97})
Line 2619: MSI (s) (CC:64) [12:19:41:776]: Verifying accessibility of file: cef.pak
Line 2620: MSI (s) (CC:64) [12:19:41:776]: Verifying accessibility of file: cef.pak
Line 2622: MSI (s) (CC:64) [12:19:41:779]: Note: 1: 2329 2: 32 3: C:\xxx\cef.pak
Line 2623: MSI (s) (CC:64) [12:19:41:779]: Verifying accessibility of file: cef.pak
Line 2625: Info 1903. Scheduling reboot operation: Deleting file C:\xxx\cef.pak. Must reboot to complete operation.
Line 3382: MSI (s) (CC:68) [12:19:42:632]: The file represented by File table key 'cef.pak' has no eligible binary patches
Line 3801: MSI (s) (CC:68) [12:19:42:933]: Executing op: FileCopy(SourceName=cef.pak,SourceCabKey=cef.pak,DestName=cef.pak,Attributes=512,FileSize=1961473,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=62914560,HashOptions=0,HashPart1=885556701,HashPart2=2067920947,HashPart3=-336625845,HashPart4=-1380829775,,)
Line 3801: MSI (s) (CC:68) [12:19:42:933]: Executing op: FileCopy(SourceName=cef.pak,SourceCabKey=cef.pak,DestName=cef.pak,Attributes=512,FileSize=1961473,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=62914560,HashOptions=0,HashPart1=885556701,HashPart2=2067920947,HashPart3=-336625845,HashPart4=-1380829775,,)
Line 3801: MSI (s) (CC:68) [12:19:42:933]: Executing op: FileCopy(SourceName=cef.pak,SourceCabKey=cef.pak,DestName=cef.pak,Attributes=512,FileSize=1961473,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=62914560,HashOptions=0,HashPart1=885556701,HashPart2=2067920947,HashPart3=-336625845,HashPart4=-1380829775,,)
Line 3802: MSI (s) (CC:68) [12:19:42:939]: File: C:\xxx\cef.pak; Overwrite; Won't patch; REINSTALLMODE specifies all files to be overwritten
Line 3803: MSI (s) (CC:68) [12:19:42:939]: Source for file 'cef.pak' is compressed
Line 3805: MSI (s) (CC:68) [12:19:43:713]: Verifying accessibility of file: cef.pak
Line 3806: MSI (s) (CC:68) [12:19:43:713]: Verifying accessibility of file: cef.pak
Line 3808: MSI (s) (CC:68) [12:19:43:717]: Note: 1: 2329 2: 32 3: C:\xxx\cef.pak
Line 3809: MSI (s) (CC:68) [12:19:43:717]: Verifying accessibility of file: cef.pak
Line 3810: Info 1603. The file C:\xxx\cef.pak is being held in use. Close that application and retry.
Line 3811: Info 1903. Scheduling reboot operation: Deleting file C:\xxx\cef.pak. Must reboot to complete operation.
Line 3812: Info 1902. Scheduling reboot operation: Renaming file C:\xxx\TBMBFB2.tmp to C:\xxx\cef.pak. Must reboot to complete operation.
In Windows 10 however this does not occur, it tries to immediately replace the file without using the temporary file and it therefore fails.
cef.pak
Line 1895: MSI (s) (88:8C) [12:07:12:133]: The file represented by File table key 'cef.pak' has no eligible binary patches
Line 3011: MSI (s) (88:8C) [12:07:13:761]: Executing op: FileRemove(,FileName=cef.pak,,ComponentId={AEDD9CDD-C5CB-4260-A5D5-A7C13011CC97})
Line 3012: MSI (s) (88:8C) [12:07:13:763]: Verifying accessibility of file: cef.pak
Line 3013: MSI (s) (88:8C) [12:07:13:764]: Verifying accessibility of file: cef.pak
Line 3016: MSI (s) (88:8C) [12:07:13:782]: Note: 1: 2329 2: 32 3: c:\xxx\cef.pak
Line 3017: MSI (s) (88:8C) [12:07:13:782]: Verifying accessibility of file: cef.pak
Line 3019: Info 1903. Scheduling reboot operation: Deleting file c:\xxx\cef.pak. Must reboot to complete operation.
Line 3747: MSI (s) (88:8C) [12:07:16:042]: The file represented by File table key 'cef.pak' has no eligible binary patches
Line 4322: MSI (s) (88:8C) [12:07:16:577]: Executing op: FileCopy(SourceName=cef.pak,SourceCabKey=cef.pak,DestName=cef.pak,Attributes=512,FileSize=1961473,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=62914560,HashOptions=0,HashPart1=885556701,HashPart2=2067920947,HashPart3=-336625845,HashPart4=-1380829775,,)
Line 4322: MSI (s) (88:8C) [12:07:16:577]: Executing op: FileCopy(SourceName=cef.pak,SourceCabKey=cef.pak,DestName=cef.pak,Attributes=512,FileSize=1961473,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=62914560,HashOptions=0,HashPart1=885556701,HashPart2=2067920947,HashPart3=-336625845,HashPart4=-1380829775,,)
Line 4322: MSI (s) (88:8C) [12:07:16:577]: Executing op: FileCopy(SourceName=cef.pak,SourceCabKey=cef.pak,DestName=cef.pak,Attributes=512,FileSize=1961473,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=62914560,HashOptions=0,HashPart1=885556701,HashPart2=2067920947,HashPart3=-336625845,HashPart4=-1380829775,,)
Line 4323: MSI (s) (88:8C) [12:07:16:584]: File: c:\xxx\cef.pak; Overwrite; Won't patch; REINSTALLMODE specifies all files to be overwritten
Line 4324: MSI (s) (88:8C) [12:07:16:584]: Source for file 'cef.pak' is compressed
Line 4325: MSI (s) (88:8C) [12:07:16:585]: Re-applying security from existing file.
Line 4326: MSI (s) (88:8C) [12:07:21:645]: Verifying accessibility of file: cef.pak
Line 4327: MSI (s) (88:8C) [12:07:21:647]: Using source file security for destination.
Line 4328: MSI (s) (88:8C) [12:07:21:647]: Note: 1: 2318 2: C:\Config.Msi\a5880.rbf
Line 4329: MSI (s) (88:8C) [12:07:21:651]: Note: 1: 1310 2: 0 3: c:\xxx\cef.pak
Line 4330: Info 1603. The file c:\xxx\cef.pak is being held in use. Close that application and retry.
Line 4331: MSI (s) (88:8C) [12:07:21:652]: Product: XXX-- Error 1310. Error writing to file: c:\xxx\cef.pak. System error 0. Verify that you have access to that directory.
Line 4332:
Line 4333: Error 1310. Error writing to file: c:\xxx\cef.pak. System error 0. Verify that you have access to that directory.
Line 4334: MSI (s) (88:8C) [12:07:21:683]: Note: 1: 2265 2: 3: -2147287035
Line 4335: MSI (s) (88:8C) [12:07:21:684]: User policy value 'DisableRollback' is 0
Line 4336: MSI (s) (88:8C) [12:07:21:684]: Machine policy value 'DisableRollback' is 0
Line 4337: Action ended 12:07:21: InstallFinalize. Return value 3.
Line 4347: MSI (s) (88:8C) [12:07:21:713]: Executing op: FileCopy(SourceName=C:\Config.Msi\a5880.rbf,,DestName=c:\xxx\cef.pak,Attributes=32,FileSize=0,PerTick=0,,VerifyMedia=0,ElevateFlags=3,,,,,,,InstallMode=4194304,,,,,,,)
Line 4348: MSI (s) (88:8C) [12:07:21:713]: File: c:\xxx\cef.pak; Overwrite; Won't patch; REINSTALLMODE specifies all files to be overwritten
Line 4349: MSI (s) (88:8C) [12:07:21:715]: Re-applying security from existing file.
Line 4350: MSI (s) (88:8C) [12:07:21:718]: Note: 1: 2318 2:
Line 4351: MSI (s) (88:8C) [12:07:21:720]: Verifying accessibility of file: cef.pak
Line 4352: MSI (s) (88:8C) [12:07:21:722]: Using source file security for destination.
Line 4353: MSI (s) (88:8C) [12:07:21:722]: Note: 1: 2318 2: C:\Config.Msi\a5881.rbf
Line 4354: MSI (s) (88:8C) [12:07:21:735]: File will have security applied from OpCode.
Line 4355: MSI (s) (88:8C) [12:07:21:737]: Note: 1: 1310 2: 32 3: c:\xxx\cef.pak
Line 4356: Info 1603. The file c:\xxx\cef.pak is being held in use. Close that application and retry.
Line 4357: MSI (s) (88:8C) [12:07:21:737]: Error in rollback skipped. Return: 3
Line 4358: Info 1310. Error writing to file: c:\xxx\cef.pak. System error 32. Verify that you have access to that directory.
Is there a way to get that behaviour for other types of files (e.g .pak files)?
CEF Browser: I am not familiar with this component. Does it run in-process? (as a dll) - or does it have an API-call to shut itself down? Could you try to implement the Windows Restart Manager "RegisterApplicationRestart" feature described below for your main executable? Or you can call shutdown in a custom action for the component if there is an API?
Data File: Also, is this a data file that you should not install at all, but rather let the component itself create on launch? If this is the case you can remove the file from the installer and avoid it being entangled with your installer at all? This is particularly preferable for unversioned files - which can be hard to update beacuse of the MSI file overwrite rules / file versioning rules.
Restart Manager: Windows Installer supports what is referred to as a Restart Manager feature. The idea is to have the application shut itself down gracefully during installation - releasing all file and resource locks - and then to have Windows Installer restart it again after all files have been updated. This means that the application itself will take care of its own shutdown and restart when told to do so: "shut yourself down and restart when told" (saving all data and ideally the exact state). Only the application itself can know how to do this properly?
Technical Support: This is a technical article on how to implement support for the Restart Manager feature in your application - from Advanced Installer, makers of leading deployment tools. It is a nice article: https://www.advancedinstaller.com/user-guide/qa-vista-restart-manager.html
HRESULT WINAPI RegisterApplicationRestart(PCWSTR pwzCommandline, DWORD dwFlags);
The whole idea is basically to prefer restarting applications rather than restarting the OS - and also to avoid reboots in general. To that end: 1) Your application calls RegisterApplicationRestart() with a command line specified for its eventual restart - it "signs up" for restart management. 2) Your application watches for WM_QUERYENDSESSION messages and shuts down gracefully saving data in an appropriate way when told to do so. 3) Then Restart Manager can restart the application when finished installing (restart can be disabled).
Links:
Restart Manager and rebooting
Restart Manager guidelines for applications
I am using Win10 and developed an app which has setup project(with VS2013). It can be installed to win7 but cannot be installed to win10. Is there any settings on setup projects on the visual studio?
Update:
msiexec log is:
Action start 13:34:52: ExecuteAction.
MSI (c) (38:14) [13:34:52:291]: PROPERTY CHANGE: Adding SECONDSEQUENCE
property. Its value is '1'.
MSI (c) (38:14) [13:34:52:291]: Grabbed execution mutex.
MSI (c) (38:14) [13:34:52:291]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (c) (38:14) [13:34:52:291]: Switching to server: TARGETDIR="C:\Users\xxx\AppData\Local\PathFolder\ProjectSetup\" VSDNETURLMSG="This setup requires the .NET Framework version 4.5.
Please install the .NET Framework and run this setup again. The .NET Framework can be obtained from the web. Would you like to do this now?" VSDNETMSG="This setup requires the .NET Framework version 4.5.
Please install the .NET Framework and run this setup again." CURRENTDIRECTORY="C:\Users\xxx\Winform\ProjectSetup\Release" CLIENTUILEVEL="0" CLIENTPROCESSID="3384" USERNAME="Windows User"
SOURCEDIR="C:\Users\xxx\Winform\ProjectSetup\Release\" ACTION="INSTALL" EXECUTEACTION="INSTALL" ROOTDRIVE="F:\" INSTALLLEVEL="1" SECONDSEQUENCE="1" ADDLOCAL=DefaultFeature
MSI (s) (18:84) [13:34:52:304]: Running installation inside multi-package transaction C:\Users\xxx\Winform\ProjectSetup\Release\ProjectSetup.msi
MSI (s) (18:84) [13:34:52:304]: Grabbed execution mutex.
MSI (s) (18:6C) [13:34:52:307]: MainEngineThread is returning 1603
MSI (s) (18:84) [13:34:52:313]: User policy value 'DisableRollback' is 0
MSI (s) (18:84) [13:34:52:313]: Machine policy value 'DisableRollback' is 0
MSI (s) (18:84) [13:34:52:313]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (18:84) [13:34:52:313]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (18:84) [13:34:52:316]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (18:84) [13:34:52:316]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (38:14) [13:34:52:317]: Back from server. Return value: 1603
MSI (c) (38:14) [13:34:52:317]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (38:14) [13:34:52:317]: PROPERTY CHANGE: Deleting SECONDSEQUENCE property. Its current value is '1'.
Action ended 13:34:52: ExecuteAction. Return value 3.
MSI (c) (38:14) [13:34:52:317]: Doing action: FatalErrorForm
Action 13:34:52: FatalErrorForm.
Action start 13:34:52: FatalErrorForm.
MSI (c) (38:14) [13:34:52:317]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'FatalErrorForm'
DEBUG: Error 2826: Control Line1 on dialog FatalErrorForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: FatalErrorForm, Line1, to the right
DEBUG: Error 2826: Control Line2 on dialog FatalErrorForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: FatalErrorForm, Line2, to the right
DEBUG: Error 2826: Control BannerBmp on dialog FatalErrorForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: FatalErrorForm, BannerBmp, to the right
Action 13:34:52: FatalErrorForm. Dialog created
Action ended 13:34:53: FatalErrorForm. Return value 1.
Action ended 13:34:53: INSTALL. Return value 3.
MSI (c) (38:14) [13:34:53:273]: Destroying RemoteAPI object.
MSI (c) (38:88) [13:34:53:273]: Custom Action Manager thread ending.
=== Logging stopped: 6.05.2019 13:34:53 ===
MSI (c) (38:14) [13:34:53:280]: Note: 1: 1708
MSI (c) (38:14) [13:34:53:280]: Product: ProjectSetup -- Installation failed.
MSI (c) (38:14) [13:34:53:280]: Windows Installer installed the product. Product Name: ProjectSetup. Product Version: 1.0.0. Product Language: 1033. Manufacturer: PathFolder. Installation success or error status: 1603.
MSI (c) (38:14) [13:34:53:281]: Grabbed execution mutex.
MSI (c) (38:14) [13:34:53:281]: Cleaning up uninstalled install packages, if any exist
MSI (c) (38:14) [13:34:53:282]: MainEngineThread is returning 1603
=== Verbose logging stopped: 6.05.2019 13:34:53 ===
I have a java desktop application which is using WIX to install the application. At install WIX is creating a folder located in the {...}/AppData/Local folder. The application is then populating this folder with subfolders and files during execution of the application.
We noticed that at uninstall of the application this folder is not removed (if it is populated, if it is empty it is removed via the RemoveFolder elelemt) which leads to unpleasantries.
Reasearch into the matter shows that the RemoveFolder element can only remove empty folders, ie. without subfolders and files. For solving the issue I came up with the solution of executing a batch file with code for removing the whole folder, including sub folders and files, via a Custom Action. I thought of placing this file in the installation path of the application, which is not the same as where the folder I want to remove is placed.
After turning on logging for installing/uninstalling the application I find that this custom action is not executedc in the correct order, ie. it is executed after the installation folder is removed and thereby the batch file is never run.
Here is my WIX InstallExecuteSequence:
<InstallExecuteSequence>
<Custom Action='RemoveAlelionFolder' After="InstallFiles">
Installed AND NOT UPGRADINGPRODUCTCODE
</Custom>
<RemoveExistingProducts After="InstallValidate"/>
</InstallExecuteSequence>
<CustomAction Id='RemoveAlelionFolder' ExeCommand='[INSTALLDIR]remove.bat' Directory="INSTALLDIR" Execute="deferred" Return='asyncNoWait' />
Here are parts of the install/uninstall log file:
Action ended 15:20:21: RemoveShortcuts. Return value 1.
Action start 15:20:21: RemoveFiles.
MSI (s) (8C:BC) [15:20:21:111]: Counted 9 foreign folders to be removed.
MSI (s) (8C:BC) [15:20:21:111]: Removing foreign folder: C:\Users\Public\Desktop\
MSI (s) (8C:BC) [15:20:21:111]: Removing foreign folder: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Company\
MSI (s) (8C:BC) [15:20:21:111]: Removing foreign folder: C:\Users\{username}\AppData\Local\Company\ **<-- This is not working if folder contains files**
MSI (s) (8C:BC) [15:20:21:111]: Removing foreign folder: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Company\
MSI (s) (8C:BC){Removing a lot of folders here}
MSI (s) (8C:BC) [15:20:21:112]: Doing action: RemoveFolders
MSI (s) (8C:BC) [15:20:21:112]: Note: 1: 2205 2: 3: ActionText
Action ended 15:20:21: RemoveFiles. Return value 1.
Action start 15:20:21: RemoveFolders.
MSI (s) (8C:BC) [15:20:21:113]: Doing action: CreateFolders
MSI (s) (8C:BC) [15:20:21:113]: Note: 1: 2205 2: 3: ActionText
Action ended 15:20:21: RemoveFolders. Return value 1.
Action start 15:20:21: CreateFolders.
MSI (s) (8C:BC) [15:20:21:114]: Doing action: InstallFiles
MSI (s) (8C:BC) [15:20:21:114]: Note: 1: 2205 2: 3: ActionText
Action ended 15:20:21: CreateFolders. Return value 1.
MSI (s) (8C:BC)
MSI (s) (8C:BC) [15:20:21:118]: Note: 1: 2205 2: 3: Patch
MSI (s) (8C:BC) [15:20:21:118]: Note: 1: 2228 2: 3: Patch 4: SELECT `Patch`.`File_`, `Patch`.`Header`, `Patch`.`Attributes`, `Patch`.`Sequence`, `Patch`.`StreamRef_` FROM `Patch` WHERE `Patch`.`File_` = ? AND `Patch`.`#_MsiActive`=? ORDER BY `Patch`.`Sequence`
MSI (s) (8C:BC) [15:20:21:118]: Note: 1: 2205 2: 3: MsiSFCBypass
MSI (s) (8C:BC) [15:20:21:118]: Note: 1: 2228 2: 3: MsiSFCBypass 4: SELECT `File_` FROM `MsiSFCBypass` WHERE `File_` = ?
MSI (s) (8C:BC) [15:20:21:118]: Note: 1: 2205 2: 3: MsiPatchHeaders
MSI (s) (8C:BC) [15:20:21:118]: Note: 1: 2228 2: 3: MsiPatchHeaders 4: SELECT `Header` FROM `MsiPatchHeaders` WHERE `StreamRef` = ?
Action start 15:20:21: InstallFiles.
MSI (s) (8C:BC) [15:20:21:118]: Doing action: RemoveAlelionFolder **<-- Here is action for removing folder w/ files**
MSI (s) (8C:BC) [15:20:21:118]: Note: 1: 2205 2: 3: ActionText
Action ended 15:20:21: InstallFiles. Return value 1.
Action start 15:20:21: RemoveAlelionFolder.
MSI (s) (8C:BC) [15:20:21:119]: Doing action: CreateShortcuts
MSI (s) (8C:BC) [15:20:21:119]: Note: 1: 2205 2: 3: ActionText
Some research effort:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Removing-Folders-td703071.html
Removing files when uninstalling WiX
How to add a WiX custom action that happens only on uninstall (via MSI)?
https://stackoverflow.com/questions/320921/how-to-add-a-wix-custom-action-that-happens-only-on-uninstall-via-msi
Solved!
I had to run the Custom Action 'After='InstallInitialize' in order for it to run at the correct place in the flow of the code.
<InstallExecuteSequence>
<Custom Action='RemoveAlelionFolder' After="InstallInitialize">
Installed AND NOT UPGRADINGPRODUCTCODE
</Custom>
<RemoveExistingProducts After="InstallValidate"/>
</InstallExecuteSequence>
I have recently installed Visual Studio 2013. After a couple of weeks I found thousands of MSI*.LOG files had been created in my C:\Windows\Temp directory - almost 30Gb worth. Each file is virtually the same and is about 3.1Mb. It appears to be installing the same thing over and over. I can delete all of the files, but they start to reappear almost immediately. I have placed a snippet of one of the files below. I am new to posting on StackOverflow so I'm not sure if I need to put more of the file or all of the file or what. I found 2 other articles on the internet suggesting issues with VS2013 so I have gone through the Repair process as well as uninstalling/reinstalling VS2013. I did notice that after I uninstalled VS2013 that no more files were created, but they started to appear again after I reinstalled VS2013.
I didn't receive any errors during VS2013 installation. I am able to create new solutions/projects and everything seems to compile/build just fine so I am at a loss as to what the problem could be.
Has anyone seen this issue? Is there a resolution that solves the problem? I'm looking for something other than just "clean up the files every night"!
=== Verbose logging started: 12/1/2014 12:29:41 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscorsvw.exe ===
MSI (c) (9C:18) [12:29:41:414]: Resetting cached policy values
MSI (c) (9C:18) [12:29:41:414]: Machine policy value 'Debug' is 0
MSI (c) (9C:18) [12:29:41:414]: ******* RunEngine:
******* Product: {9C593464-7F2F-37B3-89F8-7E894E3B09EA}
******* Action:
******* CommandLine: **********
MSI (c) (9C:18) [12:29:41:414]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (9C:18) [12:29:41:414]: Grabbed execution mutex.
MSI (c) (9C:18) [12:29:41:414]: Cloaking enabled.
MSI (c) (9C:18) [12:29:41:414]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (9C:18) [12:29:41:430]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (84:94) [12:29:41:430]: Running installation inside multi-package transaction {9C593464-7F2F-37B3-89F8-7E894E3B09EA}
MSI (s) (84:94) [12:29:41:430]: Grabbed execution mutex.
MSI (s) (84:DC) [12:29:41:430]: Resetting cached policy values
MSI (s) (84:DC) [12:29:41:430]: Machine policy value 'Debug' is 0
MSI (s) (84:DC) [12:29:41:430]: ******* RunEngine:
******* Product: {9C593464-7F2F-37B3-89F8-7E894E3B09EA}
******* Action:
******* CommandLine: **********
MSI (s) (84:DC) [12:29:41:430]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (84:DC) [12:29:41:445]: SRSetRestorePoint skipped for this transaction.
MSI (s) (84:DC) [12:29:41:445]: End dialog not enabled
MSI (s) (84:DC) [12:29:41:445]: Original package ==> C:\Windows\Installer\4c8872.msi
MSI (s) (84:DC) [12:29:41:445]: Package we're running from ==> C:\Windows\Installer\4c8872.msi
MSI (s) (84:DC) [12:29:41:461]: APPCOMPAT: Uninstall Flags override found.
MSI (s) (84:DC) [12:29:41:461]: APPCOMPAT: Uninstall VersionNT override found.
MSI (s) (84:DC) [12:29:41:461]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (s) (84:DC) [12:29:41:461]: APPCOMPAT: looking for appcompat database entry with ProductCode '{9C593464-7F2F-37B3-89F8-7E894E3B09EA}'.
MSI (s) (84:DC) [12:29:41:461]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (84:DC) [12:29:41:461]: MSCOREE not loaded loading copy from system32
MSI (s) (84:DC) [12:29:41:461]: Opening existing patch 'C:\Windows\Installer\3007d0.msp'.
MSI (s) (84:DC) [12:29:41:461]: Opening existing patch 'C:\Windows\Installer\2fe190.msp'.
MSI (s) (84:DC) [12:29:41:461]: Opening existing patch 'C:\Windows\Installer\20c3cd.msp'.
MSI (s) (84:DC) [12:29:41:477]: Opening existing patch 'C:\Windows\Installer\20c3cc.msp'.
MSI (s) (84:DC) [12:29:41:477]: SequencePatches starts. Product code: {9C593464-7F2F-37B3-89F8-7E894E3B09EA}, Product version: 12.0.21005, Upgrade code: {015856DA-C69D-3EE0-85EC-270367A147A1}, Product language 1033
MSI (s) (84:DC) [12:29:41:477]: SequencePatches returns success.
MSI (s) (84:DC) [12:29:41:477]: Final Patch Application Order:
MSI (s) (84:DC) [12:29:41:477]: {BFB5154E-888D-4D0E-B377-018AF8B74968} -
MSI (s) (84:DC) [12:29:41:477]: {C823005E-3448-3126-A3E5-9B568096F87A} -
MSI (s) (84:DC) [12:29:41:477]: {1B46DFCA-9504-4ACD-AB79-FBC3C899784E} -
MSI (s) (84:DC) [12:29:41:477]: {1F654618-A065-3008-9415-576BB5F0E42D} -
MSI (s) (84:DC) [12:29:41:477]: Machine policy value 'DisablePatch' is 0
MSI (s) (84:DC) [12:29:41:477]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (84:DC) [12:29:41:477]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (84:DC) [12:29:41:477]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (84:DC) [12:29:41:477]: Looking for patch transform: RTM.1
DEBUG: Error 2746: Transform RTM.1 invalid for package C:\Windows\Installer\4c8872.msi. Expected product {7781AFF2-D0BE-364B-B18A-D7DBEF8B712D}, found product {9C593464-7F2F-37B3-89F8-7E894E3B09EA}.
MSI (s) (84:DC) [12:29:41:477]: Skipping validation for patch transform #RTM.1. Will not apply because previous transform was invalid
MSI (s) (84:DC) [12:29:41:477]: Looking for patch transform: RTM.2
1: 2746 2: RTM.1 3: C:\Windows\Installer\4c8872.msi 4: {7781AFF2-D0BE-364B-B18A-D7DBEF8B712D} 5: {9C593464-7F2F-37B3-89F8-7E894E3B09EA}
Thanks!
After running repair from the Visual Studio installer the problem seems to be resolved. I lost some gigs, but there's no more daily fillup.
In my case problem started after installing Update 5 for VS 2013 Community Edition. Repairing didn't resolve the problem.
However, I found this post on Heath Stewart's MSDN Blog and it helped in my case.