SyMenu - Recent Posts

Topic "SyMenu 8.16" a message from sl23

Tue, 13 Oct 2026 20:40:34 GMT

I am almost there, well, about halfway to a release. Should I upload the source to the github repo? Or do you want it kept private? Also, do you want to review the code to make sure it is suitable rather than me just releasing the plugin?

The final behaviour will be:

SyMenu startup + already current: no popup.
SyMenu startup + successful first install/update: no popup.
SyMenu startup + failure: show an error.
User clicks AudioPlugins: perform a fresh online check and always show the result.
Future SPS Manager manual refresh notification: perform the same check/update silently, then return control to SyMenu.

Too late! I'll email you the entire project so you can check and let me know when its ok to release it or whether its ok to upload the project to github.
Thanks for your help with this!

EDIT: email sent.

edited by sl23 on 13/10/2026

Topic "SyMenu 8.16" a message from sl23

Tue, 13 Oct 2026 18:05:11 GMT

Hi, I have one small issue. I havent really started this yet, but am at the initial development stage, planning. I have found one flaw in the example plugin, or rather ChatGPT has. There is no way to know if a user has clicked the Update App Definitions button in the SPS Manager. If my suite is loaded and I click that, it is expected that a check/download would be performed, yes? But the current test plugin does not have that ability yet. Would you be able to add that or have I missed something?

Thanks much appreciated.

Topic "SyMenu 8.16" a message from Gianluca

Tue, 13 Oct 2026 10:03:08 GMT

It's not a problem whether you use a RAR or a ZIP archive because the plugin itself is responsible for unpacking it. So it's your choice.
Anyway, I rarely use RAR because it is a proprietary format. They keep the archiver proprietary while providing the extractor for free, which I find a bit awkward.
I've never had any issues with ZIP files, either when using GUI tools or when creating and extracting them programmatically. The issue you got was probably related to the specific ZIP implementation rather than the ZIP format itself.
For more than ten years, whenever I needed compression or extraction features in SyMenu, I've relied on 7-Zip through command-line calls rather than implementing the compression algorithms directly in code. Because of that, I'm a lot out of touch with the implementation details and common issues of ZIP libraries, so I'm afraid I can't give you any particularly useful advice on the coding side.

Topic "SyMenu 8.16" a message from sl23

Mon, 12 Oct 2026 14:55:32 GMT

Thanks Gian, i will look at this soon, still a bit tied up with my PolyHost app/plugin.

One question... Would it be ok to sue RAR instead of a ZIP file? I prefer RAR and is easier for me to deal with. Besides, I have had several corrupted ZIPs lately where I update the ZIP file content, no idea why, but RAR seems much more robust, never had any issues with them in over 15 years and I use them constantly on a daily basis. My plan was to create the archive and upload to github so the plugin can check the latest release and update accordingly.

EDIT:
Github repo created: https://github.com/sl2365/AudioPluginsSuite
Suite name: AudioPlugins
Filename: AudioPlugins.rar

edited by sl23 on 12/10/2026

Topic "SyMenu 8.16" a message from Gianluca

Mon, 12 Oct 2026 12:58:22 GMT

Ok, to be clearer with everyone reading this thread, what I sent you is a code template in C# to start creating your own plugin.

Topic "SyMenu 8.16" a message from sl23

Mon, 12 Oct 2026 12:35:38 GMT

Thanks for explaining, I see I completely misunderstood now! lol

One thing, how do I even start with a plugin? I mean, I surely need a basis for how the plugin should interact with SyMenu, is there a template or something, so I can work from that to get my plugin to work correctly? Or is that something still in the works? (EDIT: No worries, I saw you sent me a link in my email! Thanks very much.)

Thanks for the great update, this expands SyMenu considerably!

edited by sl23 on 12/10/2026

Topic "SyMenu 8.16" a message from Gianluca

Fri, 09 Oct 2026 11:21:53 GMT

sl23 wrote:

I'm totally confused!

Let me clarify, because I think I jumped ahead.

sl23 wrote:

You keep mentioning "the plugin", what plugin is this? Do I need to create one specifically to manage this suite, or is that the part you have done in this update?

About the plugin: yes, you would write it yourself.
What I changed in this update is that SyMenu now tells every subscribed plugin when it starts.
SyMenu doesn't manage custom suites by itself as it does with the main suite, so your plugin uses that "SyMenu is starting" moment to do the work.
For example, it can check online whether a newer version of your suite definitions is available, or prepare the local folders on first run.

