![]() HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. I have a powershell script to look for those with a bad install state and export then delete the key. ![]() Look for folders ending in FF in a group. HKLM\SOFTWARE\Classes\Installer\Products. Then, you need to fix the registry from the old version, it's in THREE places: The actual problem is that it leaves the old uninstaller info in ~30% of cases, and on next upgrade it fails with that error.įor a small amount of PCs, deploy with PDQ deploy and run pskill (or taskkill I guess) of regdll32 on the machines to force the error to clear and update to continue. Manual remediation of these is easy enough, but the concern was the number of machines requiring manual intervention.įor a start, this problem is DIRECTLY due to Javas stupid bloody "updating" system. Contact your support personnel or package vendor. A DLL required for this install to complete could not be run. Error 1723.There is a problem with this Windows Installer package.To wit: this was previously tested with my test box, then my test group of 45 users, then the entire 200-person engineering department, all succesfully, before pushing to the entire company, where it experienced three different types of failures across this 6%: Some of the higher-ups are upset about the 6%, so I'd love to be able to point them to some things that say that's not too bad (unless, of course, 6% actually is bad). I'd read somewhere (of course, I can't find this now) that 10% is an "expected" failure rate according to Microsoft for deployments. I just pushed out Java 6u45 last night, and it failed on 6% of our machines. Wondering what you guys consider an acceptable failure rate for software deployment. As a general rule, if someone has flair, they almost definitely know what they're talking about. Microsoft employees typically have MSFT Official flair, and MVPs usually have MSFT Enterprise Mobility MVP with a link to their personal site/blog.Please send mod mail if you qualify and would like flair set for your account. Flair is reserved for Microsoft employees and MVPs.System Center Configuration Manager and Endpoint Protection.Listing of Local ConfigMgr-related User Groups (largely outdated) URL shorteners cause this almost every time, but so do strings of apparent gibberish like WSUS and PXE sometimes. It might have been caught by the spam filter. Post your SCCM tips and tricks, requests for help, or links others might find useful! Post not showing up?
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |