Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Runtime Error! R6016 when launch Explorer on Windows11 24H2 #342

Open
alice0775 opened this issue Dec 7, 2024 · 3 comments
Open

Runtime Error! R6016 when launch Explorer on Windows11 24H2 #342

alice0775 opened this issue Dec 7, 2024 · 3 comments
Labels
bug Something isn't working planned The issue is planned to be addressed

Comments

@alice0775
Copy link

The following error appears when launch Explorer if enable Taskbar height and icon size mod.
The error appears 80% probability.


Microsoft Visual C++ Runtime Library

Runtime Error!
R6016

  • not enough space for thread data

Software:

Edition Windows 11 Home
Version 24H2
Installed on ‎11/‎24/‎2024
OS build 26100.2454
Experience Windows Feature Experience Pack 1000.26100.36.0

Windhawk v1.5.1
Taskbar height and icon size 1.2.16

Prerequisite:

  1. Update Windows to 24H2
  2. Install Windhawk v1.5.1 and Taskbar height and icon size 1.2.16 and enable it
  3. Click on Start button > Settings > Personalization > Start > Folders
  4. Turn on File Explorer

Steps to reproduce:

  1. Close all explorer window if any
  2. Click on Start button
  3. Click on Explorer icon at the bottom right of the Start menu
  4. Repeat from step 1 if the error not appear.

Actual results:
The runtime error R6016 appears

Expected results:
No error

@alice0775 alice0775 added the bug Something isn't working label Dec 7, 2024
@alice0775 alice0775 changed the title Runtime Error! R6016 when launch Explorer Runtime Error! R6016 when launch Explorer on Windows11 24H2 Dec 7, 2024
@alice0775
Copy link
Author

The bug only occurs in the STR step in comment#0.
Even if this error occurs, that Explorer seems to work fine.

@m417z
Copy link
Member

m417z commented Dec 7, 2024

It was discussed here: ramensoftware/windhawk-mods#1178. I plan on including a fix in the next Windhawk version.

It's a known issue with any mod that injects into explorer and uses the C++ runtime library. The problem is caused by a combination of Windhawk and msvcrt (Microsoft C runtime library), and may happen when a new explorer.exe process starts, sends a message to the main explorer.exe process to open a new window, and exits right away. That doesn't happen in most cases (opening a new folder, Win+E, etc.), but may happen if you run explorer.exe directly via a shortcut, Win+R, etc.

A workaround will be added to the next Windhawk version. Meanwhile, you can install this mod as a temporary workaround:
https://gist.github.com/m417z/f0cdf071868a6f31210e84dd0d444055

To install it, click the bottom right button to create a new mod, replace the code, click "Compile Mod", then "Exit Editing Mode".

Note that the error occurs when the process is shutting down, so it's not really harmful, but it can be annoying.

@m417z m417z added the planned The issue is planned to be addressed label Dec 7, 2024
@mkacct
Copy link

mkacct commented Dec 16, 2024

I also have this issue. Thanks for acknowledging it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working planned The issue is planned to be addressed
Projects
None yet
Development

No branches or pull requests

3 participants