sl23 wrote:

Could I create a SyMenu plugin that does this check automatically?

Yes, you can and you should. Without it, your suite is just a definitions file online that users must download and update manually.

sl23 wrote:

whats the Master SPS you mention and where does this go? Where do I place this? does it become a part of the suite itself? Then I update that whenever theres an updated sps within the suite?

About "Master SPS": sorry, I was describing my own setup. "Master" is just the name I would use for a local copy of the SPS files. It is not part of the suite that users receive.
Here is the workflow I would follow:
- Keep the SPS files of your custom suite in a local folder (your "master" files).
- Edit them with SPS Builder, which also helps check file integrity and VirusTotal results. In theory you can do it manually, but then you must check file integrity, VirusTotal report, package size, exe availability, and so on, by yourself.
- Don’t use SPS Builder to upload these files to the official SyMenu suite, or they would become part of it.
- When ready, zip the files and upload the zip to an online location, for example GitHub.
- When a file needs an update, edit it in your master folder, create a new zip with all the files and upload it again.
- Your plugin checks that location at SyMenu startup (for example by comparing a version number in the zip name or in a small config/ini file).
- If there is a newer version, the plugin notifies the user, who can then update the suite automatically, exactly as they do with the main suite.

Topic "SyMenu 8.16" a message from sl23

Thu, 08 Oct 2026 15:45:47 GMT

ok, I need further information! lol

I'm totally confused! You keep mentioning "the plugin", what plugin is this? Do I need to create one specifically to manage this suite, or is that the part you have done in this update?

So I have to do the following:

1. Create a zip of all sps files contained in the suite.
2. Upload to say, github.
3. But whats the Master SPS you mention and where does this go? Where do I place this? does it become a part of the suite itself? Then I update that whenever theres an updated sps within the suite?

Could I create a SyMenu plugin that does this check automatically? ie, it performs the check online to see if the updated suite matches the latest installed version via a blank versioned file.ini then downloads and installs into the suite if newer.

Topic "SyMenu 8.16" a message from Gianluca

Thu, 08 Oct 2026 13:54:00 GMT

I confirm that SyMenu uses the notification icon status for custom suites too.
But how does this work? What does a custom suite editor need to do in order to notify SyMenu about updates?
Actually, nothing special is required. The mechanism is exactly the same as the one used by the main suite.

Let me explain.
When SyMenu starts, it checks its endpoint for updated SPS definitions. If newer definitions are available, it downloads them into its _cache folder.
In your scenario, these two tasks are delegated to the plugin.
I agree that distributing the custom suite SPS files as a ZIP archive is the simplest solution. SPS files are very small and compress extremely well, so a ZIP archive grants a small download size and a single file to manage. The only difference between the main suite and a custom suite is that for the main suite SyMenu can read SPS files directly from the ZIP archive, while for the custom suite it needs the files to be extracted first. However, unzipping a file is trivial and the plugin can do that in secs.

Once the plugin has downloaded and extracted the updated SPS files inside the custom suite _cache folder, the situation becomes identical to the main suite. At that point, SyMenu can detect available updates in exactly the same way it does for the official suite.

How?
Through the software version stored in each SPS file.
Let's see the entire workflow.
When a new version of AudioPluginABC is released, you would:
- update the master SPS for AudioPluginABC, changing the version number and, if necessary, the download URL and any other metadata (file size, VirusTotal information, etc.);
- package the updated SPS files into sl23CustomSuiteCollection.v345.zip;
- upload the updated ZIP file to your endpoint;
- let the plugin and SyMenu do the rest.

The plugin is responsible for checking whether a newer SPS collection is available, downloading it, and extracting it.
SyMenu is responsible for determining whether any installed applications in the custom suite require updates by reading the downloaded SPS files.

I also suggest versioning the ZIP filename (for example, v345).
This gives the plugin a simple reference point to determine whether the online definition package is newer than the locally downloaded package.

If you adopt this approach, remember to preserve a version marker that the plugin can compare against. This can be the previous ZIP file itself, an empty file named after the version (for example, v345), or a simple text file containing the current version number.

