Slow BD Playing and Ripping with two different drives

QuiGonJosh said:

So I've been using a Pioneer external BD player for months now and it's work fine, both playing and ripping discs. No issues. But then last week, after a Windows update, it wouldn't read at anything above 0.3x speed. Playback is choppy as hell and ripping is at a crawl at 0.0x at times. I figured the drive had crapped out, so I bought a ASUS BW-16D1X, but I'm getting the same problems. My USB ports are fine. Drivers updated. Firmware updated on both BD drives. DVD's read rates are fine. Any ideas?

Click to expand...

What windows update was this exactly? It's possible that the Universal Serial Bus controller drivers got updated and aren't working well. I'd go through your USB devices and your BD driver and see in device manager if the "roll back driver" button is available on any of those things and try that first.

markmon1 said:

What windows update was this exactly? It's possible that the Universal Serial Bus controller drivers got updated and aren't working well. I'd go through your USB devices and your BD driver and see in device manager if the "roll back driver" button is available on any of those things and try that first.

Click to expand...

Roll Back Driver is greyed out for both BD drives and USB 3.0 in Device Manager.

This was the last update on July 6th and since then the BD drives have been kaput.

July 6, 2021—KB5004945 (OS Builds 19041.1083, 19042.1083, and 19043.1083)

QuiGonJosh said:

Roll Back Driver is greyed out for both BD drives and USB 3.0 in Device Manager.

This was the last update on July 6th and since then the BD drives have been kaput.

July 6, 2021—KB5004945 (OS Builds 19041.1083, 19042.1083, and 19043.1083)

Click to expand...

See if there's a system restore point set prior to the update and restore to that. Windows update always creates a restore point.

markmon1 said:

See if there's a system restore point set prior to the update and restore to that. Windows update always creates a restore point.

Click to expand...

There's a new update from yesterday for Windows 10. I'm going to install that one first. It says there's a fix for USB devices connecting to printers. I don't know if that will fix anything. Who knows. If not, I'll try to go restore before the last update on the 6th.

Is uninstalling updates similar to a restore point?

QuiGonJosh said:

Is uninstalling updates similar to a restore point?

Click to expand...

I mean it only is if you know exactly what changed and what to uninstall. The restore point just puts everything back to how it was before the 'event' occurred. So since you really have no idea what broke this, no they won't be the same. Use the system restore.

markmon1 said:

I mean it only is if you know exactly what changed and what to uninstall. The restore point just puts everything back to how it was before the 'event' occurred. So since you really have no idea what broke this, no they won't be the same. Use the system restore.

Click to expand...

Gotcha. Thanks.

Well, that update did nothing. Guess I'll try the restore.

QuiGonJosh said:

There's a new update from yesterday for Windows 10. I'm going to install that one first. It says there's a fix for USB devices connecting to printers. I don't know if that will fix anything. Who knows. If not, I'll try to go restore before the last update on the 6th.

Click to expand...

I didn't see this response earlier. Be careful here. I believe Windows update only keeps one restore point so if you do another update, the previous restore point me be replaced with your system as it stands today.

You can uninstall Windows Updates just like you can with any other software application. Open the Control Panel and select the Programs and Features option. From there you can view installed updates. Just right-click on the updates you wish to uninstall and select the Uninstall option. Updates are dated so it shouldn't had to see which updates were the most recent ones installed.

There was an issue with one of the most recent updates they sent out, but I believe they may have already sent out a newer update to fix the problem. I forget exactly what the issue was.