Sttub30-w11-x64 neded, Problem with memory integrity in winn 11 because of USB drivers STTub30

[Peter BENSCH]

Welcome, @PKoll.1​, to the community!

We are very sorry that you have this problem with your W11 machine, but it is the manufacturer's responsibility because they did not remove this software, which is normally only intended for development purposes, before delivery.

Anyway, I have given some advice in this thread on how to proceed. Please let us now if ths works for you.

If the problem is solved, please mark this thread as answered by selecting Select as best, as also explained here. This will help other users find that answer faster.

Regards

/Peter

[smoli.1]

Hi there, thank you for your answer.

As I said on another thread, your proposal isn't accurate and doesn't work. In my case, oem77.inf is associated with an XBOX driver.

All we need is an updated version of STTUB30.SYS (ST MICROELECTRONICS; VERSION: 3.0.5.0. Does it exist? Can you provide us a link to download the file if it does?

Much appreciated.

[smoli.1]

Please, you should take into consideration that removing the file causes the computer hangs on restart. Regards.

[Peter BENSCH]

As already mentioned, the driver is part of a package (DfuSE) for the development of STM32 devices, but has long been on NRND (Not Recommended for New Design). The driver should never have been used in a production system, which is why you must contact MSI to get a solution to the problem.

I'm so sorry, but I can't help you here.

Regards

/Peter

[cpryor]

Hello,

I'm a developer and need a working version of the Sttub30 .sys. Deletion is no solutio be cause we need to use it.

All references to a Sttub30-w11-x64 from 2015 with newer version that is compatible with core isolation.

But everything was deleted, because it was missused for MSI bluescreens.

The new DFU tool is No solution, because the driver device ID has changed and it needs complete other tools and driver and protocols.

We can not update all  devices for the new tool.

PLEASE. This one screenshot is the only hint that is left of the driver in the hole internet:

[Pavel A.]

@cpryor This driver is no longer needed. In modern Windows one should use winusb. To support older products, perhaps install a dedicated Windows PC with the integrity checks disabled. Or a Linux machine where this issue does not exist at all. Your IT can help you with this.

[cpryor]

-----

[cpryor]

@Pavel A.

Thank you peter for your reply.

The problem is, that there is no OS FutureDescriptor in the original DFU SE sample code. (I could add, but that does not change tousand devices at customers)

Even if i assign manual a winusb driver, the dfuSE Demo 3.0.6 is not searching for winusb devices and is it not listing it.

And this forcing on customer pc's will be very difficult because of needed inf, that needs sinature and licensing from Windwows.

Could you please try to find this working driver version? Somebody from your company must have it.