Another important point is the role of SPS Builder.
You can use it for sure. What you can't do is upload custom suite SPS files to the UGMFree cloud. For a custom suite you can work with local files (SPS Builder does this easier), and upload the definitions manually to your endpoint.

If you need any other information, please ask.

Topic "SyMenu 8.16" a message from sl23

Thu, 08 Oct 2026 13:14:06 GMT

I sent an email about this, but perhaps it may be better to post here, then users can see how this affects their own suites.

So the idea of this is that for personal/custom suites to notify SyMenu via the blue Get New Apps icon, by turning it green, is that right? Does it extend that far?
But I see you have actually added per item in-menu update notification.

Is there anything an author of a custom suite needs to do? Or is this purely on SyMenu side?
As already discussed via email, I plan on releasing a custom suite for AudioPlugins, will these need to be zipped, as the current two built-in suites are, or do I need to make these individual files?

I am just trying to figure out some things wrt how this will work. For example, for a zipped file that can be easily downloaded by users in one go, it becomes necessary for me to manually add new files however I receive these from others, into the suite. For individual sps files, I don't need to do this, but then how do others download all of the separate files as a suite? Its a bit of a problem either way. I am trying to think of how this could literally be done automatically, I realise checks need to be performed on sps files to avoid spam and malicious sps files, but how do you do this? What is your process?

Essentially, we need to understand the process for creating, sharing, updating custom suites.

Thanks for the update, it is indeed a great thing you've done!

edited by sl23 on 08/10/2026

Topic "SyMenu 8.16" a message from Gianluca

Wed, 07 Oct 2026 15:09:56 GMT

Dear all,
A new version has just been released.
The most important changes are:

A new interface for the plugin system (whatever that means!).
SyMenu now highlights in the context menu the updates availability in any SPS suite, including custom suites, through a dedicated icon and special text in the context menu.

Let's take a closer look at these two features.

Plugin startup notifications
The new plugin interface allows a plugin to be notified whenever SyMenu starts.
A more consistent implementation might have been to leverage SyMenu's native Autoexec on Start feature. However, that would have required users to enable Autoexec just to execute a plugin during startup. It seemed preferable to let the plugin itself declare its intention to run at that stage.
For those interested in the technical details, the new interface is called ISyPluginNotificationStartup and, as usual, it is exposed through SyMenu.Plugin.Resources.dll.
If you need further information, you know who to contact.

Update notifications for secondary and custom suites
This is a long-awaited feature.
SyMenu can now show update notifications not only for the main suite, but also for the secondary suite (NirSoft) and even for custom suites created by users.
When updates are available, the corresponding context menu entry is highlighted with a dedicated icon and text, making it much easier to spot pending updates.

As always, if you have questions or need additional details, feel free to ask.

Topic "Symenu 8.XX refuses to update" a message from Gianluca

Thu, 01 Oct 2026 08:43:16 GMT

Okay, after checking the dll timestamps, I'm pretty sure I've figured out what happened.

It looks like SyMenu.Libraries.dll was copied or moved to the SyMenu root folder some time ago.
Since SyMenu probes the root folder before looking in the Lib folder, it found the dll there and loaded it successfully.
This worked fine until the latest update.
The new version requires a newer SyMenu.Libraries.dll, but the probing process still found the old dll in the root folder and attempted to load it from there. Once loaded, SyMenu checked the assembly metadata, detected that it was not the required version, and crashed.
Deleting the DLL from the root folder solved the issue because the probing process was then able to resolve the correct dependency from the Lib folder.

Lesson learned. Next time, I should remember to ask the reporter for a complete file listing of the SyMenu core folders right away.

Thanks, this has been really useful.

Topic "Symenu 8.XX refuses to update" a message from Gianluca

Thu, 01 Oct 2026 08:31:44 GMT

Frustrated wrote:

Fixed the problem. Renamed the SyMenu.Libraries.dll in the Symenu folder and Symenu found the dll in its Lib folder.

Really?
Any idea how SyMenu.Libraries.dll ended up in the root SyMenu folder?
The updater preserves the original package structure, and in both the zip and exe distributions that dll is located in the Lib folder.
Could it have been copied there manually at some point?

Topic "Symenu 8.XX refuses to update" a message from Frustrated

Thu, 01 Oct 2026 05:22:00 GMT

