Shadohz Posts: 1 1 days ago	Shadohz Posts: 1 I have SyMenu running on a host machine with is networked to a couple of Win11 client machines. The client machines have offline syncing enabled (Win11 feature). The problem is that SyMenu is taking between 15-30 minutes to stop loading when Offline Syncing is disabled and 40minutes to +1hr when Offline Syncing is enabled. By "settle" I mean for SyMenu to stop scanning or whatever it is that it's doing that makes that its icon flicker. The times are from Reboot (i.e. startup) to when the Symenu program gives me access to installed SyMenu applications. The only thing I can say for sure is that Offline Files extends this abnormal behavior. I can't explain why there's a huge time difference in the startup-to-settle times. I read a couple of similar posts about applications being at the root of the SyMenu application folder but that isn't the case here. All the Symenu apps are under Z:\ProgramFiles\SPSSuite\SyMenuSuite. I installed custom apps to \..\SPSSuuite\Custom_Programs. Any explanation or resolution for this? Any way to stop this scan behavior on the client machines?
	link
Gianluca Administrator Posts: 1358 9 hours ago	Gianluca Administrator Posts: 1358 This is a really tough one… Above all because I haven’t clearly understood what your configuration is. For example, I still don’t know whether the SyMenu instance is running on the host machine or if it is launched on the Windows 11 client machines. If your setup is the last one, what happens if you launch SyMenu directly from the host? What exactly is the offline syncing doing? And why is this feature involved with the SyMenu files? At the moment, I don’t have a clear picture of what normally happens on your machines, so I can’t even imagine what the impact on SyMenu might be. Anyway, even if I had a clear idea, I still wouldn’t have a solution for you because the problem could be anywhere. So my suggestion for a possible resolution would be exactly the same as the one I’m giving you now. Download a clean version of SyMenu. If you download the ZIP version, remember to remove the lock that Windows adds to any package downloaded from the Internet. I explain how to do that here for a plugin package: https://www.ugmfree.it/manual#SyMenuPluginBlocked Unzip it into an empty folder on your host machine. Ideally, choose a folder without any security, authorization, or permission issues, so avoid locations like C:\Program Files or C:\Windows. The best option is always D:\SyMenu if you have a D: drive. Run the new SyMenu. Multiple versions of SyMenu can coexist on the same machine, even on the same disk. I assume everything will work fine: SyMenu should load in a few seconds and suggest installing some programs from the suite. Now, step by step, start adding the configurations needed to mimic your real installation. For example, add some programs, link network folders, or whatever your main installation normally does. After each change, run some tests: restart SyMenu and check for any strange behavior, try launching some programs, and so on. If the program starts to struggle, slow down, freeze, collapse, call home, or scream for help, you’ll know the reason, it will certainly be the last change you made. At that point, please come back here and we’ll try to solve the problem together.
	link

---