Windows 10 and Microsoft .Net Framework 4.6.1 error

  • 7
  • 21
  • Problem
  • Updated 7 months ago
  • In Progress
I updated Windows 10 to the latest build (15002) and when I try to start Quicken 2017, I get an error message that .Net framework 4.6.1 is not installed. When I install it as a stand alone file, it says its already installed. When I tried to reinstall Quicken 2017, it says it installs all ok. Then same error on startup. I then installed the November Mondo update file and installs fine. Then same error when starting Quicken 2017.
Photo of MikeHarden

MikeHarden

  • 326 Points 250 badge 2x thumb

Posted 7 months ago

  • 7
  • 21
Photo of MikeHarden

MikeHarden

  • 326 Points 250 badge 2x thumb
I uninstalled Quicken 2017 and Installed Quicken 2016. Quicken 2016 is running fine. I will stick with 2016 until I can get an update on if 2017 is fixed through this thread. Please let me know if anyone is running Quicken 2017 on Windows 10 build 15002. Thanks.
Photo of RedScare

RedScare

  • 60 Points
I am having the same problem, and will also downgrade to 2016.
Photo of alphabeta

alphabeta

  • 2,178 Points 2k badge 2x thumb
Scan the messages here. The is a simple edit to the registry to fix it
Photo of Sue Meyer

Sue Meyer

  • 102 Points 100 badge 2x thumb
How about putting the simple edit to the registry up here, to save us from searching the messages for the fix.
Photo of alphabeta

alphabeta

  • 2,178 Points 2k badge 2x thumb
N777TY .
160 Points 100 badge 2x thumb
Developers did something bad... like hard-coded checking installed version of Framework by looking at a registry key... Anyways, this can be temporarily worked around... I don't recommend doing this but it'll get Quicken started (until they sort this out properly).

You have to do some wrangling to get this to work - DO NOT do this if you have no idea what these steps below mean:
1) Open RegEdit
2) Go to this key: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\NET Framework Setup\NDP\v4\Full
3) Right click on it and go to Permissions.
4) Take ownership of the key
5) Change permissions on the key (so you can modify the value) .. ie give Administrators Full Control
6) Change the value of Version subkey -- current value will be 4.7.02020 -- change it to 4.6.02020

That's it. Quicken checks this key and checks if it starts with 4.6.... and since it doesn't (it starts with 4.7) it blows up.. those numbers 02020 afterwards do not matter..

Good luck.. hope they work this out soon.

PS... Forgot to mention -- Quicken works just fine with .NET Framework 4.7 ;)
Photo of Jake Metzler

Jake Metzler

  • 72 Points
Worked perfectly.... had a little problem with getting permission but worked it out.
Thank you!
Registry fix worked. Thanks. Hopefully I don't have to change the owner back to TrustedInstaller because i tried that and it didn't like it ;).
Photo of Paul Rose

Paul Rose

  • 708 Points 500 badge 2x thumb
is it possible that someone can make a batch file to click on?
Photo of David Paulson

David Paulson

  • 80 Points 75 badge 2x thumb
I uninstalled, made the registry entries, and now quicken stalls at the registration of the software with my username.  Back to the previous release of Windows!
Photo of johnpombrio

johnpombrio

  • 184 Points 100 badge 2x thumb
Did not work for me with Home and Business 2016 and 2015. It hangs with an error about net.framework while trying to install. Tried the registry fix and that did not help.
(Edited)
Photo of Mike

Mike

  • 100 Points 100 badge 2x thumb
I have the same problem on Windows 10 15002.
Photo of Rob Harris

Rob Harris

  • 256 Points 250 badge 2x thumb
Having the exact same issue. Many are reporting this in the Feedback Hub. Hopefully either MS or Intuit will fix this soon. Very soon.
Photo of alphabeta

alphabeta

  • 2,178 Points 2k badge 2x thumb
Me too. Went through the recommended fixes, neither worked. I backed out Build 150002, Q2017 works fine again.
Photo of dominiccoombe

dominiccoombe

  • 60 Points