I downloiaded the Zip and checked the blocking option and there was none. I unzipped the files and replaced the existing files in the folder. Same result. When I ran SyMenu.exe nothing happens. No Symenu splash screen nor Symenu in the systray in W11

Faulting application name: SyMenu.exe, version: 8.15.9738.16613, time stamp: 0x6a620000
Faulting module name: KERNELBASE.dll, version: 10.0.26100.9444, time stamp: 0xf5847879
Exception code: 0xe0434352
Fault offset: 0x0016aed4
Faulting process id: 0x89A4
Faulting application start time: 0x1DD515443FBE555
Faulting application path: D:\_Drive_E\Downloads\Nasty Fixes\SyMenu\SyMenu.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: c5d5abe6-091e-4c8e-8913-117b0aae2a6a
Faulting package full name:
Faulting package-relative application ID:

---------------------------------

Application: SyMenu.exe
CoreCLR Version: 10.0.1126.37416
.NET Version: 10.0.11
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException: Could not load file or assembly 'SyMenu.Libraries, Version=8.15.9738.16612, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
File name: 'SyMenu.Libraries, Version=8.15.9738.16612, Culture=neutral, PublicKeyToken=null'
at SyMenu.Program.Main(String[] args)

Fixed the problem. Renamed the SyMenu.Libraries.dll in the Symenu folder and Symenu found the dll in its Lib folder.

edited by Frustrated on 01/10/2026

edited by Frustrated on 01/10/2026

Topic "Symenu 8.XX refuses to update" a message from Gianluca

Wed, 30 Sep 2026 08:24:43 GMT

Interesting.
If you don't mind, I'll use this thread as a sort of collector for SyMenu update issues, so I've slightly changed the thread title.
I'm particularly interested in this case because you're the first person to report a problem with the updater. Hopefully you'll also be the last... but experience suggests you might just be the first of a larger group.

At the moment I have no clear idea what is happening on your system. To investigate properly, I'd probably have to ask you to dig through Windows Event Logs and collect diagnostics for me... but I'm not that evil. What I can suggest instead is a workaround to solve that quickly and easily. It's useful both for failed updates and for installations that may have become corrupted over time:

Download the latest SyMenu package from the website. The EXE package is the easiest option, but the ZIP package works as well.
Unblock the downloaded package using the same procedure described for SyMenu plugins here: https://www.ugmfree.it/manual#SyMenuPluginBlocked
Run the EXE or extract the ZIP into the exact same folder where SyMenu is currently installed.
For example, if SyMenu is located in D:\CoolApp\SyMenu, make sure the installer or ZIP extraction target is D:\CoolApp\SyMenu.
If Windows asks whether existing files should be overwritten, answer Yes to All.

This procedure effectively performs a "reinstallation" of SyMenu while leaving your configuration, profiles, program entries, and personal settings untouched.

As I mentioned, I'm trying to collect both failed update cases and their successful resolutions. So, whatever the outcome, please let me know how it goes. Every piece of feedback helps me understand whether this is an isolated incident or the beginning of a new adventure with the updater.

Thanks for your help and patience!

Topic "Symenu 8.XX refuses to update" a message from Frustrated

Wed, 30 Sep 2026 04:03:09 GMT

Tried twice to update from 8.13.9578 and the result is always the same. The app notifies me on launch that there is an update. I tell it to update. The update window briefly shows up then disappears. From then on Symenu refuses to run. I can not even see it in the Windows task manager. I have to restore the entire directory from a backup.

Win11 Pro 25H2

edited by Gianluca on 30/09/2026

Topic "SyMenu 8.15" a message from Gianluca

Sun, 30 Aug 2026 10:10:51 GMT

The new version is finally out!
The biggest update in this release is a complete rewrite of the tooltip system. Most importantly, you can now customize the tooltip delay directly from the GUI.
Check out the full changelog here: https://www.ugmfree.it/symenudownload#changelog

If you have any feedback, bug reports, or ideas, feel free to get in touch.

Topic "A crazy new adventure!" a message from sl23

Sun, 23 Aug 2026 22:29:28 GMT

oh well, I can't use it anyway! No GPU!

Topic "Unhandled Exception - X=0 Y=0" a message from Gianluca

Sun, 16 Aug 2026 08:47:45 GMT

Hi PhredE,

