NetSetMan Support

NetworkVic

Member

Registered: 2015-06-18

Posts: 1

Does not minimize on Win10

I assume you are starting to de-bug for Win 10. I have found a cosmetic issue (Win build 10130) using ver. 4.0.3.
Even tho the menu is checked to minimize on start up, the interface pops up after startup. Both 'Start with Windows/minimized' and 'Always start minimized' are checked (although I think those are redundant).

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: Does not minimize on Win10

Sorry for the late reply. Initially I was waiting for an internal result of a Win10 machine migration to a new test system, to be able to test the problem before responding. However, since that is still delaying I'd like to reply without having tested the issue.

First of all, "Start with Windows / minimized" and "Always start minimized" are not redundand as they a allow the combination to have it started minimized with Windows, but when started manually to have it started visible.

Second, in my understanding there shouldn't be any difference in the autorun process between Win10 and previous versions. One probable cause might be that the application is launched twice. The second time the already running application would be called into the foreground. So please check for that possibility on your system. Did you create some autorun configuration for NetSetMan yourself (autorun folder, Tast Scheduler, etc.)?

Please check

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run

and

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

Where is NetSetMan included with what details?

kaltec

Member

Registered: 2016-03-07

Posts: 3

Re: Does not minimize on Win10

I'm having this issue as well on Windows 10 (Build 6.3.10240) with NetSetMan Pro version 4.1.2 (Release Date 2016-02-11).

I checked the registry entries you referenced above, and the program is only present in the HKEY_LOCAL_MACHINE hive. The entry lists the program location with the '-h' command line parameter.

I terminated the program and manually started the app with the -h and -hide options, but neither of them caused the program to start minimized.

I don't currently have a windows 7 box to test with, so I can't see if it's limited to the Windows 10 platform.

Thanks!

~kal

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: Does not minimize on Win10

We've tested this on multiple Windows 10 systems just now. NetSetMan started correctly minimized on all of them when run with the -h parameter.

Important: Make absolutely sure that during your tests NetSetMan isn't already running (in the background or minimized in the tray). If there's an already running instance, the new process isn't started additionally but instead calls this instance to appear in the foreground. In this case the parameter is completely ignored.

If the problem persists, then please send us your settings.ini file from the program folder zipped as an email file attachment (see Contact page) so we can perform the test again with exactly your configuration. What kind of user account are you using? Administrator or limited user account? With or without UAC? Is the NSM Service activated in the program preferences?

kaltec

Member

Registered: 2016-03-07

Posts: 3

Re: Does not minimize on Win10

The user I'm logged in as is part of the local admin group. UAC is set to the default setting. The NSM service is running as 'Local System' (by default).

Originally, the NMS service was active as well as the options 'start with windows' and 'start minimized in tray'. If I disabled the 'start with windows' option and restarted, I could start the program with -h and it would hide normally. If I enabled 'start with windows', the main UI would not be hidden after reboot.

On a whim, I went ahead and disabled the NMS service and rebooted. I still had the 'start with windows' and 'start minimized in tray' checked. After reboot, I received the UAC prompt (for NSM), but the program started minimized after I clicked 'Accept'. Yay!

I went ahead and re-enabled the NMS service, then restarted again. This time, no UAC prompt (as expected), but the NMS UI was front and center.

I do not have any settings/shortcuts causing it to load automatically (other than the checkbox from within the program itself).

Would you still like me to send in my settings, or is the above information enough to have you test?

Thanks!

~kal

Last edited by kaltec (2016-03-08 04:31)

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: Does not minimize on Win10

Thank you for the additional information. According to it the minimized launch itself does work, but something's going wrong during the start using the service. Your user account setup seems to be pretty basic, so the problem must be somewhere else. Please send us the settings file so we can see if there's some special constellation that causes that. We'll do further investigation based on that.

kaltec

Member

Registered: 2016-03-07

Posts: 3

Re: Does not minimize on Win10

settings file removed

Last edited by NetSetMan Support (2016-04-29 02:21)

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: Does not minimize on Win10

We analyzed the problem but unfortunately were unable to reproduce it. We can offer to provide a special debug version that logs its activities into a local text file. Once you've reproduced the problem with it, you can send us the log file so we're able to analyze the problem in detail. This should help to better understand what exactly might fail in your case (maybe it's a timing problem, maybe some parameter isn't sent correctly).

ChrisElsen

Member

Registered: 2016-04-21

Posts: 8

Re: Does not minimize on Win10

I'm running into a similar issue under Windows 10. But in my case, even with the parameter "-h" the program doesn't start minimized.

More than happy to try the special debug version.

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: Does not minimize on Win10

Alright, we'll prepare the debug version for next week.
Before doing so: Could you please make sure that during your current tests there's no running/minimized instance of NetSetMan? If you use the command line to run the application (even with -h) while NetSetMan is already sitting in the tray then this only results in bringing the already running instance to the foreground (instead of running a second instance minimized).

ChrisElsen

Member

Registered: 2016-04-21

Posts: 8

Re: Does not minimize on Win10

Yes, confirmed that NetSetMan is definitely not running (checked the tray and TaskMgr).
Thanks for providing the debug version.

ChrisElsen

Member

Registered: 2016-04-21

Posts: 8

Re: Does not minimize on Win10

I did some more testing: If I launch NetSetMan with "Run as administrator" it starts correctly into the Taskbar. Obviously I have to confirm the Windows UAC window first, or disable UAC.

To me that looks like NetSetMan is having issues with permissions.
The NSM service is running.

Also AutoSwitch is not working.

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: Does not minimize on Win10

We'll provide the debug version later this week, as promised. Then we'll know more.

Also AutoSwitch is not working.

This statement is quite generalized. AutoSwitch is a complex feature with many different condition options and combination possibilities. If there's a bug, we'll be happy to fix it. But first, please make sure there's no misunderstanding in the functionality by reading the corresponding topic in the help file:
www.netsetman.com/help?hf=en#hf_autoswitch
And additionally some background information on that topic in the FAQ:
www.netsetman.com/faqautoswitch
If after that you still think something's not working as it should be please post a new topic with a detailed problem description.

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: Does not minimize on Win10

With the help of ChrisElsen we've identified the reason for the problem that caused the discussed "Run minimized" problem in some cases. The fix will be available with the next official release.