The MSI " Failed. Uninstall VMware

After I try to delete folders and subfolder and folder file in appdata, but it still cannot install VMware and show pop up these below screenshot. I was tried the solution from VMware base knowledge but the same thing.
Pleas help. Thanks.

Has this been posted to the wrong social.technet forum or am I seeing some strange cross-over? Your post is in the forum "Microsoft Tech Companion for Windows 8." But it appears to be a post on an entirely different topic - installing VMware workstation.
Darrell Webster | webster.net.nz | Twitter/@DarrellCWebster

Similar Messages

MSI Fail error when trying to unininstall VMWare Player 7.

I downloaded the trial version of VMWare Workstation 11. When I do the install it tries to uninstall VMWare Player 7. The uninstall fails with the cryptic error message 'MSI Fail.'
I've found various articles about this around the web and even tried a few 'solutions' to no avail. Is there a sure fire way to uninstall the Player so I can try the Workstation?

I already found the link you posted and followed it but the player is still on my system so VMW still wants to uninstall it and I get the msi fail error. I also tried the manual removal and that didn't work. In fact I wound up breaking some non vmware stuff. Thank heaven for disk images.
Also, the article mentions the file VMware_Install_Cleaner.zip but I can't seem to find it. Is this something that might work to clear up the problem? Too bad I can't just reinstall the player but there is no option for that. I tried a repair but that was a no go too. Also tried deleting files from my Temp folder which some folks claim worked for them.
Also ran the MSI fixit program from MS and while it said it fixed some things about the Player I still couldn't install VMW.

Can I use the MSI Gaming App OC settings in Afterburner then uninstall Gaming Ap

Hello all,
I finally bought an MSI GTX 760 TF OC Gaming Edition GPU last week. Unfortunately the OC isn't programmed into the BIOS and to get the highest Factory OC I need to use the MSI Gaming App. The problem is it does not start with Windows or remember your last Clock Selection.
I know Afterburner can start with Windows and apply your last selected profile.
So can I......
1. Open Gaming App and select OC.
Open GPU-Z and see how much the Clock Speed has increased.
Restore the default Clock (Gaming).
Open Afterburner and apply the same increase to the clock value as the Gaming App gave me.
Save the profile.
Tick the 'Start with Windows' box.
Uninstall the Gaming App.
2. Will the above effectively apply the same OC as the gaming App and therfore make the Gaming App obsolete?
3. Also I've read on some forums that Afterburner will only OC the MSI card if the gaming App is installed. I'm away from home so cannot test any of this. Maybe this was the case with the original version of the gaming app. can anyone confirm?
4. Also I've read people reporting that once the OC has been applied it is locked at this high clock and doesn't downclock when idle. From what I've seen the Gaming App does downclock depending on GPU demand. As does Afterburner. Can anyone confirm?
I don't know why MSI did things this way. It's a Gaming Edition card so there should be a way of applying the factory OC and leaving it set that way. The Gaming App is a nice simple little tool but as a bare minimum they should let us start it with Windows and automatically apply the last selected Clock profile.
Dragging the shortcut into the start-up folder doesn't work for me. And even if it did, the last profile selection is not remembered.
To be honest, the Gaming App is ideal for me but only if I can set it and forget it. There should be a box (like there is in Afterburner) that starts the Gaming App when Windows starts and applies the last Clock profile selected.
Now that would be simple. Afterburner is great and gives you lots of control. But I just want the OC that MSI have created. It should be set at BIOS level for a so-called OC Gaming Edition card.
From the official Afterburner Guide on this forum....
"Another thing which needs to be kept in mind is that maximum clockrates for the latest GeForce GTX7xx Gaming requires running >>Gaming APP<<. Switch to Gaming Mode (N770 TF 2GD5/OC (GeForce GTX 770 GAMING)) or OC Mode (N780 TF 3GD5/OC (GeForce GTX 780 GAMING)) to allow maximum boost clockrates."
Many thanks in advance,

Sure you can set these settings (clock rate etc) in afterburner and you should be good to go. Just for stability, run a benchmark. It should be same OC as Gaming App applies, but GApp might change voltages (never used it so not sure).
Afterburner works with ANY brand's card. However MSI Gaming App not.
However if you change settings in Nvidia control panel in : 3D settings -> Global Settings -> Power management mode -> change from Adaptive to Prefer max performance. After this card will neved downclock even at idle.