From what I’m seeing, the issue is related to how the menu is drawn.
You mentioned that with the default white theme there’s no border, but the Border thickness selector cannot be set to 0 because the minimum value is 1.
What I suspect is a combination of particular SyMenu’s drawing custom settings and some Windows graphical configuration (typically display scaling), because I’m unable to reproduce the issue on my systems in anyway.

So I need your help to investigate further.

First I need to know how your Windows scaling is set? (100%? 75%? 125%? Other?)

Then please send me a private message through the website or the contact form. This way I can get your configuration file ([SyMenu]\Config\SyMenuConfig.zip), run it on my machine, and check whether the problem is simply a misconfiguration.
Otherwise, if you don’t have a particularly complex setup, you can also try this yourself:
- quit SyMenu
- delete [SyMenu]\Config\SyMenuConfig.zip
- run SyMenu again and reconfigure it
Your configured programs will remain untouched, but your SyMenu configuration will be reset. Hopefully, this will allow you to change the theme and save the new settings correctly.

Let me know which option you prefer to follow.

Topic "Unhandled Exception - X=0 Y=0" a message from PhredE

Sun, 16 Aug 2026 04:43:44 GMT

I'm not getting SyMenu to update its Options window. Cancel Continue Quit is all I can get out of it.
I'm trying to alter the extremely puzzling default theme (white windows on white windows with no borders. wha?) but even though I now have achieved perceptible green borders, there's little else I'm able to do. I can't escape/update Options.
Latest; no updates available.
Any reason sighted?
Thx.
Crash report attached.

Topic "VS Code Update Process Fails to Migrate Data Dir" a message from Qw

Fri, 07 Aug 2026 18:05:59 GMT

Thank you, its been restored to the normal directory structure

Topic "VS Code Update Process Fails to Migrate Data Dir" a message from Gianluca

Fri, 07 Aug 2026 16:26:21 GMT

WTF!

It was a regression bug when publishing the SPS definitions! I accidentally published an old version of VSCode instead of the newest one.
Sorry for the inconvenience!

I have just updated the program definition, so please proceed this way:
- Open SyMenu
- Go to SPS Manager
- Refresh the program definitions using the force button (if you can't find it, check the manual here: https://www.ugmfree.it/manual#SPSForm and look for "you can force it pressing the special button")
- Search for Visual Studio Code Portable (x64)
- Right-click on the grid item and choose Force update from web site

Everything will be fixed... provided you haven't moved the Data folder from its original location (it must be located in .\data).

Please let me know the outcome!

Topic "VS Code Update Process Fails to Migrate Data Dir" a message from Qw

Fri, 07 Aug 2026 15:08:09 GMT

The Visual Studio Code portable installation broke during the last two updates. The updater installs new versions into different directory trees. Consequently, the Data folder from the previous installation is no longer visible to the new version.
Analysis of the local directory structure indicates that the Data folder contains the application extensions, such as anthropic.claude-code, github.vscode-pull-request-github, and ms-python.black-formatter. When the new version is extracted to an isolated directory path without migrating this Data folder, the application loses access to all previously installed extensions and user configurations.
Attach is the tree of the new VScode after updating from SyManu and old tree before updating.

I request a fix to the SyMenu update configuration for Visual Studio Code. The update process must ensure the Data directory is preserved and correctly linked to the active installation path.

Topic "SyMenu 8.14" a message from Gianluca

Wed, 08 Jul 2026 11:47:48 GMT

The SyMenu summer version is finally out!
Great news (at least from a technical point of view): SyMenu has been migrated to .NET 10 to improve performance, security, and stability.
Unfortunately, major upgrades like this can sometimes introduce unexpected bugs or graphical glitches. Please report any unusual behavior you might notice.
For all the other updates, please check the changelog on the download page.

Bye!

Topic "Problem updating Speccy" a message from Gianluca

Fri, 26 Jun 2026 08:57:20 GMT

What a pity!
They've changed a lot the package and it would have been interesting to test a real update with the new SPS (I personally don't use speccy so it was difficult to test it by myself).
Anyway problem solved!

Topic "Problem updating Speccy" a message from ronen1n

Thu, 25 Jun 2026 21:32:52 GMT

I already installed it in vm and transferred the files, but thinking about it now maybe the reinstall with symenu makes more sense like you suggested

Topic "Problem updating Speccy" a message from Gianluca

Thu, 25 Jun 2026 12:10:05 GMT

