Downloading & Installing software updates R59.6 - process stalls at Optimizing and Executing Files.
Why was this closed in April when the problem still exists when updating as of today? In addition ever since update prior to this one, the software runs a lot slower. What trackers are you running for the government or yourselves to cause this slow down?
I think we pay Intuit way too much in yearly fees to have to put up with this.
Comments
-
You don't pay Intuit anything unless you use Turbotax or Quickbooks. Intuit hasn't owned Quicken for a number of years.
Quicken Windows user since 1993.
0 -
I also saw an unusually long delay in the "optimizing" phase today. I let it run and did other things around the house. When I returned to my Win10 PC, it had completed and all was well.
@catbait did you allow the update to complete, and were you OK after that?
Quicken user since version 2 for DOS, now using QWin Biz & Personal Subscription (US) on Win10 Pro.
1 -
After 30 minutes, I stopped it as I needed to get in Quicken to check things. I'll let it go when I am done tonight and see if it loads… 😴
0 -
Let it run and checked it after 7 hours. Yep, it installed, but I have no real clue how long it took. I think the install team needs to change the phrase "installation may take a little while" to "run the installation over night"! It reminded me of the old Windows updates of the late nineties.
1 -
I had the same problem, my update ran for a long time, probably hours. The problem with slow Quicken updates has been happening for a long time.
Computer is 64bit, win10 pro, Version 10.0.19045 Build 19045
Quicken Classic Business and Personal R59.6 Build 27.1.59.6 (after updating)
I took some troubleshooting steps using procmon.exe - from microsoft, during the update, to monitor all system processes over time. Started procmon monitoring after the update had started, stopped monitoring after approx. 20 mins.
Quicken's msiclean32.exe was accessing the registry constantly during this time. This program was using one process id, #1193184. It read through part of my registry 522 times during 20 min, approx going through 46,744 registry entries every 2 sec. That is 522*46,744=~24 million registry accesses in 20 min.
When you see <RegMSICompPath> , substitute it with "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components" (i just did this to condense)
*I read in one place that this is path to MSI install file components registered under System Account.*
MSIClean32 operations for 20 min.
___________
A. Sequence, MSIClean32 registry enumeration, repeated 522 times.
(Same result every time through)
___________
RegQueryKey HKLM Handle Tags:0x0 Success
RegOpenKey <RegMSICompPath>\Components Granted Access:All Access Success
Search through many reg keys:
RegEnumKey <RegMSICompPath> SUCCESS Index: 0, Name: 00010C4985120CD6221FB3C87C6DF163
RegEnumKey <RegMSICompPath> SUCCESS Index: 1, Name: 00029BB0C6A0F9E3A27D18D5B33A1C9A
… (repeats RegEnumKey operation 46,740 times using index:2-46,742, accessing different Key Names)
RegEnumKey <RegMSICompPath> SUCCESS Index: 46,743, Name: FFFE6BB28DBF17C44B7EBA031E0007FE
RegEnumKey <RegMSICompPath> SUCCESS Index: 46,744, Name: FFFE8B14A86A46F0B1FD1270E2367E68
Close search:
RegEnumKey <RegMSICompPath> Index:46,745, Length:288 NO MORE ENTRIES
RegEnumValue <RegMSICompPath> Index: 0, Length: 522 NO MORE ENTRIES
RegCloseKey <RegMSICompPath> SUCCESS
___________
After reading through all 46,744 registry entries, performed B. Sequence
B. Sequence, MSIClean32 Single key enumeration, repeated 522 times.
(Different KeyName and Different RegEnumValues every time through)
___________
RegQueryKey HKLM SUCCESS Query: HandleTags, HandleTags: 0x0
RegOpenKey <RegMSICompPath>\<KeyName, example:79A144A4313F16FE6855845D96FC65D0> SUCCESS Desired Access: Maximum Allowed, Granted Access: All Access
RegSetInfoKey <RegMSICompPath>\<KeyName, example:79A144A4313F16FE6855845D96FC65D0> SUCCESS KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
RegEnumValue <RegMSICompPath>\<example:79A144A4313F16FE6855845D96FC65D0> SUCCESS Index: 0, Name: <RegEnumValue example: 68B1C7EDFE7220D488E671CC438530B4, Type: REG_SZ, Length: 150, Data: C:\Program Files (x86)\Nuance\Nuance Cloud Connector\ger_backup-intro.html>
RegEnumValue <RegMSICompPath>\<KeyName example:79A144A4313F16FE6855845D96FC65D0> NO MORE ENTRIES Index: 1, Length: 520
RegCloseKey <RegMSICompPath>\<KeyName example:79A144A4313F16FE6855845D96FC65D0> SUCCESS
___________
After A. Sequence and B. Sequence sections, starts back at A. Sequence
After 20min this was still going through the registry, and after a day I noticed that the update did complete.
The patch was stored under C:\ProgramData\Quicken\Inet\Common\patch\quickenPatch\ in a folder <this time> named "w190". Apparently after the update completed the folder was removed.
Observations:
MSIClean32 seems to be searching through 10s of thousands of entries to find one entry that it looks at. The entry it enumerates usually doesn't have anything to do with Quicken. Is there a logic flaw in the looping sequence? Can any programmer make sense of what might be wrong?
1