me too backing out to 14986 it works fine without any reinstallation of quicken
not sure where the incompatibility is
Photo of alphabeta

alphabeta

  • 2,178 Points 2k badge 2x thumb
Scan the messages, all that is required is a single digit edit in the registry
Photo of Tony Mattas

Tony Mattas

  • 230 Points 100 badge 2x thumb
It's likely a quicken problem, it looks like they statically linked to .NET 4.6.1, and the latest build comes with .NET 4.7. While 4.7 is compatible with 4.6.1, typically statically linking to a specific version is frowned upon. Fortunately you have a few days to back out 150002 until Quicken can get this fixed.
Photo of alphabeta

alphabeta

  • 2,178 Points 2k badge 2x thumb
You could be right. Reinstalling Quicken should reload 4.6.1 and that didn't work here. I think its and MS problem, don't know, don't care. I am anxious for either one of them to fix it. I have more faith in a quick solution from MS.
Photo of Rob Harris

Rob Harris

  • 256 Points 250 badge 2x thumb
I am pretty sure he's right. I don't think that this is on MS to fix - this is what software updating looks like. Intuit needs to implement the fix. I tend to agree, however, that they are less likely to fix it quickly.
Photo of johnpombrio

johnpombrio

  • 184 Points 100 badge 2x thumb
Quicken is no longer owned by Intuit. Now called Quicken INC. and owned by HIG Capital as of several months ago. So don't look to Intuit for the solution (even though they still make me log into the Intuit site when installing.)
Photo of Quicken Colin

Quicken Colin, Official Rep

  • 202,552 Points 100k badge 2x thumb
From my understanding 15002 is a preview build, similar to a beta release.  The purpose of these releases is to give Microsoft a feel for potential issues with the release when it goes fully public, and to address those ahead of time.  My suggestion would be to roll back the update and use the latest public build offered for Windows 10.
Photo of Rob Harris

Rob Harris

  • 256 Points 250 badge 2x thumb
OR....Intuit could address the issue so it will not be a problem going forward. This, after all, is what pre-releases are all about.
Photo of Quicken Colin

Quicken Colin, Official Rep

  • 202,552 Points 100k badge 2x thumb
I'm not a developer, but I'm sure that they will address issues that arise with Windows updates.  However there is not guarantee that this is pre-release software. As per the Windows Insider ToS, it may only be experimental software which may not make it to the final release. https://insider.windows.com/Home/TermsOfUse
Also, Intuit divested Quicken Back in late March, early April of 2016.  Quicken Inc is now it's own company.
(Edited)
Photo of Rob Harris

Rob Harris

  • 256 Points 250 badge 2x thumb
This is a pre-release of Windows that is expected to hit the streets in April. I doubt seriously that Microsoft will downgrade the .NET Framework. Either way, Quicken (excuse me) will have to address the issue eventually. Considering the amount of noise that is being generated in various places around the net, sooner would probably be better than later from a PR perspective.
Photo of johnpombrio

johnpombrio

  • 184 Points 100 badge 2x thumb
 Quicken Inc. is owned by HIG Capital now. They will be the ones that need to fix this problem. Just because it is now a fast ring release, the new net.framework can be rolled out to the general public at any time. So it needs to be fixed. Intuit DOES still own TurboTax 2016 and that too is broken by the net.framework. In the meantime, I am running the two programs on another non fast ring computer running Windows 10.
Photo of Jimmy Asbill

Jimmy Asbill

  • 60 Points
And that is what an "Official Rep" has to say to its customer base. I've been using QUICKEN since Parsons first birthed it, and your response sticks in my craw...
Photo of jmdonv

jmdonv

  • 60 Points
It does sound like this is really a quicken issue where moving from 4.6.x to 4.7.x breaks a hard dependency. Will back out 15002 as quicken not known for quick fixes and quicken the only remaining reason for me to run windows.
Photo of jwhayn

jwhayn

  • 72 Points
If not fixed quickly, it will be the final straw with Quicken.
Photo of thecreator

