(FYI - I don't know if this exact version of "slow" shutdown pertained to 5.0).
I upgraded my Windows 10 installation of HW5.0 to 5.0.1, with no known issues nor problems. I stumbled on a delay in shutting down HW. In the simplest case, I cleanly start HW, load a small instrument (I've been using the SP Klavichord for this test.) The PC is fast, ~2 seconds from "Load Organ..." to playable. Play a few notes, then either click on the close button (upper right-hand corner "X" on the main window) or use the File->Exit menu command. HW begins its shutdown, but then hangs with all its windows still painted, but HW goes non-responsive. One CPU core goes to 100% due to HW, but Windows Task Manager shows no paging or I/O on behalf of HW. Seems to average about 30-60 seconds, then it terminates. This delay happens most, but not all of the time. The system as a whole remains fully responsive, only HW seems affected. This behavior occurs with or without a Page File allocated to the OS.
One work around I discovered - if I cold-start another program that opens a window, such as Task Manger or a browser, then HW immediately completes its shutdown as the second program's window paints. But the new program seems to need to be a complete fresh task instance - re-invoking something that stayed resident in the background does not unfreeze HW. When I use the menu File->Exit command, HW's little Progress-bar window paints, but also freezes about 1 second into the shutdown.
My OS is the latest general release Windows 10 Pro (1909), patched up to date, all drivers et al current and so forth.
Cheers, Bob
I upgraded my Windows 10 installation of HW5.0 to 5.0.1, with no known issues nor problems. I stumbled on a delay in shutting down HW. In the simplest case, I cleanly start HW, load a small instrument (I've been using the SP Klavichord for this test.) The PC is fast, ~2 seconds from "Load Organ..." to playable. Play a few notes, then either click on the close button (upper right-hand corner "X" on the main window) or use the File->Exit menu command. HW begins its shutdown, but then hangs with all its windows still painted, but HW goes non-responsive. One CPU core goes to 100% due to HW, but Windows Task Manager shows no paging or I/O on behalf of HW. Seems to average about 30-60 seconds, then it terminates. This delay happens most, but not all of the time. The system as a whole remains fully responsive, only HW seems affected. This behavior occurs with or without a Page File allocated to the OS.
One work around I discovered - if I cold-start another program that opens a window, such as Task Manger or a browser, then HW immediately completes its shutdown as the second program's window paints. But the new program seems to need to be a complete fresh task instance - re-invoking something that stayed resident in the background does not unfreeze HW. When I use the menu File->Exit command, HW's little Progress-bar window paints, but also freezes about 1 second into the shutdown.
My OS is the latest general release Windows 10 Pro (1909), patched up to date, all drivers et al current and so forth.
Cheers, Bob
Cheers, Bob