Runtime Error! R6016 when launch Explorer on Windows11 24H2

[alice0775]

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]

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

[m417z]

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.

[mkacct]

I also have this issue. Thanks for acknowledging it

[jlavis]

Hi. To start, I love WindHawk, btw. I just hate how Microsoft trashes features and such from previous Windows versions. WindHawk brings back loved features and more!

I'm still running 1.5.1. I don't see a newer version. Is it just still in dev/testing and will be released shortly? Thank you!

[m417z]

Thanks for the feedback @jlavis, I'm glad that you like Windhawk!

Is it just still in dev/testing and will be released shortly?

Yes. I'm not sure about "shortly", but I'm working on it.

[jlavis]

Yes. I'm not sure about "shortly", but I'm working on it.

Sorry, didn't mean to feel anxious.. I didn't know this bug was related to Windhawk.. I kept searching for memory issues with the latest Windows patch releases, but it looks like the issue was part of Windhawk. At least the issue is somewhat known and will be fixed/released at some point. I haven't been following on your release cadence. Thanks again!