thecreator, SuperUser

  • 58,168 Points 50k badge 2x thumb
Hi @ All,

This was why I wrote up: https://getsatisfaction.com/quickencommunity/topics/add-your-quicken-information-to-your-posts-plus-...

They are too many programs that Build 15002.1001 broke.

You should be dual-booting your computer, if testing Insider Preview Builds from Microsoft.

You should have the Public Release of Windows on one partition with Quicken installed and the Insider Preview Release of Windows, if Beta Testing for Windows also with Quicken installed and report the problems to Microsoft and Quicken.

Quicken 2017 Versions worked in Build 14986.1001, but fails to start in Build 15002.1001 Beta Build.
Photo of Mike

Mike

  • 100 Points 100 badge 2x thumb
The question is - what is best practice for a software developer? is it to hard code the requirement  .net framework 4.6.1? or should it be a .net framework version or later? If it is the later then Quicken should fix it. It's also interesting that Quicken 2016 works... was that not hard coded? why did it change in 2017?

I think Quicken needs to fix it.
(Edited)
Photo of QPW

QPW

  • 309,594 Points 100k badge 2x thumb
"what is best practice for a software developer?"

And there is the 64,000 dollar question!

And the answer is that the develop is screwed no matter what they do.

BTW I don't think this is a "dynamically linked" question.

I don't even think you can statically link .Net into your program.
This is more about stating what .Net versions your program can use.

The reason this isn't any easy problem is because of the simply fact that .Net versions are not completely backwards and forwards compatible.

Say you as a developer see that you would like to use a new feature in .Net XXX.
If you put it in, and some of your users only have .Net XXX - 1 all kinds of nasty things can happen.  So you state that you require .Net XXX.

Note you can also state that you can use .Net XXX and future .Net versions.
That means that your users will get "improvements/fixes" that come out in the newer versions of .Net, but it also sets you up for failures if Microsoft put in something that isn't backwards compatible with the version of .Net your program is compiled with.

And Microsoft has certainly done this in the past.
In fact when changing from .Net 2.0 to .Net 4.X in Quicken 2014, they got burnt big time!  That broke lots of things that they are still struggling with to this day.
Photo of jwhayn

jwhayn

  • 72 Points
Reverting back to Quicken 2016 works
Photo of QPW

QPW

  • 309,594 Points 100k badge 2x thumb
P.S. If you have seen the threads about .Net 4.6.1 and Vista you will see that basically they (Quicken developers) got them selves in a pickle by requiring .Net 4.6.1 for Quicken 2017 and Vista didn't support it.

The fix there from what I understand was that basically Microsoft put out .Net 4.6.1 in a later patch for Vista.
Photo of QuickenUserDC

QuickenUserDC, SuperUser

  • 28,046 Points 20k badge 2x thumb

There are good reasons why a company may not implement a 'Best Practice' solution, whether that applies here or not is unknown.

There are two problems here that I can think of.

First is whether this is a Quicken or Microsoft problem. It is possible that Quicken is not reading the DOT NET release correctly and therefore not understanding that 4.7 is ok but it could also be that Microsoft did not implement the API correctly and is giving Quicken bad data. This is after all, a preview build.

The other problem is whether Quicken hard-coded 4.6.1 or not. Again this could be a coding problem or Quicken (for some reason) needed to code 4.6.1 specifically.

Unfortunately, we will never know what the underlying problem is.

I do hope Quicken will see this thread and start looking at the problem. Otherwise there will be a lot of problems once the Windows 10 release goes public.

Photo of Rob Harris

Rob Harris

  • 256 Points 250 badge 2x thumb
I don't have a single other program that requires 4.6.1. I have not read about any other program that refuses to run with a newer version, either. Quicken clearly has a check for a specific .NET version, and thus guarantees an issue when the new framework is released. It would have been much better to produce a warning (at most) that the supported .NET framework was not detected and that the program may be unstable. My bet is that it would be just fine. The requirement really should check for 4.6.1 or NEWER.
Actually, Rob, I have a game by BigFishGames that stopped working after I updated to 15002. It worked fine with 14986. I had to change the compatibility to Windows 7 before I could get it to work again.
Photo of Rob Harris