I've just tested and it works well for me.
Can you report the entire error message please?
You can even delete the old one and reinstall the new one because it could be a problem only with the update process.

Topic "Main Symenu Program Update Failure" a message from Syngensmyth

Wed, 10 Jun 2026 03:11:16 GMT

If I go on one of the machines that I haven't accessed for a few months, the Symenu update fails. Not the individual downloads but the main program update.
This is what I get. Any solutions to keep from downloading everything again with a new Symenu?

YourSyMenu version is: 8.11.9501
New version is: 8.13.9578
SyMenu can automatically install the new version into the current folder.
Do you want to start the update process now?

Error in update process. Please manually download and
install SyMenu.

Topic "Symenu Crashing Periodically [Win11 24H2 26100]" a message from Gianluca

Sat, 30 May 2026 14:55:11 GMT

Nice!
These apparently random bugs are my favourites, because it’s impossible to fix them the “right” way.
So we’ll go with the wrong one: trial and error.
Please be patient we have a loooong road ahead of us.
I’ll get in touch with you privately as soon as possible with further instructions for you.

Topic "Symenu Crashing Periodically [Win11 24H2 26100]" a message from AllonZ

Fri, 29 May 2026 22:08:11 GMT

So, I have been having this small issue for a while but I finally have the time to make a post about it.

I am not sure when it started, but SyMenu seems to crash randomly throughout the workday without an error message. I just restart it and it usually runs fine for another few hours or so before it crashes again.

No big deal but thought it's worth a post.

Event Viewer shows 2 consecutive ID 1000 faults when SyMenu.exe crashes. I see other times when only 1 fault is logged and SyMenu.exe does not crash.

I am running it on Windows 11 Pro 24H2 26100.8457 as a standard user (have not yet tested as admin).
SyMenu ApplicationLog contains no data (another issue?) and I could not attach SyMenu.exe.20104.dmp because it was too big, so the WinDbg analysis is pasted below.
All dependencies seem fine so I did not paste the Process Explorer Data below.
No rush. Let me know if I can provide you with any other data.

Event Viewer log:

Error 5/29/2026 2:42:19 PM Application Error 1000 Application Crashing Events
Log Name: Application
Source: Application Error
Date: 5/29/2026 2:42:19 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: -----\-----
Computer: -----
Description:
Faulting application name: SyMenu.exe, version: 8.13.9578.12752, time stamp: 0x698d0000
Faulting module name: ntdll.dll, version: 10.0.26100.8328, time stamp: 0xf814f1d6
Exception code: 0xc0000710
Fault offset: 0x000bf82a
Faulting process id: 0x4E88
Faulting application start time: 0x1DCEF796CAE7152
Faulting application path: D:\SyMenu\SyMenu.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: d1eb6f26-64fa-48fb-b18a-a717f081bd27
Faulting package full name:
Faulting package-relative application ID:
Event Xml:

1000
0
2
100
0
0x8000000000000000

35253

Application
-----

SyMenu.exe
8.13.9578.12752
698d0000
ntdll.dll
10.0.26100.8328
f814f1d6
c0000710
000bf82a
0x4e88
0x1dcef796cae7152
D:\SyMenu\SyMenu.exe
C:\WINDOWS\SYSTEM32\ntdll.dll
d1eb6f26-64fa-48fb-b18a-a717f081bd27

WinDbg analysis:
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

Integrated managed debugging does not support enumeration of symbols.
Type information missing error for Instance
Type information missing error for Instance
Type information missing error for Instance
Type information missing error for Instance
Type information missing error for Instance
Type information missing error for Instance
ClrmaManagedAnalysis::GetThread 27e8
ClrmaThread::Initialize 27e8
~ClrmaThread
ClrmaManagedAnalysis::get_ProviderName
ClrmaManagedAnalysis::GetThread ffffffff
ClrmaThread::Initialize 27e8
ClrmaThread::get_CurrentException
ClrmaThread::get_NestedExceptionCount
~ClrmaThread

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3671

Key : Analysis.Elapsed.mSec
Value: 3840

Key : Analysis.IO.Other.Mb
Value: 2

Key : Analysis.IO.Read.Mb
Value: 2

Key : Analysis.IO.Write.Mb
Value: 12

Key : Analysis.Init.CPU.mSec
Value: 718

Key : Analysis.Init.Elapsed.mSec
Value: 286012

