utmapp
Cannot access TPM data.
Describe the issue
The other day I tried to create a Windows VM and failed since trying to run it resulted in an error, "Cannot access TPM data." The next day I tried again to make a new VM and it miraculously worked! Today however, I went to launch the same VM from the day before and was once again met with "Cannot access TPM data."
Configuration
- UTM Version: 4.5.4 (100)
- macOS Version: 15.1 Beta (24B5035e)
- Mac Chip: M1
Debug log
Attempting to enable "Debug Logging" for the VM fails with the error "The file couldn’t be opened."
Upload VM
Today it seems to work fine, not closing this yet though since I don't expect it to keep working. Reminds me of the "can't print on Tuesdays" bug lol
I'm facing the same issue, also on the 15.1 beta - restarting macOS seems to fix it temporarily.
Hi, same here. On macOS 15.0 final.
-->>> RESOLVED : by reseting UEFI settings in VM Settings / QEMU sub menu
Same here, just updated from 4.4.5 to 4.5.4 to match thread. Running 15.0 final. M1 chip. Attempting to Reset UEFI / QEMU sub menu results in "The file couldn't be opened".
Same here, just updated from 4.4.5 to 4.5.4 to match thread. Running 15.0 final. M1 chip. Attempting to Reset UEFI / QEMU sub menu results in "The file couldn't be opened".
Same issue here.
The problem is repeatable. Every time I unplug my macBook Pro (M1 Ultra) from my home office and plug it into my work office (and vice versa) it happens upon plugin at the other location. This requires a reboot to clear the condition.
Hi, I confirm that the reboot works for me too but it is not a comfortable solution. Has anyone found a better method?
Update to 15.0.1. That's your better method.
:-) Thanks. I'll try tonight. I'll give you feedback in few days.
Issue present on 15.0.1 on m1 Pro. Attempting to "Reset UEFI Variables" under QEMU submenu results in "The file could not be opened." Rebooting temporarily fixes the issue. My machine has been up for 1 day 14 minutes.
Two errors in the console messages:
error 03:51:39.905044-0400 QEMUHelper os_unix.c:49437: (2) open(/private/var/db/DetachedSignatures) - No such file or directory
error 03:51:39.905031-0400 QEMUHelper cannot open file at line 49437 of [1b37c146ee]
Can someone provide a sysdiagnose? Note that it may contain identifiers but it will only be used in diagnosing the issue and then be deleted. You can send the dump to dev at getutm dot app
Hmm, after a host reboot the 'Cannot access TPM data' message is gone.
Settings > QEMU > Reset UEFI vars, also give an ~~access denied~~ error before the reboot (probably the above "The file could not be opened." error)
I'm on macOS Sequoia 15.0.1
Looks like a bug in macOS that doesn't allow the App to access its Container, after some amount of uptime (maybe network address / hostname change?).
Normally at: /Users/<username>/Library/Containers/com.utmapp.UTM/Data/Documents/<VM Naem>.utm/Data/{efi_vars.fd,tpmdata}. Unix access rights seemed OK at the time.
A bug in macOS App Sandbox?
Update to 15.0.1. That's your better method.
:-) Thanks. I'll try tonight. I'll give you feedback in few days.
I have no problem anymore. I don't know why.
Sequoia 15.1
MacOS 15.0.1 UTM 4.5.4 (100) VM: Windows 11 ARM
I have the same problem, and reboot MacOS can temporarily fix it.
MacOS 15.0.1 (M3 Pro Late '23 MacBook Pro) UTM 4.5.4 (100) VM: Windows 11 ARM
Same exact problem here. Why isn't this being fixed?
Same issue here, MacOS Sequoia 15.0 checking Reset UFEI variables and then saving brings up the message "The file couldn’t be opened." After I hit "ok" the box is unchecked.
Also cant add a shared directory to a MacOS VM it says the same "The file couldn’t be opened." message.
Edit: After a restart the MacOS loads and the shared folder is applied. The Windows 11 VM starts without the error but now it looks like it's in some kind of shell. To be fair I've never turned on this windows vm before and I saw this same shell / boot loader screen on an x86 iso I tried to run as ARM64. I did get my windows 11 iso from CrystalFetch tho and it did say Apple Silicon so I'm not sure what to believe.
Edit 2: Looks like updating to 15.1 fixed it ¯_(ツ)_/¯.
It looks like this is linked to #6639.
Quoting the relevant text from the link posted by @tonilampela in https://github.com/utmapp/UTM/issues/6639#issuecomment-2431688538:
We've tracked down the problem to an issue with macOS 15.0 (Sequoia). Technically this involves their "Bookmark" resolution code ... It also only happens a little while after a device restart (about 2-6 hours usually), so it's a bit of a "heisenbug", very difficult to track down. Restarting your device or logging out/in also fixes things because it restarts the process which handles bookmarks on Apple's side. ...
Apple have acknowledged the issue and believe they have already fixed it in macOS 15.1 Beta 4. So updating to that beta version of macOS should fix this too.
~ https://www.reddit.com/r/strongbox/comments/1fo7z20/comment/lp5mtnu/
So rebooting should be a temporary fix to get a VM running; or upgrade to macOS 15.1 RC.
Hi, same here. On macOS 15.0 final.
-->>> RESOLVED : by reseting UEFI settings in VM Settings / QEMU sub menu
I got 'This file couldn't be opened' which I suppose is the root cause. I just shut down the VM normally.
