I ran every test/fix as the app instructed & lo & behold - Acronis would install & function as normal. Kind of what a good IT specialist could do, but without needing the college education -) 5) Bump installer version and product code. AI installer will install the merge module.
3) Install application on new Vista install. Add an application executable that needs this merge module to run. Unlike most 'smart system tweakers' it doesn't try to optimise your machine to being 'something super' all it does is makes sure everything is set to 'factory defaults', without breaking installed apps etc. Add the MicrosoftVC80CRTx86圆4.msm merge module. (Freeware with a donate/pro option, which is not necessary to use the tool for this job, the free version is sufficient) So, I went to a tool I've used before to get errant Windows installs to behave NET Framework on Win 10 as it claimed it was 'part of the OS', didn't touch the registry sizing as it would be most unlikely to be the culprit on a brand-new installation, registered mfc90.dll The issue only arose after I did a full reset.Īfter much Googling, mostly suggesting C++ runtime installs, I arrived at -Īcronis Products: Installation Fails with "An error occurred during the installation of assembly" ",publicKeyToken"įollowing the advice, I ran sfc, checked services were as expected, installed every C++ runtime back to 2005, can't install. I had previously had no issues installing to the same machine using Windows 7 & it continued to work after it was upgraded in-place to Windows 10. I was suffering the Install fails with ",publicKeyToken" issue on a clean Windows 10 install. Here's how the Windows all-in-one Repair fixed my Acronis install. Posting here to to make the solution more easily Googlable.įrom one very satisfied customer & brand new Pro version purchaser, in recognition of the pain it saved I've posted the following message on the Acronis forums.
0 kommentar(er)
