|
I'd try uninstalling then reinstalling your .NETs first. -- I'm digging into what's causing the installation error, if the above doesn't work I ~might~ have another idea besides doing a refresh of windows.
|
#
¿
Mar 2, 2017 03:35
|
|
|
|
| # ¿ May 2, 2024 22:21 |
|
|
I didn't realize how difficult it is to remove .NET now, sorry! It's installed through Windows Update now, so uninstalling the correct KB would remove it but I don't know for sure which one is the correct one (I think 4.6.2 is KB3151900 maybe?) or how it may affect your system. I take back my advice on doing so, but the option is there. Something less risky is running this .NET setup verification tool found here https://blogs.msdn.microsoft.com/astebner/2008/10/13/net-framework-setup-verification-tool-users-guide/. From what I've been able to find, the Quicken installer uses the same tool to verify that your .NET installation is good (from logs it looks like it's called by CheckHealthOfDotNetFramework() - the one failing the install). Run the verification tool for .NET Framework 4 Client to see if it is in fact your .NET messing up or their installer bugging out. Actuarial Fables fucked around with this message at 07:33 on Mar 2, 2017 |
|
#
¿
Mar 2, 2017 07:29
|
|
|
Sorry for not getting back sooner; I got sick and died. If you haven't already given up and reset your Windows install, there's a few more things to try out - Make sure you're running the setup as Administrator - Re-download the Quicken installation files - Run this Quicken Cleaner Tool - Make a new user (Settings > Accounts > Family and other people > Add someone else to this PC) and run the install on this new user. The Quicken installation logs are located in "C:\ProgramData\Intuit\Quicken\Log\installer" if you'd like to take a look at them. I believe the only personal information is your Microsoft username in the file paths(C:\Users\YourName\blah\blah). You can open the logs in notepad and Edit > Replace... it with something generic if you're inclined to post them somewhere. If nothing still resolves this - and you're feeling up to it - you can push the issue on Quicken support with the troubleshooting you've done.
|
|
#
¿
Mar 6, 2017 06:58
|
|
|
|
|
#
¿
Mar 6, 2017 17:45
|
|