After downloading and creating the MSI for Lightroom, the install fails with no errors reported. Checking compatability, windows comes back with not compatible on both win 7 and 8.1.

Installer MSI fails with no error or message of any kind. Tested compatability with the windows compatability check and it comes back as not compatible. What now?

Hans,
It is a known problem on Windows 98, Windows and Windows 2000 if you are using Intel Pentium 4 processor with Sun JRE and Symantec JIT. I had the same problem with Windows 98. Oracle has a patch. Please see Note:131299.1 on metalink for details.

ERROR: An error occurred during the installation of assembly component / ERROR: Third party payload installer Adobe_Lightroom_x64.msi failed with exit code: 1603

During the Installation of LR I get an error message. Initially I didn't have enough space for the installation on the start partition drive. However, now, it should be sufficient and I re-booted the computer a couple of time, hence I would assume that the temporary installation files have been deleted.
Now, nevertheless each time I try to re-install the software I get the following messages:
ERROR: An error occurred during the installation of assembly component {6435B7C0-E0C8-3EA2-91AE-7640034EAFCE}. HRESULT: 0x80070002.
ERROR: Install MSI payload failed with error: 1603 - Schwerwiegender Fehler bei der Installation.
MSI Error message: An error occurred during the installation of assembly component {6435B7C0-E0C8-3EA2-91AE-7640034EAFCE}. HRESULT: 0x80070002.
ERROR: Third party payload installer Adobe_Lightroom_x64.msi failed with exit code: 1603
Since PS was installed without problems I would refrain from deinstalling the Creative Cloud and start over again.
Any hints?
Thx

Claasd5335054 you will want to review the MSI log files to determine what error message is preventing the installation from completing.
ERROR: An error occurred during the installation of assembly component {6435B7C0-E0C8-3EA2-91AE-7640034EAFCE}. HRESULT: 0x80070002.
ERROR: Install MSI payload failed with error: 1603 - Schwerwiegender Fehler bei der Installation.
MSI Error message: An error occurred during the installation of assembly component {6435B7C0-E0C8-3EA2-91AE-7640034EAFCE}. HRESULT: 0x80070002.
ERROR: Third party payload installer Adobe_Lightroom_x64.msi failed with exit code: 1603
This is the only error information contained within Adobe Lightroom 5's installation log. The MSI log files contain the additional error messages.

How do I uninstall the MSI DOT program.

HI,
I'd like to know how I uninstall the DOT program that comes with MSI VGA drivers.
If I just uninstall the MSI driver, then install a nvidia driver, the DOT part of the old msi driver comes back. how do I remove this?
Ive tried using the driver cleaner program, in between unstalling old driver, and installing new driver, this does not help.
Thanks.

Quote
Originally posted by Roger_kelly
MSICPL.DLL is a Dynamic Link Library which when present integrates with the Nvidia Control Panel and gives u the MSI DOT Panel so that you can use DOT along with Nvidia Drivers. If you delete this file you will not get the DOT panel, you will have the Vanilla NVIDIA Control Panel without the DOT.
Rajiv
Thanks Rajiv,
I understand now

Cannot update Firefox. It says, "Update could not be installed. (patch apply failed). Cannot take the risk of uninstalling MF.

Am unable to update my firefox and also cannot install any other browser like chrome or opera. I had uninstalled Chrome and cannot re install it. My internet explorer is not working as well. So cannot take the risk of uninstalling firefox and install a fresh version (it might fail). However I have scanned and checked my computer as far as possible with multiple programmes and no trouble is reported. All other programmes in my PC are running fine. Windows, internet security is getting updated smoothly. The only problem here is installing browser(s) or updating it.
I am on win 7 64 bit system. Firefox version is 31. It iis constantly asking me to update to 32.0.2. I have tried all specified ways to update it, but failed.

Try this:
*Download the full Firefox installer and save the file to the desktop https://www.mozilla.org/en-US/firefox/all/
*Start the installation with a double-click on the desktop icon
Do a malware check with several malware scanning programs on the Windows computer.
Please scan with all programs because each program detects different malware.
All these programs have free versions.
Make sure that you update each program to get the latest version of their databases before doing a scan.
*Malwarebytes' Anti-Malware: http://www.malwarebytes.org/mbam.php
*AdwCleaner: http://www.bleepingcomputer.com/download/adwcleaner/ http://www.softpedia.com/get/Antivirus/Removal-Tools/AdwCleaner.shtml
*SuperAntispyware: http://www.superantispyware.com/
*Microsoft Safety Scanner: http://www.microsoft.com/security/scanner/en-us/default.aspx
*Windows Defender: http://windows.microsoft.com/en-us/windows/using-defender
*Spybot Search & Destroy: http://www.safer-networking.org/en/index.html
*Kasperky Free Security Scan: http://www.kaspersky.com/security-scan
You can also do a check for a rootkit infection with TDSSKiller.
*Anti-rootkit utility TDSSKiller: http://support.kaspersky.com/5350?el=88446
See also:
*"Spyware on Windows": http://kb.mozillazine.org/Popups_not_blocked
*https://support.mozilla.org/kb/troubleshoot-firefox-issues-caused-malware

My itunes won't update. It's looking for 10.6.0.40. Last time it tried to update, I downloaded the msi to my desktop and I deleted it within the last six months. Now I can't uninstall or update.

The last time my iTunes couldn't update. I used support from Itunes and downloaded it my desktop. My mistake. Because without thinking, I deleted it within the last six months from my desktop, without thinking I'd need it later. For the past month I've needed to update my Itunes and it can't find the msi. Now, my Ipad, my kids' ipod touches and my iphone can't update. Especially the ipod touches, iphone and work ipad have already updated to the OS6. And, now they won't work with this outdated iTunes. Help.