Rob Harris

  • 256 Points 250 badge 2x thumb
My statement was not to claim that NO other program will have issues with 15002. It was intended to point out that clearly, the vast majority of programs do not have any issue with 15002 or .NET 4.7. Even Quicken has no issue with either one - REALLY - the issue is only their check for a specific version of .NET. There is no underlying code incompatibility. That's probably true for your game, too.
I shouldn't say that it stopped working totally. It gets to the main menu but when I click on any option, it minimizes to the desktop, but you're right, Rob. It's probably checking the .net  version when lauching the particular option.
Photo of Rob Harris

Rob Harris

  • 256 Points 250 badge 2x thumb
...and you DID get it to work with compatibility mode. This situation is exactly what compatibility mode is for. In contrast, Quicken contains code that prevents it from running, regardless of anything else, if the .NET version doesn't start with "4.6". That is, simply put, a poor approach
Photo of Quicken Dave

Quicken Dave, Official Rep

  • 165,412 Points 100k badge 2x thumb
Hi All,

I apologize for any frustration or inconvenience this .Net Framework issue has caused. This issue has been forwarded to the Quicken development team and the issue is being investigated. As soon as more information is available, we will either update this thread or an announcement will be posted on the Community home page.

Thank you in advance for your patience while the developers investigate this matter.

Dave
Photo of Mike

Mike

  • 100 Points 100 badge 2x thumb
Thanks Dave much appreciated !
Photo of Quicken Dave

Quicken Dave, Official Rep

  • 165,412 Points 100k badge 2x thumb
Official Response
Hi Again, Everyone,

Just a quick note to let you know that Quicken Kathryn has posted an announcement about the .Net Framework issue. To be notified when there is an update in the status of this, please follow the Announcement.

Here's a link to the Announcement:
I hope this helps,
Dave
Photo of Rob Harris

Rob Harris

  • 256 Points 250 badge 2x thumb
Kathryn's comments are not really accurate. Quicken IS compatible with .NET 4.7 (as proven by many on here who have had complete success with the registry edit). The issue is the check that is being employed during startup. There is no real compatibility problem...just bad code in the check procedure. It is disheartening that Quicken would make such a statement and take that position.
Photo of bob hyman

bob hyman

  • 110 Points 100 badge 2x thumb

Further, the fact that *older* versions of Quicken work OK with 4.7 of .Net framework indicates that once upon a time Quicken did the minimum version check correctly. And that implies (but does not prove) that Quicken codebase historically doesn't have any deep-seated incompatibility with 4.7. 

