Need help analyzing MSI install log Please.
This computer is windows 7, completely up to date. I am running into a problem installing Jungle Disk Backup software. This software was already installed on the computer at some point but somehow got corrupted and can't be installed and there's no way to uninstall. I keep getting an error that the "installation ended prematurely due to an error" but no specifics from the software. By logging the install I was able to find the error but not real sure how to fix this.
Please see the log from the installation below and do a "find" for "return value 3". Right above this line "Action ended 10:11:19: InstallFinalize. Return value 3.", the 3-4 lines above showing an error installing "cbfs.cab" driver is the culprit but everything I've tried isn't working.
I've tried:
- clean boot,
-registerting the cbfs driver which fails because the dll is missing.
-reparing Windows installer but other programs install ok so that's sorta unneccessary
-unregistering/reregisteri
Thanks for your help in advance.
jd-install.log
Please see the log from the installation below and do a "find" for "return value 3". Right above this line "Action ended 10:11:19: InstallFinalize. Return value 3.", the 3-4 lines above showing an error installing "cbfs.cab" driver is the culprit but everything I've tried isn't working.
I've tried:
- clean boot,
-registerting the cbfs driver which fails because the dll is missing.
-reparing Windows installer but other programs install ok so that's sorta unneccessary
-unregistering/reregisteri
Thanks for your help in advance.
jd-install.log
ASKER
So you think I should just contact Jungle Disk support?
ASKER
There's got to be a way to rid this computer of this software and reinstall without having to contact Jungle disk and/or rummage through the registry? What about a repair install?
You could monitor the install using Procmon (http://live.sysinternals.com/procmon.exe). It would reveal simple things like incorrect registry key permissions on the existing service, etc.
I can also read procmon logs and help you out if you do a trace of the installation transaction.
Just keep in mind that it captures a LOT of records - so start capture as late as possible and end it as early as possible.
I can also read procmon logs and help you out if you do a trace of the installation transaction.
Just keep in mind that it captures a LOT of records - so start capture as late as possible and end it as early as possible.
ASKER
Ok. So, obviously there's something else going on with this system because it's giving me error "unable to load Process Monitor device driver"? I tried rebooting and re-downloading. This computer had some malware I cleaned off of it about a week ago and it's possible something in the registry got muckered up.
ASKER
Just tried to load TDS Killer and same error message "Can't load driver".
ASKER
Just ran TDS Killer anyway and it found about 150 locked files listed as kernel drivers and found file 44e89afd9f486c81.sys as rootkit.win32.necurs.gen. The locked files look to be legitimate .sys files and after running autoruns it's listing most of the files under services as "file not found". There are no restore points. I'm wondering if a complete reinstall is the way to go here.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yeah, I agree. Plus deleting or quarantining the file TDS Killer finds is causing it to crash on booting.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
"Driver install failed: 8 (C:\Program Files\Jungle Disk Workgroup\cbfs.cab)"
The error 3 coming back from the InstallFinalize generates an overall 1603 - both of which are generic failures in MSI resulting from the DLL setting the entire package to fail.