Thunderbolt 3 dock shows as unsupported after reboot

[baatch]

Hi,

I have an HP Zbook Thunderbolt 3 dock connected to an iMac Late 2013 running Catalina 10.15.17.

I have followed all the instructions and got it working. The dock shows as HP Thunderbolt 3Dock

But if I reboot the computer it stops working and the dock shows as unsupported.

If I reconnect the cables it starts working again. Is this expected behavior that it can't survive a reboot? I was thinking of installing the OS on an SSD harddrive as connected through the thunderbolt 3 dock, but if it can't survive reboots it will not work..

Please help, attaching debug report

t3u-diagnose.txt

[rgov]

I thought this was documented somewhere but maybe not. Try attaching the Thunderbolt device after the reboot, without reloading the kext.

Extensions in /Library/Extensions should be loaded at boot and you can confirm by running kextstat | grep -i unblocker.

[rgov]

I don't know if it will be possible to do what you want (boot off an SSD) but probably not with Thunderbolt3Unblocker.

First the Mac EFI locates the boot device, then loads macOS off of the device, and then macOS loads Thunderbolt3Unblocker. It happens way too late in the process.

I don't know whether Thunderbolt devices are blocked the same way in EFI but T3U does not affect that.

[superbillgates]

I thought this was documented somewhere but maybe not. Try attaching the Thunderbolt device after the reboot, without reloading the kext.

Extensions in /Library/Extensions should be loaded at boot and you can confirm by running kextstat | grep -i unblocker.

I am suffering totally the same problem, where the system version is macOS 12.2 and the machine is MacBook Pro 13.3inch 2017.

Would you please fix the bug, thanks very much.

[charlie0129]

Slightly off-topic: in case someone MUST have their devices to survive reboots without re-attaching, although not recommended, they can try the old KhaosT's TB3 Enabler, which this repo replaces. I have used both of them before. The old one does not officially support macOS version > 10.14.5, but as long as it finds the bytes to modify, it should work. At least I can confirm it works on 10.15.7.

But still, the old one modifies system files so the risk is much higher. Also, you need to solve the problems you might encounter along the way. For example, macOS after 10.15 don't mount their root directory rw, so the old patch cannot make modifications, this should be (FYI, and can be) solved first.

Regarding the particular problem in this issue, I don't think the old patch will help either, simply because the Mac EFI, which is NOT affected by both patch, won't load the unsupported device at the first place, as rgov asys #75 (comment)

[xenek]

Hi, I found KextBeast and a more recent version (link found in comments issue #77 by Wangsoft) - when installing on Sonoma on ancient Macbook Air mid 2013 Hardware, was persistent over reboots. I had to install to system/extensions using Kextbeast, on a perfectly fresh install of Sonoma 14.1.2 - an install on a ventura and sonoma earlier wasn't persistent and I had to rerun KextBeast every time.