24/04/2017
Topic:
RESOLVED: Webroot + SyMenu = W32.Trojan.Gen
AllonZ
|
I have been running Webroot SecureAnywhere and SyMenu side-by-side for a while with no issues. But today Webroot popped up saying SyMenu was detected as having a w32.Trojan.Gen infection. When I ran a manual scan with Webroot, several other apps I installed with SyMenu also cam up with the W32.Trojan.Gen infection.

Anyone else having this issue? Is this a false positive or has my SyMenu been compromised?
Even if I tell Webroot to ignore this for now, it is still detected as an infection and SyMenu will not run.
Do I uninstall SyMenu and the other infected apps? Or have Webroot Quarantine them for now?
Or should I report this as a false positive to Webroot and not remove the detected threats?
Any help would be greatly appreciated. edited by AllonZ on 28/04/2017 edited by AllonZ on 28/04/2017 |
25/04/2017
Topic:
RESOLVED: Webroot + SyMenu = W32.Trojan.Gen
AllonZ
|
Thanks for rhe quick reply Gianluca.
That's what I was afraid of since the total number of infections was going up evey time I scanned.
I will rinse and repeat. |
25/04/2017
Topic:
RESOLVED: Webroot + SyMenu = W32.Trojan.Gen
AllonZ
|
OK... So i woke up this morning and powered on my system, after having turned it off last night to stop any further infection and before I had a chance to remove the infected files. I ran the scan again and now no infections are detected. SyMenu opens without triggering any warnings.
What is going on now?
Would you recommend that I save the config files, delete the the files that were said to be infected and then reinstall them? edited by AllonZ on 28/04/2017 |
28/04/2017
Topic:
RESOLVED: Webroot + SyMenu = W32.Trojan.Gen
AllonZ
|
UPDATE:
"On April 24, Webroot experienced a technical issue affecting some business and consumer customers. Webroot incorrectly identified multiple files as malware. Actual malicious files are being identified and blocked as normal."
Find the official release as well as other pertinent information here.
|
04/06/2024
Topic:
Clicking 'Updates available' Crashes SyMenu
AllonZ
|
When I receive the green 'Updates available' notification in SyMenu and click on it, the popup menu freezes for 5-10 minutes then SyMenu crashes. I immediately restart SyMenu, click 'Updates available' and I can update the apps as normal. The next time I have more 'Updates available' this behavior repeats itself.
I believe this has been happening off and on since the last update. Let me know if you would like any more information. |
05/06/2024
Topic:
Clicking 'Updates available' Crashes SyMenu
AllonZ
|
I am running SyMenu 8.02.8896 and the issue still happens every now and then.
It is hard to say whether or not changing the password is an effective workaround because the issue does not happen every time I try to update apps.
I will try a different password for a while and report back with my findings. |
05/06/2024
Topic:
Clicking 'Updates available' Crashes SyMenu
AllonZ
|
I sent you an email about a different topic, but mentioned that I changed my password. I was able to login to the forum with the new password but have been unable to login to SyMenu.
I thought maybe the server needed some time to update the required database but it has been 4 or 5 hours and I still cannot login to SyMenu with the new password.
I did make the new password pretty long. Is there a limitation to the number of bits a password can have?
edited by AllonZ on 05/06/2024 |
08/06/2024
Topic:
Clicking 'Updates available' Crashes SyMenu
AllonZ
|
I apologize if I have misunderstood your advice.
There does seem to be a limit to the length and characters for passwords within SyMenu. I assume you do not know what the specific limitations are or you would have already mentioned them.
I will report back here if I run into any further issues.
Thank you for your time!
edited by AllonZ on 08/06/2024 |
14/06/2024
Topic:
Clicking 'Updates available' Crashes SyMenu
AllonZ
|
SyMenu crashed again today when trying to access the SPS Manager dialog, so there is something else going on. It's no big deal because It now opens just fine after restarting. It's a bit annoying but I can deal with it. If you would like me to do any further troubleshooting just let me know.  |
28/06/2024
Topic:
Clicking 'Updates available' Crashes SyMenu
AllonZ
|
It is hard to say whether or not this workaround had any effect because the issue does not happen every time the SPS Manager is opened.
I see SyMenu has been updated to 8.03.8944 but I have not seen a post in the New SyMenu releases section since 8.01. What updates have been made since 8.01? |
28/06/2024
Topic:
Clicking 'Updates available' Crashes SyMenu
AllonZ
|
Makes sense. Didn't even think to look on the download page. 🤦♂ My bad
Thanks! |
07/08/2025
Topic:
How to Downgrade an SPS
AllonZ
|
Since I can find no way to downgrade and SPS, I am wondering if it is possible to get a copy of an older version of an SPS, specifically for Thunderbird Portable. After installing the new version, 141, some add-ons are not available and they are very important to my workflow. I would greatly appreciate it if you could direct me on where to find the ThunderbirdPortable_sps file for install. If that is not possible, maybe you can attach the file in reply the this message. Thanks for you time! AllonZ |
07/08/2025
Topic:
How to Downgrade an SPS
AllonZ
|
Thanks for the quick reply and pointing me in the right direction, Gian!
I do not recall if you already do so (ignore if you do), but it would be great to include 'esr' at the end of ThunderbirdPortable version numbers, just as Mozilla does with their file naming convention. ESR is also included in the file naming convention of the .paf files. So it should be easy enough for you to identify and add to the version number when you are updating the SPS. This would allow users like myself to easily identify whether or not we want to upgrade or wait for the ESR.
Thanks you so much for the wonderful app and the great support! Keep up the good work!
Here is a write-up on the process I took to resolve the issue:
How to Rebuild ThunderbirdPortable_sps in Order to Downgrade
- NOTE: The following steps are for ThunderbirdPortable_sps but it is possible that similar steps can be used to downgrade other SPS installations.
- Many add-ons only work with ESR versions of Thunderbird, so if you inadvertently upgrade to a non-ESR version it is possible to downgrade to an ESR version of ThunderbirdPortable using the steps below.
⚠️ WARNING: This process will delete your profile data!!!
1. Backup your Thunderbird data using 1 of 2 methods ⠀⠀a. Make a copy of your profile folder and save it to your desktop temporarily ⠀⠀⠀OR ⠀⠀b. Archive it to a backup location of your choice, outside of the ThunderbirdPortable_sps folder: ⠀⠀⠀⠀\SyMenu\ProgramFiles\SPSSuite\SyMenuSuite\ThunderbirdPortable_sps\Data\profile
2. Official Thunderbird release page ⠀⠀a. Navigate to the official releases page to compare and confirm which releases are ESR: ⠀⠀⠀⠀https://www.thunderbird.net/en-US/thunderbird/releases/
3. Copy ESR release URL ⠀⠀a. Navigate to the source files URL: ⠀⠀⠀⠀https://sourceforge.net/projects/portableapps/files/Mozilla%20Thunderbird%2C%20P.E./ ⠀⠀b. Click the newest/desired ESR version that is confirmed from the URL in step 2 ⠀⠀c. Right click the URL of the desired language & copy link address ⠀⠀⠀⠀1. The URL should be the same or very similar to the following format: ⠀⠀⠀⠀⠀⠀https://sourceforge.net/projects/portableapps/files/Mozilla%20Thunderbird%2C%20P.E./Mozilla%20Thunderbird%20ESR%2C%20Portable%20Edition%20140.1.0/ThunderbirdPortableESR_140.1.0_English.paf.exe/download
4. Change the ThunderbirdPortable.sps Download URL ⠀⠀a. Extract ThunderbirdPortable.sps from the sps.zip file in the SyMenu Suite Cache folder: ⠀⠀⠀⠀\SyMenu\ProgramFiles\SPSSuite\SyMenuSuite\_Cache\ ⠀⠀b. Edit ThunderbirdPortable.sps using 1 of 2 methods
⠀⠀⠀⠀1. Text editor: Replace the URL after <DownloadUrl> with the copied URL from step 3c and Save ⠀⠀⠀⠀⠀⠀OR ⠀⠀⠀⠀2. SPS Builder [install via SPS Manager, .NET required] ⠀⠀⠀⠀⠀⠀a. Load ThunderbirdPortable.sps ⠀⠀⠀⠀⠀⠀b. Change 'Download Url' with copied URL from step 3c ⠀⠀⠀⠀⠀⠀⠀⠀1. Do not change any other info ⠀⠀⠀⠀⠀⠀c. Choose working folder same as step 5 ⠀⠀⠀⠀⠀⠀⠀⠀\SyMenu\ProgramFiles\SPSSuite\SyMenuSuite\_Cache\ ⠀⠀⠀⠀⠀⠀d. Save ⠀⠀c. Add edited ThunderbirdPortable.sps back to the sps.zip file ⠀⠀⠀⠀1. This will overwrite the original ThunderbirdPortable.sps
5. Update to edited ThunderbirdPortable.sps ⠀⠀a. Exit and restart SyMenu ⠀⠀b. Run SPS Manager: SyMenu > 'Get new apps' ⠀⠀⠀⠀1. Right click ThunderbirdPortable ⠀⠀⠀⠀⠀⠀a. Be sure that ThunderbirdPortable is not running in the background ⠀⠀⠀⠀2. Click 'Force update from the web site'
6. Import saved profile ⠀⠀a. Once the installation is complete, run ThunderbirdPortable and you will see a popup warning: ⠀⠀⠀⠀"You have launched an older version of Thunderbird" ⠀⠀b. Click 'Create new profile' ⠀⠀c. Once Thunderbird has fully loaded exit the app ⠀⠀d. Cut and paste, or extract the profile folder backup from step 1 to: ⠀⠀⠀⠀\SyMenu\ProgramFiles\SPSSuite\SyMenuSuite\ThunderbirdPortable_sps\Data ⠀⠀e. Replace existing files: Yes to all ⠀⠀f. Run Thunderbird to load imported profile
edited by AllonZ on 07/08/2025 |
04/03/2026
Topic:
A crazy new adventure!
AllonZ
|
Awesome! I've been looking for something like this for a while now. Can't wait to try it! |
20 days ago
Topic:
Symenu Crashing Periodically [Win11 24H2 26100]
AllonZ
|
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: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> <EventID>1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2026-05-29T18:42:19.1342632Z" /> <EventRecordID>35253</EventRecordID> <Correlation /> <Execution ProcessID="31480" ThreadID="24172" /> <Channel>Application</Channel> <Computer>-----</Computer> <Security UserID="S-1-5-21-3561418018-3650584135-2967397845-1013" /> </System> <EventData> <Data Name="AppName">SyMenu.exe</Data> <Data Name="AppVersion">8.13.9578.12752</Data> <Data Name="AppTimeStamp">698d0000</Data> <Data Name="ModuleName">ntdll.dll</Data> <Data Name="ModuleVersion">10.0.26100.8328</Data> <Data Name="ModuleTimeStamp">f814f1d6</Data> <Data Name="ExceptionCode">c0000710</Data> <Data Name="FaultingOffset">000bf82a</Data> <Data Name="ProcessId">0x4e88</Data> <Data Name="ProcessCreationTime">0x1dcef796cae7152</Data> <Data Name="AppPath">D:\SyMenu\SyMenu.exe</Data> <Data Name="ModulePath">C:\WINDOWS\SYSTEM32\ntdll.dll</Data> <Data Name="IntegratorReportId">d1eb6f26-64fa-48fb-b18a-a717f081bd27</Data> <Data Name="PackageFullName"> </Data> <Data Name="PackageRelativeAppId"> </Data> </EventData> </Event>
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 |