OTOH (there's always another hand), it's possible some developer added a feature to Quicken recently that created an incompatibility with 4.7, so the developer "fixed" that bug by making the version check stricter.  That would be unprofessional, but tempting if s/he didn't know MS' release schedule for .Net Framework...  It's the kind of thing that can happen in a poorly supervised software development organization that doesn't think its market dominance depends on customers affirmatively preferring their product in a field of competitive alternatives. 

Photo of Sue Ward

Sue Ward

  • 60 Points
This needs to be resolved like yesterday.  I reimaged my laptop today after seeing this error (and some other misbehavior), thinking that would FIX the problems.  Now that this has been done, it's not possible to roll back to the previous version of Windows. I am now unable to open my file to get things updated or paid.  Furthermore, when I purchased the 2017 product, I got rid of the old installer, and i'm not finding it available on my account to download.  It would be just good customer service to at least make that installer available for those of us who are having the issue.  Shouldn't be too difficult to consult your registration records and do this.
Photo of thecreator

thecreator, SuperUser

  • 57,916 Points 50k badge 2x thumb
Hi @ Sue Ward ,

https://insider.windows.com/Home/GetStarted

"

Windows Insider Preview may be substantially modified before it’s commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here. Some product features and functionality may require additional hardware or software.

"
The Insider Preview Build 15002.1001 has broken some programs like Microsoft Office Outlook 2007.

You can go back to the Public Version of Windows 10, by downloading the MediaCreationTool.exe from: https://www.microsoft.com/en-us/software-download/windows10

What previous version of Quicken and where did buy the previous version from?
 
Photo of Rob Harris

Rob Harris

  • 256 Points 250 badge 2x thumb
Outlook 2007? Seriously? LOOL. There will be new versions of the .NET Framework. There is no what that there will not be. For Quicken to be coded as it currently is, looking for one and only one .NET Framework version is just silly. It has already been proven that Quicken 2017 runs fine on .NET 4.7.
Photo of Quicken Dave

Quicken Dave, Official Rep

  • 165,412 Points 100k badge 2x thumb
Sue,

Unfortunately, I don't think this is a problem that is going to be resolved immediately. As mentioned in the announcement referenced in my previous response, Quicken is currently incompatible with the new .NET framework (4.7) in the Windows preview release, but unfortunately, it won't be resolved until a future release.

This is primarily a user-to-user forum, so no one here has the ability to consult registration records and/or provide you with an old installer. You will need to reach out to Quicken customer support for help with that. To reach out to a Quicken chat agent, visit the support page(see link below), you will have to select the issues that pertain to yoursituation, from the drop down menus. Once you've done this, a blue button willappear that will allow you to initiate the chat session.If you prefer phone support, Quicken phone support isavailable Monday through Friday, 5:00AM PST – 5:00PM PST, at 1-650-250-1900,for all supported products. Please be aware that phone support may have alonger wait time.

Dave
(Edited)
Photo of Rob Harris

Rob Harris

  • 256 Points 250 badge 2x thumb
Quicken 2017 ABSOLUTELY IS NOT incompatible with .NET 4.7. Many people are running it just fine on .NET 4.7 using the registry edit provided in this thread. The ONLY issue is an extremely poorly written requirements check within the Quicken 2017 startup procedure. THAT'S it. Would take no more than 15 minutes to fix, and hour to test...patch could be out the door within a day - and that's not even working hard at it.
Photo of Rob Harris

Rob Harris

  • 256 Points 250 badge 2x thumb
It could very easily be as simple as editing a line of code that contains "= 4.6" to ">= 4.6".

Done.
Photo of N777TY .

N777TY .

  • 270 Points 250 badge 2x thumb
Developers did something bad... like hard-coded checking installed version of Framework by looking at a registry key...  Anyways, this can be temporarily worked around... I don't recommend doing this but it'll get Quicken started (until they sort this out properly).

You have to do some wrangling to get this to work - DO NOT do this if you have no idea what these steps below mean:
1) Open RegEdit
2) Go to this key:  Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\NET Framework Setup\NDP\v4\Full
3) Right click on it and go to Permissions.
4) Take ownership of the key
5) Change permissions on the key (so you can modify the value) .. ie give Administrators Full Control
6) Change the value of Version subkey -- current value will be 4.7.02020 -- change it to 4.6.02020

That's it.  Quicken checks this key and checks if it starts with 4.6.... and since it doesn't (it starts with 4.7) it blows up..  those numbers 02020 afterwards do not matter.. 

Good luck.. hope they work this out soon.

PS... Forgot to mention -- Quicken works just fine with .NET Framework 4.7 ;)
(Edited)
Photo of Rajendra Dixit

Rajendra Dixit

  • 82 Points 75 badge 2x thumb
Perfect solution! That worked!
Photo of Gene Douglass

Gene Douglass

  • 112 Points 100 badge 2x thumb
Thanks, worked for me too!  No need to go back to previous build of Windows 10.  As with previous build, sleep and hibernate did not work but gave me BSOD, and page fault error.
Photo of Sean OBrien

Sean OBrien

  • 64 Points
The registry fix worked perfectly! Thank You
Photo of CaptainRichard

CaptainRichard

  • 190 Points 100 badge 2x thumb
The registry fixed worked great   Thank you  Have no issue using 4.7.220
(Edited)
Photo of Quicken Dave

