Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

Windows Installer Cleanup Utility Replacement's Windows 10 Compati


4 replies to this topic

Matt@configurationnation

Matt@configurationnation
  • Full Members
  • 3 posts

Posted 23 November 2015 - 17:53

Hi,

 

I rely on the Windows Installer Cleanup Utility replacement fixitforme for fixing client pcs that suddenly start not installing software MSIs anymore:-

https://support.micr...l_and_uninstall

When I go to the site it tells me it is not compatible with Windows 10. Is this likely to be the webpage code being out of date or is it really not recommended for Windows 10 users and if that is the case what is recommended? The site disabled the run button so I guess I'm forced to download it on another machine to test it.

 

Maybe I can still use the old cleanup utility (if the user doesn't have office 2007)?

 

Many Thanks

Matt

 

ps. also posted here: http://answers.micro...m=1448443362291


Edited by Matt@configurationnation, 25 November 2015 - 10:46.


VBScab

VBScab
  • Full Members
  • 436 posts

Posted 24 November 2015 - 21:41

>I rely on the Windows Installer Cleanup Utility replacement fixitforme
Why? That's a tool designed for end-users who are too timid to get into the guts of their machines. Shouldn't you be performing proper trouble-shooting rather than sledge-hammering WI into submission?


- Don't know why 'x' happened? Want to know why 'y' happened? ProcMon will tell you.
- Try using http://www.google.com before posting.
- I answer questions only via forums. Please appreciate the time I give here and don't send me personal emails.

Matt@configurationnation

Matt@configurationnation
  • Full Members
  • 3 posts

Posted 25 November 2015 - 10:35

Where software does not install becuase Windows Installer is in a bad state why would I not use the Microsoft tool designed to fix Windows Installer when it get's into a bad state?

 

In this instance the customer runs the MSI on his machine and the UI completes as normal and then installer switches to the server and then MainEngineThread is returning 1603. Do you think I need get procmon out and get more detail on why it might be failing? I suspect another installer did not finish correctly, can you offer any better way to resolve this? Installsite FAQ here says to use the MSI cleanup util for such cases.


Edited by Matt@configurationnation, 25 November 2015 - 10:59.


VBScab

VBScab
  • Full Members
  • 436 posts

Posted 28 November 2015 - 09:01

>ProcMon

I'm shocked that you haven't already explored that avenue: you can't really do packaging  - or any kind og support role - properly without ProcMon.


- Don't know why 'x' happened? Want to know why 'y' happened? ProcMon will tell you.
- Try using http://www.google.com before posting.
- I answer questions only via forums. Please appreciate the time I give here and don't send me personal emails.

Matt@configurationnation

Matt@configurationnation
  • Full Members
  • 3 posts

Posted 29 November 2015 - 10:14

...that's a tool designed for end-users who are too timid to get into the guts of their machines.

 

Great that's just what I need. :P

 

Procmon might prove that the server is locked for some other process but won't give me a reliable why to fix it easily for the end-user. I would have to remote in to the machine  (or talk home users through it yikes!) each time and manually analyse the results and then try the manual version of what this app used to do?


Edited by Matt@configurationnation, 29 November 2015 - 11:01.