![]() But would be great to hear if it also fixes those problems for the rest of you which are quite common from what I've I ran into a similar situation in attempting to install the driver after attempting to install the certificate, but realized I was installing the certificate incorrectly, but was eventually successful. Hope that makes any sense to you, and as I said it worked for me on my particular setup. They are exactly the same, only difference is on the. sys file with the intel driver online ( ). If you don't trust a self signed driver (you would do well) then go ahead and binary compare the. ![]() I'm not driver or hardware expert by any means, so I don't know for sure but I think it's related to the TBT security where on Apple devices it's disabled.Īnyway, since I got tired of manually replacing that file on every windows update (I'm on the windows insider dev channel) I decided to go ahead and make my own version of the driver mixing Apple. ![]() There were a few differences but the one that caught my eye was one referencing a BusDriverMode registry key being set to 0x0 on the Intel one while on the Apple side it was set as 0x1. So I compared the 1.41.613 driver provided by apple with the same version from intel, then that sys file was exactly the same and only the. ![]() Sometimes it rebooted sometimes the TB3 port got disabled.īy trial and error I found out that if just hand replaced the TbtBusDrv.sys of newer drivers inside Windows\System32\Drivers without actually installing the new driver itself using the inf file then it fixed most of my TB3 issues that I discribed on the OP. I just can speak for my particular case ( MBP 16 RTX 2070) where if I installed the official drivers it prevented from booting with the egpu connected.
0 Comments
Leave a Reply. |