Quicken Dave, Official Rep

  • 162,412 Points 100k badge 2x thumb
Hey Guys, I'm glad this has worked for those of you that have tried it. Just a reminder that it's always a good policy to make a copy of your existing RegEdit, before making any changes.
Photo of thecreator

thecreator, SuperUser

  • 54,050 Points 50k badge 2x thumb
Hi @ All, ,

One more thing, if you make the Registry Change, installing the next Windows Build may cause problems, so you need to change the Registry Value back to what is was, before you install the next New Build.

Just keep that in mind..
Photo of Kevin Barrett

Kevin Barrett

  • 70 Points
I tried changing the permissions but keep getting a box saying I don't have permission to change. Any suggestions?
Photo of Rob Harris

Rob Harris

  • 256 Points 250 badge 2x thumb
Click advanced.....change owner at the top.
Photo of Kevin Barrett

Kevin Barrett

  • 70 Points
Thanks Rob. That was simple.
Photo of steve

steve

  • 194 Points 100 badge 2x thumb
Thanks.  Worked for me.  I renamed "Version" to "Versionx" and created a new entry for "Version".  Easier to undo.
Photo of Rob Harris

Rob Harris

  • 256 Points 250 badge 2x thumb
Great info, thank you. This just proves that there is no incompatibility...just poor coding.
Photo of MikeHarden

MikeHarden

  • 326 Points 250 badge 2x thumb
When you do this workaround in the registry, make sure you follow the exact instructions. I was in a similar key and it did not work. Found out I was in wrong string. Once I followed the instructions, it worked. And thanks for the fix, as I now have a similar issue in another program at work. Attempting to see if this fixes as well...
Photo of johnpombrio

johnpombrio

  • 184 Points 100 badge 2x thumb
No luck. Tried the registry fix and changed the Full (and the 1033 and the client in turn) version to 4.6.02020, uninstalled Quicken 2017, shut down. restarted and reloaded Quicken. Now all it does is flash for a fraction of a second the red logo and that is it. Nothing is running. Worse, now TurboTax is no longer running! Fortunately I have another couple of computers so I got both working on another Win10 (not in fast ring) computer. Whew. I even tried loading in Quicken Home and Business 2016 and that does not work as it errors out during the install.
 I also tried all the "cleanup" utilities that Quicken said to try. The qcleanui uninstalled the program but it did not fix the program not running after I installed it again. I also deleted everything I could find on the computer, registry, appdata, using Revo Uninstaller Pro, anything with quicken, intuit, or turbotax in its name. Nothing worked and both Quicken and TurboTax are now dead on my main computer.
(Edited)
Photo of steve

steve

  • 244 Points 100 badge 2x thumb
I'll probably get thrown out of the forum for this, but the .NET issue, Quicken hanging almost daily during one-step updates, etc., are why I'm looking at Personal Capital as an alternative to Quicken.  Intuit should be embarrassed by the low quality of their product, but they don't seem to care as long as they keep raking in the software upgrade fees. (Do they still insist that Quicken data must be on the "C:" drive?  They were still making that absolutely ridiculous claim about 2 years ago.  Local disk, OK,  C: drive, no way is that a logical requirement.  If so, why do they allow files on other disks to be opened?  My data has been on D: for years with no adverse affects, yet the "tech people" in Quicken Tech Support insist that it must run on C:.  D: and C: are on the same spindle.  C: is for the OS, D: is for data.)
Photo of thecreator

thecreator, SuperUser

  • 58,168 Points 50k badge 2x thumb
Hi @ steve ,

Huh? My Data and Quicken Data File are located locally on my Data Partition, separate from the operating system. In the operating system, I am in right now, the Data Partition is Drive F.
Photo of alphabeta

alphabeta

  • 2,178 Points 2k badge 2x thumb
C: Exclusively OS
D: Exclusively alternate OS
E: Applications (including Quicken)
F: Non Graphic Data
G: Graphic Data
Photo of splasher

splasher, SuperUser

  • 542,712 Points 100k badge 2x thumb