(1) Download the Windows Installer CleanUp utility installer file (msicuu2.exe) from the following Major Geeks page (use one of the links under the "DOWNLOAD LOCATIONS" thingy on the Major Geeks page):
http://majorgeeks.com/download.php?det=4459
(2) Doubleclick the msicuu2.exe file and follow the prompts to install the Windows Installer CleanUp utility. (If you're on a Windows Vista or Windows 7 system and you get a Code 800A0046 error message when doubleclicking the msicuu2.exe file, try instead right-clicking on the msicuu2.exe file and selecting "Run as administrator".)
(3) In your Start menu click All Programs and then click Windows Install Clean Up. The Windows Installer CleanUp utility window appears, listing software that is currently installed on your computer.
(4) In the list of programs that appears in CleanUp, select any iTunes entries and click "Remove", as per the following screenshot:
(5) Quit out of CleanUp, restart the PC and try another iTunes install. Does it go through properly this time?

The MSI GAMING APP - FAIL

Hello my friends,
I bought the MSI r9 380 4Gb (Gaming) card and tried to install the MSI gaming app, but when I try to start the app all I get is "The platform does not support this application".
question ; Do I need the MSI Gaming motherboard for thi...

Just to add,
I can run the 'Heaven Benchmark' just fine.
FPS:
123.2
Score:
3103
Min FPS:
24.9
Max FPS:
212.9
System
Platform:
Windows 7 (build 7601, Service Pack 1) 64bit
CPU model:
Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz (3207MHz) x4
GPU model:   ...

I have a problem updating my AcrobatX ERROR: Install MSI payload failed with error: 1603 - Alvorlig feil under installasjonen. MSI Error message: Ugyldigt drev: K:\ ERROR: Third party payload installer AcroPro.msi failed with exit code: 1603

Acrobat X problem updating.
ERROR: Install MSI payload failed with error: 1603 - Alvorlig feil under installasjonen.
MSI Error message: Ugyldigt drev: K:\
ERROR: Third party payload installer AcroPro.msi failed with exit code: 1603
I have uninstalled my AcrobatX and now This message appear when I try to reinstall:
ERROR: Install MSI payload failed with error: 1603 - Alvorlig feil under installasjonen.
MSI Error message: Ugyldigt drev: K:\
ERROR: Third party payload installer AcroPro.msi failed with exit code: 1603
Is there anybody who know how to solve it?

Hi Patricia ,
For error 2203 ,please refer to the following link.
https://helpx.adobe.com/creative-suite/kb/error-2203-install-creative-suite.html
For error 1603 ,refer to this link.
https://helpx.adobe.com/creative-suite/kb/error-1603-install-cs3-cs4.html
Let us know if this solves the issue .If required ,we"ll surely assist you further.
Regards
Sukrit Dhingra

I try to install lightroom 5.6 and receive Exit Code: 7 ERROR: Third party payload installer Adobe_Lightroom_x64.msi failed with exit code: 1603

Exit Code: 7
Please see specific errors below for troubleshooting. For example, ERROR:
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 3 error(s)
----------- Payload: Adobe Photoshop Lightroom 5 5.6.0.0 Adobe_Lightroom_x64.msi_5.6 -----------
ERROR: Schlüssel ist im angegebenen Status nicht gültig.
ERROR: Install MSI payload failed with error: 1603 - Schwerwiegender Fehler bei der Installation.
MSI Error message: Schlüssel ist im angegebenen Status nicht gültig.
ERROR: Third party payload installer Adobe_Lightroom_x64.msi failed with exit code: 1603

Same problem. I have CC installed on Win 7 with all other apps working fine. Tried to install Lightroom 5 and got:
Exit Code: 7
Please see specific errors below for troubleshooting. For example, ERROR:
- 0 fatal error(s), 3 error(s)
----------- Payload: Adobe Photoshop Lightroom 5 5.7.0.0 Adobe_Lightroom_x64.msi_5.7 -----------
ERROR: Error 1935.An error occurred during the installation of assembly component {5C21D397-1DA5-
3749-8C1F-165F21DE9E3E}. HRESULT: 0x80070003.
ERROR: Install MSI payload failed with error: 1603 - Fatal error during installation.
MSI Error message: Error 1935.An error occurred during the installation of assembly component
{5C21D397-1DA5-3749-8C1F-165F21DE9E3E}. HRESULT: 0x80070003.
ERROR: Third party payload installer Adobe_Lightroom_x64.msi failed with exit code: 1603
I uninstalled all Adobe CC software, ran Adobe CC Cleaner, cleaned my Registry using Piriform CCleaner 5, rebooted and reinstalled CC from scratch. Same problem--everything else installed correctly except Lightroom 5. Also tried uninstalling KB2918614--no joy.
Dayton

Third party payload installer Adobe_Lightroom_x64.msi failed with exit code: 1603

Exit Code: 7
Please see specific errors below for troubleshooting. For example, ERROR:
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 3 error(s)
----------- Payload: Adobe Photoshop Lightroom 5 5.6.0.0 Adobe_Lightroom_x64.msi_5.6 -----------
ERROR: Error 1935.An error occurred during the installation of assembly component {F24CABFE-ED58-3012-A491-F671A890E43B}. HRESULT: 0x80071A30.
ERROR: Install MSI payload failed with error: 1603 - Fatal error during installation.
MSI Error message: Error 1935.An error occurred during the installation of assembly component {F24CABFE-ED58-3012-A491-F671A890E43B}. HRESULT: 0x80071A30.
ERROR: Third party payload installer Adobe_Lightroom_x64.msi failed with exit code: 1603

I followed the ostensibly applicable steps outlined in the above linked articles and no go.
Further, I have uninstalled and reinstalled .net framework two times.
Adobe's tech support team has (according to their findings) "determined" that my windows .net framework is "corrupted" and as such my system will disallow the installation of any .msi programs; my only salvation (according to Adobe) is to fork over $100.00 to Microsoft for "advanced" Windows tech support. Earlier today I was easily able to install Silkypix RAW software which is a program having an .msi extension. This seems to contradict the Adobe technical team's findings. Moreover, I've had ZERO installation issues with any other developer's programs including Corel, Sony and a host of additional 3rd party programs- ponderous.
As well, both Adobe Air and Acrobat function and routinely update on my system without incident. For the life of me I have no idea what to do to remedy this frustrating issue.
In addition to the 1603 error, I see a 1935 error as well. I would greatly appreciate any useable suggestions to permit the installation of Lightroom and PS.
Thanks!

SCCM 2012 Client.msi Fails

I am able to install the SCCM client on many machines, but two machines are failing. First I looked in ccmsetup.log:
<![LOG[File C:\Windows\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi installation failed. Error text: ExitCode: 1603
Action:
ErrorMessages:
]LOG]!><time="16:25:20.476+00" date="03-16-2013" component="ccmsetup" context="" type="3" thread="1512" file="msiutil.cpp:860">
<![LOG[Next retry in 120 minute(s)...]LOG]!><time="16:25:20.507+00" date="03-16-2013" component="ccmsetup" context="" type="0" thread="1512" file="ccmsetup.cpp:7554">
Then i looked at client.msi.log for more detail, and searced for "return value 3". This log file is hug so i included an excerpt from it. Let me know where to look in the log file for more descriptive text.
[15:43:48] Automatic Delayed Start configuration is enabled for CCMEXEC
MSI (s) (70:64) [15:43:48:682]: Executing op: CustomActionSchedule(Action=CcmRegisterWinTaskRollback,ActionType=3329,Source=BinaryData,Target=CcmRegisterWinTaskRollback,)
MSI (s) (70:64) [15:43:48:697]: Executing op: ActionStart(Name=CcmRegisterWinTask,Description=Registers tasks with Windows Task Scheduler.,)
MSI (s) (70:64) [15:43:48:697]: Executing op: CustomActionSchedule(Action=CcmRegisterWinTask,ActionType=3073,Source=BinaryData,Target=CcmRegisterWinTask,)
MSI (s) (70:64) [15:43:48:697]: Creating MSIHANDLE (24379) of type 790536 for thread 1892
MSI (s) (70:10) [15:43:48:697]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI6477.tmp, Entrypoint: CcmRegisterWinTask
MSI (s) (70!24) [15:43:48:713]: Creating MSIHANDLE (24380) of type 790531 for thread 3620
MSI (s) (70!24) [15:43:48:713]: Closing MSIHANDLE (24380) of type 790531 for thread 3620
[15:43:48] Registering windows task 'Configuration Manager Idle Detection'
MSI (s) (70:10) [15:43:48:713]: Closing MSIHANDLE (24379) of type 790536 for thread 1892
CustomAction CcmRegisterWinTask returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (70:64) [15:43:48:760]: User policy value 'DisableRollback' is 0
MSI (s) (70:64) [15:43:48:760]: Machine policy value 'DisableRollback' is 0
Action ended 15:43:48: InstallFinalize. Return value 3.
MSI (s) (70:64) [15:43:48:838]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1114668398,LangId=1033,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (70:64) [15:43:48:838]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (70:64) [15:43:48:838]: Executing op: DialogInfo(Type=1,Argument=Configuration Manager Client)
MSI (s) (70:64) [15:43:48:838]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (70:64) [15:43:48:838]: Executing op: ActionStart(Name=CcmRegisterWinTask,Description=Registers tasks with Windows Task Scheduler.,)
MSI (s) (70:64) [15:43:48:838]: Executing op: ProductInfo(ProductKey={D6804B3A-BFEC-4AB4-BFA5-FD9BECC80630},ProductName=Configuration Manager Client,PackageName=client.msi,Language=1033,Version=83893884,Assignment=1,ObsoleteArg=0,,,PackageCode={59A0EA77-D28C-4286-83A6-04BB57B9CDD6},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
MSI (s) (70:64) [15:43:48:838]: Executing op: ActionStart(Name=CcmRegisterWinTaskRollback,Description=Rolls back the changes made by CcmRegisterWinTask.,)
MSI (s) (70:64) [15:43:48:838]: Executing op: CustomActionRollback(Action=CcmRegisterWinTaskRollback,ActionType=3329,Source=BinaryData,Target=CcmRegisterWinTaskRollback,)
MSI (s) (70:64) [15:43:48:838]: Creating MSIHANDLE (24381) of type 790536 for thread 1892
MSI (s) (70:8C) [15:43:48:838]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI6504.tmp, Entrypoint: CcmRegisterWinTaskRollback
MSI (s) (70!DC) [15:43:48:853]: Creating MSIHANDLE (24382) of type 790531 for thread 3548
MSI (s) (70!DC) [15:43:48:853]: Closing MSIHANDLE (24382) of type 790531 for thread 3548
MSI (s) (70:8C) [15:43:48:853]: Closing MSIHANDLE (24381) of type 790536 for thread 1892
[15:43:48] Removing windows task 'Configuration Manager Idle Detection'
From successfully installation i typically see folders created in C:\Windows\CCM\* but in this particular case there are only a couple .tmp files and other misc. Where should i look next? I have tried ccmsetup.exe /uninstall and then ccmsetup.exe
/mp:<machine> SMSSITECODE=<code> /noservice and also with /service.
I have tried winmgmt /resetrepository
I have checked that BITS service is running.
What else should i look for?
thanks

Did someone able to find the root cause of it and able to it resolve it, i'm currently facing the same issue:
Error 1904. Module C:\Windows\CCM\DCMADQueryProvider.dll failed to register.
HRESULT -2147024703. Contact your support personnel"
This error is not
restricted to any 1 dll but it's random like DCMADQueryProvider.dll,
statusagent.dll, ccmcore.dll
•I'm getting this error while installing
SCCM 2012 client.
Steps i tried:
1.I did try manually registering
oringinally but when the client fails to install, it removes all the source
files including the ccmcore.dll. So, ccmcore.dll doesn't reside on the system
after failing to install the client or at least not that I can see.
2. I
have tried timing it just right so that my "regsvr32 ccmcore.dll" is run during
the install process while the file is in the CCM folder but that didnt work
either.
3. I had manually created the directory CCM\x64\ccmcore.dll and
copied the file from a working client and try to register but it gave me an
error " Failed to load .dll"
4. i have tried uninstalling the client from
ccmclean and tried to reinstall it but still it fails.
Currently not sure what is wrong with the client install, so still
investigating the issue, please help if someone was able to solve the issue.
There are some
articles out there which points to resolving this issue by registering
ATL.dll.
However, in this
case ATL.dll has been registered only 1 times using regsvr32.exe (system32 and
syswow64 folders).
Based on procmon :
HKCR\Wow6432Node\CLSID\{44EC053A-400F-11D0-9DCD-00A0C90391D3}\InprocServer32\
While installing, it was looking for ATL.DLL and found the location from
registry as "“%systemroot%\system32\atl.dll”

Windows 10 SDK 10.0.10069 : The installer failed. User cancelled installation. Error code: -2147023294

I get this error when installing VS 2015 Community RC. I'm installing on Windows 10 build 10074. I tried uninstalling VS and tried performing the steps from other known issues... Change > Custom > Select feature > Update.
I also get the other errors as well...
Emulators for Windows Mobile 10.0.10069 : The installer failed. User cancelled installation. Error code: -2147023294
Emulators for Windows Mobile 10.0.10069 : The installer failed. User cancelled installation. Error code: -2147023294

Same issue here, on a Surface Pro 3.
I've tried all I can think of, including a full reinstall of the OS (10074). Basically it always fails with the errors below.
Launching VS I do have the UAP templates installed, but not the emulators. I can create a new Windows Universal app no problem, however it shows up as a Windows 8.1 type in the properties pane. Missing lots of references so obviously nothing builds.
Tried installing the tools separately (the ones linked by Paul Chapman in a separate thread). These installed fine, and gave me the emulators (at least in the drop down, haven't been able to verify they work as nothing else works). Proceeded to "repair"
the VS install after this and at that point the install completed without errors, however nothing still works inside VS. Then proceeded to "modify" and remove any Universal app stuff, rebooted and reinstalled, only to get the same error again and
back at square one.
Tried, as far as I can remember, fresh installs from both the ISO and webinstaller (as there was some talk about the ISO containing older code and missing some tools).
Spent a week trying to get a Win10 rig up now, to no avail. Previous builds (with CTP6) would give me a UAP mobile install error, which seemed linked to Hyper-V not working, however Hyper-V was working just fine...
Oh, and obviously - No, I did not cancel the install myself.
Here are some relevant lines from the install log,
[060C:0CF0][2015-04-30T14:20:08]i000: MUX: Source confirmed
[060C:1994][2015-04-30T14:20:14]i000: MUX: Finished connecting secondary installer pipe
[060C:14D4][2015-04-30T14:20:19]i000: MUX: Updating secondary installer progress display name: Windows 10 SDK 10.0.10069
[060C:14D4][2015-04-30T14:20:25]i000: MUX: Updating secondary installer progress display name: Tools for Windows 10 Universal Apps (Windows SDK 10.0.10069)
[060C:044C][2015-04-30T14:28:13]i000: MUX: ExecuteError: Package (VSSecondaryInstaller_box) failed: Error Message Id: 1603 ErrorMessage: Windows 10 SDK 10.0.10069 : The installer failed. User cancelled installation. Error code: -2147023294
[0288:0054][2015-04-30T14:28:48]e000: Error 0x80048646: Process returned error: 0x80048646
[0288:0054][2015-04-30T14:28:48]e000: Error 0x80048646: Failed to execute EXE package.
[060C:044C][2015-04-30T14:28:48]e000: Error 0x80048646: Failed to configure per-machine EXE package.
[060C:044C][2015-04-30T14:28:48]i000: MUX: Installation size in bytes for package: VSSecondaryInstaller_box MaxAppDrive: 0 MaxSysDrive: 2063301632 AppDrive: 0 SysDrive: 2060471296
[060C:044C][2015-04-30T14:28:48]i000: MUX: ExecutePackageComplete for secondary installer
[060C:044C][2015-04-30T14:28:48]i000: MUX: Disconnecting secondary installer pipe
[060C:044C][2015-04-30T14:28:48]i000: MUX: Return Code:0x80048646 Msi Messages:Windows 10 SDK 10.0.10069 : The installer failed. User cancelled installation. Error code: -2147023294 Result Detail:0 Restart:None
[060C:044C][2015-04-30T14:28:48]i000: MUX: Set Result: Return Code=-2147187130 (0x80048646), Error Message=Windows 10 SDK 10.0.10069 : The installer failed. User cancelled installation. Error code: -2147023294, Result Detail=, Vital=False, Package
Action=Install, Package Id=VSSecondaryInstaller_box
[060C:044C][2015-04-30T14:28:48]i000: Setting string variable 'BundleResult' to value '0'
[060C:044C][2015-04-30T14:28:48]w350: Applied non-vital package: VSSecondaryInstaller_box, encountered error: 0x80048646. Continuing...
Think I'll go buy a Mac...

And another upgrade year that the MSI file kills the upgrade

So everytime we do an update we need to read and dig to find the guru answer of how to resolve this painful update. Why is this happening and how can this be fixed on both MS or Adobe end so we can normally upgrade Lightroom?
So far the FixIt utility from MS works, at least for me, it is now cleared up and isntalled....but others have had issues, and why is this so common and still an issue?

Hi,
The main problem with MSI installations is as follows (from my experience and from a developer point of view) :
MSI installers add a lot of entries to a database located in the registry under the key named HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer . If you look at this registry tree, you'll see that it contains tenths of thousands of entries which amounts, depending on the system, to several megabytes of data. Very often, a good part of these data are useless and/or related to uninstalled products.
The problem is that once this database has been corrupted, this can cause trouble to other installers. Corruption can be caused by a faulty installer, a faulty de-installer that leaves a lot of useless and harmful data behind, and by some registry cleaning tools.
The big flaw with the MSI technology is that nobody seems to be able to reverse engineer the state of the database and check whether it is healthy. There is absolutely no cleaning tool for this subtree of the registry. Many years ago, a lot of developers (among them many development MVPs and I for one) have requested from Microsoft a cleaning tool that would eliminate irrelevant or wrong data from the MSI database. Obviously, nobody has ever been able to write such a tool. There's very few usable documentation to allow writing such a utility and this would obviously be a time consuming development. I'm only aware of one single (very thick) book about the MSI technology written by a german developer who tried to make things clear. Very nice job but this was not enough information to produce an "MSI Cleaner".
The only "tool" made available by Microsoft is Windows Installer Cleanup that can only wipe out the data for a single product. It doesn't check anything, it deletes every entry related to a given product (which is rarely what we actually need). There's another tool that is able to delete everything (but I can do that manually with a registry editor). That's all.
IMHO, this explains why a given MSI installer (and especially MSI updaters) will work fine on certain systems and will fail on another. It depends on which applications (and Windows updates) were "MSI installed" or "MSI uninstalled" and in which order. The use of a registry cleaning tool may also generate trouble.
So it is extremely difficult to diagnose an MSI installation problem. Any MSI problem is tightly related to the system configuration and to the installation/uninstallation history of that system.
MSI is an ambitious technology but it often fails because it is not traceable, not debuggable and because its database cannot be repaired. Just totally or partially deleted.

The MSI " Failed. Uninstall VMware

Similar Messages

Maybe you are looking for