[Bug]: TranslucentTB has encountered a fatal error and cannot continue executing. Failed to initialize XAML Diagnostics 0x80070102: The wait operation timed out.
Ekcum opened this issue · comments
Please check for a duplicate first
- I have checked the issue tracker if my bug has already been fixed or answered in another (possibly closed) issue.
Steps to reproduce the issue
Its running and suddenly its crashing.
Expected results
It shouldnt crash.
Actual results
It crashes.
Windows version
Windows 11 Insider builds (builds 22623 and up). Please mention exact build.
Other details
The win version is 22635.3139
Relevant log output
No response
I am experiencing the same issue as described in the original post. Despite having tried various solutions such as restarting my computer, the problem persists. The program starts up then crashes with a fatal error. The error message I receive is slightly different, indicating 0x80070490: Element not found
, but it seems to be related to the same underlying issue with initializing XAML Diagnostics.
My system is running Windows Version 23H2 OS Build 22631.3085.
I have the same problem started today right after installing Win11 update "2024-01 Cumulative Update Preview for Windows 11 Version 23H2 for x64-based Systems (KB5034204)" + "Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.403.3670.0) - Current Channel (Broad)"
Now I am currently at Win11 Pro 23H2 Installed on 10/6/2022 | OS built 22631.3085 | Windows Feature Experience Pack 1000.22684.1000.0
I hope it helps. Let me know if I can provide more info :) Otherwise I am very happy with the program! And I am looking forwards to use it again
Same since last Windows Update (KB5034765)
Same issue for me but with 0x80070490: Element not found
This happens for me too.
It doesn't always happen but it happens half of the time.
Error:
TranslucentTB has encountered a fatal error and cannot continue executing.
Failed to initialize XAML Diagnostics.
0x80070102: The wait operation timed out.
Same, in my case this happens when I hide the task bar using borderless window gaming app
this is still happening to me too. A temporary solution is to run the app by yourself sometimes works, but I want it to run on its own on startup.