@Steve  You need to update your rolodex.  Intuit sold off Quicken last Spring, it is now Quicken, Inc.
Photo of steve

steve

  • 244 Points 100 badge 2x thumb
Yes, I missed that transaction.  I don't think I've contacted Quicken Support since the change.  Maybe they woke up and finally don't tell their customers that only C: is "supported" for the Quicken data files.
Photo of steve

steve

  • 244 Points 100 badge 2x thumb
I agree completely that the Quicken data can be on any local disk - maybe one day they'll correct the problems that keep it from running on a network drive - but for years Quicken support would tell people that only C: was supported.  I don't know if they still do or not.  They had me move my data from D: to C:.  When the problem didn't go away, they ignored the disk issue and never really fixed the problem (Quicken still hangs often during the online update process.)
Photo of Vivek Mishra (MSFT)

Vivek Mishra (MSFT)

  • 160 Points 100 badge 2x thumb

Hi,

The issue appears to be detection for the Quicken version expects the registry key value (Version=4.6.X) to be present, while the key value is actually set to Version=4.7.X for Win10 build 15002.

The registry key behavior is per design. Applications that need to check for a minimum version of the .NET Framework are expected to use the Release registry key value and do a “>=” test rather than examine the .NET Framework version string. Detailed guidance for handling this check can be found here: https://msdn.microsoft.com/en-us/library/hh925568(v=vs.110).aspx?cs-save-lang=1&cs-lang=csharp#code-snippet-4

Since, the registry check that looks for the .NET 4.6 version string happens to be in the Quicken 2017 app you would need to contact Quicken support for an update that corrects the registry check and uses the supported mechanism.

Also, an FYI – while manually modifying the registry key value to 4.6.02020 could solve the issue for Quicken 2017 in the short term, as an unintended side effect apps that do expect to find .NET 4.7 would now be broken. If you are confident none of the other apps you’re running require .NET 4.7 you could use this as a temporary workaround until Quicken fixes the issue, but we do not recommend using this workaround as a long-term solution.

Thanks,

Vivek Mishra (MSFT)

.NET Framework Team
Photo of bob hyman

bob hyman

  • 110 Points 100 badge 2x thumb

Sure too bad I cannot create an application container on Windows just for Quicken to run in, then hack the registry key just for Quicken.

Clearly, there won't be many / any 3rd party apps with a minimum dependency on .Net Framework 4.7 (yet), but there is absolutely no telling whether something bundled with this Windows build might have such a dependency.  Too bad windows doesn't publish this information with the developer previews.

For me, Quicken is the key app so I will risk the change.  I sure hope some bundled something isn't broken, but Quicken might surprise us all and deliver the obvious fix before I notice anything.

Photo of N777TY .

N777TY .

  • 270 Points 250 badge 2x thumb
MHO is while there clearly is a risk in making the change it'd be somewhat minimized by the fact that ONLY 32-bit hive is being changed.. so impact should be lessened considerably....  on a typical 64-bit OS, most of the apps (built in) will run 64-bit and they won't even look at the 32-bit registry hive..  that's why I was fairly comfortable making this temporary change.
Photo of CaptainRichard

CaptainRichard

  • 190 Points 100 badge 2x thumb
With latest build 5007 the registry patch is no longer working.  Any other suggestions??
Photo of Rob Harris

Rob Harris

  • 256 Points 250 badge 2x thumb
It's working fine for me....
Photo of CaptainRichard

CaptainRichard

  • 190 Points 100 badge 2x thumb
A reboot and reinstall of QB2017 fixed issue after registry fix
Photo of alphabeta

alphabeta

  • 2,128 Points 2k badge 2x thumb
All that should be required is redo of the registry edit.
Photo of Gene Douglass

Gene Douglass

  • 112 Points 100 badge 2x thumb
Latest Build 5007, just doing it again gets Quicken 2017 to work just fine.  All I did was put back to original values before the Windows update, then after update, retook ownership of keys, and changed back to 4.6.0202 like the directions say, Quicken back to working just fine!

This conversation is no longer open for comments or replies.