the procedure entry point set threadDescription could not be located in dynamic link librery'c;\program files\shortcut\Qt6Core,dll.

Question

the procedure entry point set threadDescription could not be located in dynamic link librery'c;\program files\shortcut\Qt6Core,dll.

anandh joy 0

help me to solve these problem and give the brief explanation *windows for home|Previos window version|Apps

0 comments

2 answers

Your answer

Answer 1

Thomas4-N 22,390 Microsoft External Staff Moderator

Hello anandh joy,

That error usually points to the app (this looks like Shotcut from the path) needing a newer Windows version than what's on your PC — the Qt component it bundles calls a Windows function that older builds just don't have.

Before I give you the exact fix, could you confirm which Windows version you're on? Press Win + R, type winver, and hit Enter — then share the line that reads something like "Version 1607 (OS Build 14393.xxxx)".

That'll tell me whether the fix is simply updating Windows, or installing an older build of the app that still supports your version.

Thomas4-N 22,390 Reputation points Microsoft External Staff Moderator

2026-06-06T16:47:10.53+00:00

Hello anandh joy,

Just check in to see how things are going. Let me know if you need anything.
Roger YNWA 0 Reputation points

2026-10-04T08:08:26.0933333+00:00

Hi Thomas, I have Version 10.0 (OS Build 10240: Service Pack 1) I get it together with Spotify and I assume it's maybe not available with the app I have in my version? I see the icon but not able to uninstall either.
Thomas4-N 22,390 Reputation points Microsoft External Staff Moderator

2026-10-04T14:48:38.25+00:00

Hello Roger, Windows build 10240 is too old for the SetThreadDescription function mentioned in this thread, so updating Windows is the fix to pursue if you’re seeing that same error. If the app is Shotcut, its current version requires Windows 10 version 1809 or later.

For the app you can’t remove, open Control Panel > Programs > Programs and Features, select the app, and choose Uninstall. If that fails, try Microsoft’s Program Install and Uninstall troubleshooter. I wouldn’t remove Spotify unless you’ve confirmed it’s the app you want to uninstall.
Roger YNWA 0 Reputation points

2026-10-05T06:20:33.0933333+00:00

Hi Thomas, I have to use Spotify on the web instead. I am trying to get removed after startup every time get pop up to install .NET Framework version v4.8 and 4.7.2? I am not sure I got this after trying to upgrade Win10 as seems not to work as it's failing every time. Lap top is old of course 2016. Upgrade to Win 11 will my PC be able to work with that version? Br
Thomas4-N 22,390 Reputation points Microsoft External Staff Moderator

2026-10-08T08:31:20.65+00:00

Hello Roger,

If I understand this correctly, the original Shotcut / SetThreadDescription error is probably not the main thing anymore. You’re using Spotify in the browser, Windows 10 is still on build 10240, the in-place upgrade keeps failing, and something is prompting for .NET Framework 4.8 / 4.7.2 at startup.

On that older build, current Shotcut isn’t expected to run. SetThreadDescription only exists from Windows 10 version 1607 onward, and current Shotcut asks for 1809 or later. Using Spotify on the web is a reasonable workaround for that part.

I wouldn’t keep chasing the .NET popup on its own. It often shows up after a failed upgrade or leftover installer, so it may not be the root issue. If you can, note which program is asking for .NET, or share a screenshot of that prompt.

The more important piece is the Windows 10 upgrade failing every time. Without the exact error, I can’t be sure what’s blocking it. If you can paste the message, or a screenshot, we can look at that next.

On Windows 11: I wouldn’t assume a 2016 laptop will work with it. Windows 11 needs things like a compatible 64-bit processor, TPM 2.0, UEFI with Secure Boot, 4 GB RAM, and 64 GB storage. A lot of 2016 machines miss the CPU or TPM check. The safer check is Microsoft’s PC Health Check app, rather than trying the upgrade blindly.

If possible, you can share the Windows 10 upgrade error (and optionally a PC Health Check result), and then we can go from there.
Roger YNWA 0 Reputation points

2026-10-09T07:05:29.54+00:00

Hello Thomas, thank you for all feedback. It's Softphoneintegrations.exe and LSBUpdater.exe asking for NET Framework 4.8 / 4.7.2. When upgrade Windows it's not enough storage so I added an external also but still not able to work?

Br
Roger YNWA 0 Reputation points

2026-10-09T07:50:45.68+00:00

See screen error in Swedish.
Thomas4-N 22,390 Reputation points Microsoft External Staff Moderator

2026-10-09T15:17:04.5466667+00:00

Hello Roger YNWA,

Thank you, that clarifies it. Softphoneintegrations.exe and LSBUUpdater.exe are causing the .NET prompts, but I would focus first on getting Windows upgraded.

Simply connecting an external drive does not automatically give Windows enough upgrade space. First, run Disk Cleanup, select Clean up system files, and remove unneeded temporary and Windows Update files from the C: drive.

Then return to Settings > Update & Security > Windows Update. If Windows displays Fix issues, select it and choose an external drive with at least 10 GB of free space. Please note that Windows may still require some free space on the internal C: drive even when external storage is used.

Microsoft’s instructions are here: Free up space for Windows updates

If the upgrade still fails, the screenshot currently shows only a general message rather than the actual cause. Please share any error code shown in View update history, or run Microsoft’s SetupDiag and share the final result from SetupDiagResults.log.

Once Windows is successfully upgraded, check whether the .NET prompts remain before trying to repair or remove those two programs.

Answer 2

The error indicates that the program is trying to call a function (SetThreadDescription) that does not exist in the version of the DLL (Qt6Core.dll) or Windows being used. This is a DLL entry‑point problem: the application expects a specific exported function in a DLL, but the loader cannot find it.

In general, this happens when:

The DLL is built for a newer Windows version than the one installed, and it calls APIs that the older OS does not provide.
The application or its libraries are mismatched (for example, an older EXE with a newer or incompatible Qt6Core.dll, or vice versa).

From the documentation:

A DLL exposes procedures (functions) as entry points. If the entry point name or ordinal does not match what the caller expects, the loader reports that it cannot find the entry point in the specified DLL.
In Visual Basic/.NET scenarios, a similar error appears as “Unable to find entry point <name> in DLL <filename>”, and the fix is to ensure the procedure name and casing match exactly.

Applied to this case, the practical resolutions are:

Ensure the application and Qt libraries match
- Reinstall or repair the application that uses Qt6Core.dll so it deploys the correct version of Qt for that program.
- Avoid mixing Qt DLLs from different applications or versions in the same folder.
Ensure the OS supports the required API
- SetThreadDescription is a Windows API exported by newer Windows builds. On older Windows versions, this function is not available, so any DLL or program that requires it will fail to load.
- If the OS is an older “previous Windows version”, the only reliable fix is to upgrade Windows to a version that supports the API required by the Qt build in use.
Avoid incorrect or corrupted DLLs
- If a third‑party installer placed an incompatible Qt6Core.dll under C:\Program Files\shortcut\, uninstall that program and reinstall a version that officially supports the current Windows version.

Brief explanation:

A dynamic link library (DLL) contains functions that programs call at run time.
Each callable function has an “entry point” (its exported name or ordinal).
When a program starts, Windows checks that every required entry point exists in each DLL. If a required entry point is missing, the loader reports an error like “the procedure entry point … could not be located in the dynamic link library …” and the program cannot start.

In this scenario, the program expects the SetThreadDescription entry point but the combination of Windows version and Qt6Core.dll does not provide it, so the loader fails.

References: