After each update of Fusion, Windows 10 hangs at next Hibernate

[crueby1]

This problem is back as of the last two Fusion updates: after the update is done and Fusion has restarted, all seems fine, but if I shut down Fusion and later try and hibernate my desktop PC (windows 10 latest version), the PC hangs partway through the hibernate shutdown. Screen goes black, but none of the devices including fans/keyboard turn off, and the power switch will not wake it back up again. Only way to wake the PC is to hold in the power button to hard boot it again.

This was a problem all of last year but went away several months ago. I and others have posted bugs about this numerous times, never any fix from Autodesk. Some have suggested using Sleep instead, that didn't help. Also was discussion about letting the Streamer.exe from Autodesk's folder finish, which takes 5 or 10 minutes after the update. That does not help either.

Anyone on the Fusion team ever look into this?? As a paid subscriber seems like SOME response is warranted.

[sutherland-]

Hi @crueby1 

Are you sure that all drivers of your system are up to date?

[crueby1]

Positive - they are all kept up to date. And to reiterate, the hang only happens when Fusion itself updates.

[sutherland-]

Have you tried to contact support directly regarding this? Link for contacting them is here.

[crueby1]

I did last year when it first started happening. They asked for more details on the system, had me check system error logs, that sort of thing. Then contact faded out. I dont recall who it was I interacted with. Based on other times I've contacted support, I'd say they are great when helping out with 'how do i do this' questions, but for actual bugs the best I've ever gotten was 'we have written it up and sent to engineering team', then nothing ever happens, not one bug I've reported has actually been fixed. The volume of people reporting the same sorts of problems on the forums for years bears this out, sadly. They are so focused on new features (which is good) that they never seem to go back and make sure the foundation is working right (which is bad, but common on large teams - I was a firmware/software engineer for 30+ years, have seen it many places)