PC hanging on shutdown when reWASD doesn't properly disconnect the virtual controller

[reWASDer]

Hey there! We have released reWASD 5.5, and according to the feedback from other customers here, there are no sleep issues anymore.
I hope you will update to check

[Star-Lord]

Hello, simian

Thank you for your suggestion. Hope it will be helpful.

[simian]

I used to kill the process from Task Manager sometimes, if I remembered, because killing from the notification tray wasn't working. If I forgot to do that, Windows would be like 99% finished shutting down to the point of a black screen but the PC would not turn off. There was no ability to get task manager on screen, to complete the shut down. The only option available was to hold in the power button. To be clear the problem was with 5.4 after upgrading. Once I uninstalled 5.4 and reinstalled it, I had zero issues with shutdown.

I don't use sleep mode.

[Star-Lord]

Hello simian,

Thank you for your comment.

"I had varied success by forcing REWASD agents to close before shutdown" - only reWASD agent? You didn't kill the service process in the task manager, didn't you? Killing the agent was giving a proper option to shutdown?


And using the same 5.4 version you don't have a hanging problem while shutdown? Any issues with switching PC into sleep mode?

[simian]

I had the same problem with Windows 10 hanging at shutdown. My circumstance:

I had demoed version reWASD510-1302 sometime ago but purchased REWASD recently and upgraded the installed version with reWASD540-2368. For first couple of weeks Windows 10 would not shutdown properly if I had used the gamepad. I had varied success by forcing REWASD agents to close before shutdown.

I resolved the problem entirely by completely uninstalling and reinstalling (I backed up my mappings).

I noticed that the agent icon and name in the notification area was different than before (the one resembling a battery). I can't recall how it was different but I was of the opinion that perhaps something hadn't been replaced properly in the upgrade.

Hope that helps...

[Star-Lord]

Hello,

Great! Thank you for your feedback. Seems that the stack driver is correct. We will investigate this case more detailed and but to you with updates.

[Pratator]

Hi, here is the screenshot of the driver stack.
Cheers

[Star-Lord]

Hello, Pratator

Thank you for logs. It looks like the virtual controller is still in the system. We send system command to remove the virtual controller, it's removed from the physical bus but still handled in the system for some reasons. Perhaps some other driver or process. I made a video explaining how to check the driver stack of the Xbox virtual controller - https://streamable.com/i7bdxn. May I ask you to follow these steps to take the screenshot of the device stack. The footage contains steps of physical device connection, virtual controller creating, and check device stack.

Please, feel free to contact me if any questions come up.
Thank you in advance.

[Pratator]

Hi,
Here you go.
Cheers

[Star-Lord]

Hello,
Thank you for your reply. Waiting your log files.

[Pratator]

Hello,

The controller I am using is a PS3 Navigation Controller.

I am using it wirelessly.

I still have the same XBOX 360 for Windows controller displaying in joy.cpl, with Remap on or off (following Remap being turned on initially).

I will organise the logs on my next day off.

Thanks for your help.

[Star-Lord]

Hello,

So, when remap is OFF you still have the same XBOX 360 fo Windows controller displaying in joy.cpl as when remap is ON? Does the controller is displayed in joy.cpl if you discounted the physical controller?

In this case, would appreciate it if you collect the logs:

- Unplug all connected controllers
- Open reWASD via Administrator. Open Preferences - StartLog
- Plug the device via myflsah adapter and apply the config with virtual Xbox 360 (remap ON).
- Do remap OFF to remove the virtual controller. Open Preferences again and press Stop Log.
- Attach logs with the reply.


Thank you in advance.

[Pratator]

Hi,

The virtual 360 controller still remains even after remap is turned off.

When I check joy.cpl, the virtual 360 controller is still there and the pc hangs on restart or shutdown.

However, the pc can reboot or shutdown if I manually close the "game controller mapping service".

After I have manually ended the task "game controller mapping service", the controller shows as "Controller (MAGIC-NS).

[reWASDer]

8:55pm is when I tried to turn off remapping.

Hey there! We have checked the logs, but nothing suspicions is there. The virtual device was removed, and your controller works as normal.
I have only one idea at the moment. Maybe your game somehow "remembers" the virtual controller and that is why it hangs on shut down? Could you please ensure that you have closed the games and launchers (all of them) before you shut down?

[Star-Lord]

Hello,

temp89, thank you for the logs, will investigate it and I back with updates.

Pratator Is virtual controller (Xbox 360) still active? Does the problem persist if you turn remap OFF(not just close reWASD windows, but disable the virtual controller that the system sees only your physical controller)?