New install, crashes when opening or creating any file
I am setting up a new Windows 11 machine. I installed Quicken which updated to R51.10. Quicken can open by holding Ctrl and Shift, but if I try to create a new file, open from a backup file, validate a prior file, or open an old file, it crashes.
Any file causes it to crash, doesn't matter if it comes from the old machine or is created fresh on the new computer. Also - the old file will open fine on the old computer - also Windows 11, on R50.16 (and attempting to update the old computer insists it is on the most recent version).
Tried uninstalling and reinstalling twice. Tried manually patching twice. Contacted support who has opened a ticket for me to call in about on Monday, but if anyone has seen this issue before and knows a fix, I would be grateful.
Comments
-
Hung during OSU, Crash at Startup or other unexplainable malfunctions in Quicken for Windows
Please verify this:
In Windows Control Panel / System / Advanced System Settings / Environment Variables ensure that both the TEMP and TMP variables point to a valid and existing folder, typically C:\Windows\Temp or C:\Users\your_username_here\AppData\Local\Temp
If they point to an incorrect or non-existent folder or drive change both variables to an existing folder on C:\ (or create one) e.g., C:\Temp, and reboot Windows.If the Temp folder is located on a too-small SSD C: - drive and you have an internal standard hard disk, too, move the Temp folder to the internal hard disk and change the TEMP and TMP variables
If the folder exists … does your Windows User Account have proper access rights to this folder?
If Quicken cannot create and use temporary files, all sorts of malfunctions will occur.
If the Temp folder is full of junk, clean it out. Delete all files and subfolders within the Temp folder structure that Windows allows you to delete. You may have to skip a few that are actively in use.Make sure that files in the Temp folder are NOT accessed by cloud backup software at all.
Run CHKDSK C: /r on your C: - drive (or perform Error Checking from Windows File Explorer, Properties, Tools tab)
0 -
It was a Windows issue. Since it was a brand new systems build, I just reset Windows and started over and lo and behold it worked.
0