This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients ArranM, Gowtham N.M, Gowtham NM, eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2018-03-20.16:48:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1521564520.77.0.467229070634.issue25345@psf.upfronthosting.co.za>
In-reply-to
Content
Yeah, very strange that only some MSIs are being affected by this error. They no doubt have something in common.

If by clean boot you mean reinstalling Windows, then yes, that fixes most issues, but it is pretty drastic :)

I don't actually have any good recommendations for fixing Windows Installer problems... there used to be a troubleshooting tool available, but I'm not sure where it's gone. All the best advice I can find online these days basically just says to reinstall, but you could try System Restore first (and it may even help to create a new restore point and then restore to it - I suspect that will reset some state without losing anything you installed recently).

Without full access to your machine and much better installer diagnostic skills than I have there's nothing else I can offer, sorry.
History
Date User Action Args
2018-03-20 16:48:40steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, zach.ware, eryksun, Gowtham NM, Gowtham N.M, ArranM
2018-03-20 16:48:40steve.dowersetmessageid: <1521564520.77.0.467229070634.issue25345@psf.upfronthosting.co.za>
2018-03-20 16:48:40steve.dowerlinkissue25345 messages
2018-03-20 16:48:40steve.dowercreate