Key : Analysis.Memory.CommitPeak.Mb
Value: 195

Key : Analysis.Version.DbgEng
Value: 10.0.29547.1002

Key : Analysis.Version.Description
Value: 10.2602.27.2 x86fre

Key : Analysis.Version.Ext
Value: 1.2602.27.2

Key : CLR.Engine
Value: CORECLR

Key : CLR.Version
Value: 8.0.2526.11203

Key : Failure.Bucket
Value: APPLICATION_FAULT_c0000710_ntdll.dll!TppCallbackCheckThreadAfterCallback

Key : Failure.Exception.Code
Value: 0xc0000710

Key : Failure.Exception.IP.Address
Value: 0x77c3f82a

Key : Failure.Exception.IP.Module
Value: ntdll

Key : Failure.Exception.IP.Offset
Value: 0xbf82a

Key : Failure.Hash
Value: {835ced0b-650a-ac17-6e19-92a4bb23b3ad}

Key : Failure.ProblemClass.Primary
Value: APPLICATION_FAULT

Key : Faulting.IP.Type
Value: Paged

Key : Timeline.OS.Boot.DeltaSec
Value: 23330

Key : Timeline.Process.Start.DeltaSec
Value: 14370

Key : WER.OS.Branch
Value: ge_release

Key : WER.OS.Version
Value: 10.0.26100.1

Key : WER.Process.Version
Value: 8.13.9578.12752

FILE_IN_CAB: SyMenu.exe.20104.dmp

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: (.ecxr)
eax=1405f538 ebx=1405f6f0 ecx=00000000 edx=00000000 esi=00000000 edi=00000050
eip=77c3f82a esp=1405f528 ebp=1405f590 iopl=0 nv up ei pl nz ac pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000216
ntdll!TppCallbackCheckThreadAfterCallback+0x685f3:
77c3f82a 6a04 push 4
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 77c3f82a (ntdll!TppCallbackCheckThreadAfterCallback+0x000685f3)
ExceptionCode: c0000710
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 7727d6b0
Parameter[1]: 0b48e78c

PROCESS_NAME: SyMenu.dll

ERROR_CODE: (NTSTATUS) 0xc0000710 - A threadpool worker thread is impersonating a client, after a callback to 0x%p(0x%p). This is unexpected, indicating that the callback is missing a call to revert the impersonation.

EXCEPTION_CODE_STR: c0000710

EXCEPTION_PARAMETER1: 7727d6b0

EXCEPTION_PARAMETER2: 0b48e78c

STACK_TEXT:
1405f590 77bd7051 03181870 77bad9f0 03181870 ntdll!TppCallbackCheckThreadAfterCallback+0x685f3
1405f61c 77bd6aa5 c4de4b3b 77bd62c0 77bd62c0 ntdll!TppCallbackEpilog+0x24
1405f7cc 75be5d49 03181870 75be5d30 1405f834 ntdll!TppWorkerThread+0x7e5
1405f7dc 77bed83b 03181870 c4de44c3 00000000 kernel32!BaseThreadInitThunk+0x19
1405f834 77bed7c1 ffffffff 77c3498b 00000000 ntdll!__RtlUserThreadStart+0x2b
1405f844 00000000 00000000 00000000 00000000 ntdll!_RtlUserThreadStart+0x1b

IP_IN_PAGED_CODE:
ntdll!TppCallbackCheckThreadAfterCallback+685f3
77c3f82a 6a04 push 4

SYMBOL_NAME: ntdll!TppCallbackCheckThreadAfterCallback+685f3

MODULE_NAME: ntdll

IMAGE_NAME: ntdll.dll

STACK_COMMAND: ~20s; .ecxr ; kb

FAILURE_BUCKET_ID: APPLICATION_FAULT_c0000710_ntdll.dll!TppCallbackCheckThreadAfterCallback

OS_VERSION: 10.0.26100.1

BUILDLAB_STR: ge_release

OSPLATFORM_TYPE: x86

OSNAME: Windows 10

IMAGE_VERSION: 10.0.26100.8328

FAILURE_ID_HASH: {835ced0b-650a-ac17-6e19-92a4bb23b3ad}

Followup: MachineOwner
---------

CLRMAReleaseInstance
~ClrmaManagedAnalysis

edited by AllonZ on 29/05/2026