Virpil devices won't allow my PC to sleep after 2004 update

I updated to Windows 10 2004 yesterday, and I had a problem with my PC display not turning off or going to sleep.

After a long investigative process, I have identified that it is my 3 Virpil devices that are causing the issue.

If I switch off my 2 WarBRD bases and CM2 throttle and have all other devices plugged in - including TM TPR pedals, XBox controller etc. - then everything is good. Whenever I switch on ANY of the 3 Virpil devices, the problem is back.

Any ideas?

revert back to previous windows version when this was working ok

Yep, but that is a last resort.

I've contacted Virpil support. Didn't sound too hopeful though. They basically said they were too busy to deal with the query!

At the moment, I am switching off the Virpil devices, which is a pain.

so even if you do a shutdown on your PC it keeps waking ?

Sorry, no. The problem is that it won't go to sleep or switch display off with any Virpil device connected. I have to switch them off and then everything is OK.

revert back to previous windows version when this was working ok

That can't be the solution. The world is evolving. If everybody had this attitude, we would still use Windows 3.11 today. The solution is rather that Virpil adapts its software to the new Windows version. Of course, Virpil needs some time to do this.

Sorry, no. The problem is that it won't go to sleep or switch display off with any Virpil device connected. I have to switch them off and then everything is OK.

Oh so you cannot use shutdown instead ?

That can't be the solution. The world is evolving. If everybody had this attitude, we would still use Windows 3.11 today. The solution is rather that Virpil adapts its software to the new Windows version. Of course, Virpil needs some time to do this.

Best guess is that the windows upgrade to the new windows 10 version has changed or reset some setting, causing this issue now

Maybe Op can go through his power profile settings and spot what has changed?

Suggesting some options to OP:

1. Try using shutdown instead see if that works

2. Try examining power profile setting in control panel to see if something has changed between old win version and this one

3. Try using Devcon or some other util to disable the virpil devices before going to sleep and then use it again after wake to enable them

4. Un-plug Virpil devices before sending PC to sleep

See which one is easiest for you to do

Yes, I can use shutdown, but I don't want to as I have scheduled tasks that run during the night.

Nothing has changed in the Windows power profile that I can see.

This is definitely a Virpil issue as my Thrustmaster devices are plugged in along with XBox controllers, VR headsets, etc. etc. and they all work OK. It's only when I switch on one or all of my 3 Virpil device that the issue occurs.

I don't have access to devcon, I'm afraid.

I suspect that the 2004 update has caused some incompatibility with Virpil devices.

I don't have access to devcon, I'm afraid.

think you can get it here

https://superuser.com/questions/1002950/quick-method-to-install-devcon-exe

Thanks. Tbh, it's easier switching the 3 Virpils off, but it doesn't solve the issue. I tend to walk away from my PC regularly and just let it sleep. I can't do that now. I've raised a ticket with Virpil. Let's see what they say.

On the other hand, it's not only Virpil that causes a problem.

When my Oculus runs, i have the same. When my Garmin Edge 810 is hooked up, it even restarts the computer when i shut it down. And i'm not on 2004 Windows yet.

On the other hand, it's not only Virpil that causes a problem.

When my Oculus runs, i have the same. When my Garmin Edge 810 is hooked up, it even restarts the computer when i shut it down. And i'm not on 2004 Windows yet.

Of course, there are other issues for other people, but my issue is Virpil which has just recently started happening.

OK, so I just borked one of my WarBRD bases as I accidentally loaded in a later version profile.

I watched

Please see attached. Am I shorting the right pins?

Not borked any more, I just couldn't see it as the USB devices were filtered.

So, I reverted the firmware to earlier version and it made no difference. I guess I'll just have to wait for Virpil to get back to me.

I reverted back to Windows 1909 and now everything is back to normal and all OK.

I've basically given up getting my Windows desktop computer to sleep on it's own. It seems every time I spend hours determining what the problem is and fixing it, something else is preventing it from sleeping a few weeks later.

I changed my power button function to put the computer to sleep, and just hit that every time I walk away from my computer now.

Personally, it’s only ever been an issue on this PC when I installed 2004, and even then, that was caused by Virpil devices.

For me, forcing sleep is not the answer as I have tasks that run during the night. They would mean that the PC would remain awake.

Amyway, I’m back on 1909 till this is resolved and all is good.

It has happened to me always when I leave any controller plugged in. I still don't have 2004 and it happens.

It has an explanation though: usually axis are always sending input as there is always some noise. For instance, a throttle value can be moving from let's say 1924 to 1925 and back constantly and without touching it. Windows or manufacturer software filters this and it doesn't translate into inputs in game or any other software however, input from the device is being sent constantly so it doesn't let Windows to go to sleep.

It is a very old problem and I've got rid of it by installing a powered usb HUB with switches so I can turn the devices off easily.

It has happened to me always when I leave any controller plugged in. I still don't have 2004 and it happens.

 

It has an explanation though: usually axis are always sending input as there is always some noise. For instance, a throttle value can be moving from let's say 1924 to 1925 and back constantly and without touching it. Windows or manufacturer software filters this and it doesn't translate into inputs in game or any other software however, input from the device is being sent constantly so it doesn't let Windows to go to sleep.

 

It is a very old problem and I've got rid of it by installing a powered usb HUB with switches so I can turn the devices off easily.

I think we're missing the point here. It is not a 'very old problem' for me. It has only started with Windows 2004. That is the point. Everything is all good again now that I'm back on 1909.

I also have a powered hub, and can, of course. remember to turn off the offending devives, but that is not the solution. Something in this new update has changed and it needs to be fixed by MS or Virpil or both.

Windows 10 2004 has been delayed for some time because of the many and varied problems it has been causing. Many systems can't be updated to it at all as of yet and Microsoft have warned against forcing the install. It should only be upgraded through windows update, when they make it available.

Its not Virpil software that is causing an issue because Virpil software is not used to drive the Virpil devices. Its all programmed in to the device that then uses a USB interface chip that is just like any other. Virpil don't make their own so its not likely to be their issue.

Until Microsoft sorts out its recent problems with updates you could look at using a USB hub with individual power switches for each port. They can be had for a reasonable cost. Then you just need to press a couple of buttons if you must have the latest Windows version.

Mine became available to update to 2004 on Saturday, so far no issues that I have noticed.

Do you have any Virpil devices, Don?

Do you have any Virpil devices, Don?

Yes but none hooked up at this time.

That can't be the solution. The world is evolving. If everybody had this attitude, we would still use Windows 3.11 today. The solution is rather that Virpil adapts its software to the new Windows version. Of course, Virpil needs some time to do this.

The solution was Microsoft released an update patch to fix what they broke with USB and sleep, nothing to do with Virpil

The solution was Microsoft released an update patch to fix what they broke with USB and sleep, nothing to do with Virpil

I know you've got a thing about MS, but we don't know that the solution came from them at all. It could well have been Virpil or some other manufacturer that provided the solution for all we know.

It was only Virpil and TM devices that were an issue for me. Other steering wheels, pedals, keyboards, controllers and mice were unaffected.