Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[kitz]

@ Ronski

Not sure what may have happened or when this changed, but I no longer appear able to disable the scheduled task from within the HG612viewer GUI. 

Tasks > Delete logging task

Doesn't appear to do anything and I had to directly disable it from within Task Scheduler.   Once I had disabled it in there, the HG612viewer GUI recognised that it was disabled.

[Ronski]

It does indeed seem to be broken on my windows 10 machine, but works on my server (WHS2011). I've also noticed that the Task Enabled/Task Disabled button doesn't seem to change as expected.

I'll take a look when I get chance, hopefully sometime over the next week. I wonder if MS have changed something.

Just rolled back to the previous version of the GUI and it's broken in that, so certainly looks like MS might have done something with the task scheduler/schtasks

[kitz]

No hurry ron.   Just thought I'd point it out.

I know that it used to work...  but then again that would have been on my Win7 machine.   It may be as you say it could be specific to Win10.

[Chrysalis]

yeah the last update was to fix something for me and I did specifically test toggling the task which worked fine.  Also still works now on my win 8.1 laptop.

[Ronski]

I still have a W7 machine so will test on that.

When trying on W10  last night I did get some access denied messages, so something has changed,  but a quick Google revealed nothing.

[Ronski]

Just tested on Windows 7 and all is well, MS must have been fiddling 

[Ronski]

It seems that MS has tightened up the security.

Running the following at a cmd prompt gave me an access denied message on windows 10 but works fine on windows 7

schtasks  /Delete /TN "HG612 Stats Program" /F

But if I run cmd as administrator then it works ok on W10, note above I'm using an admin account

This potentially means quite a lot of the task handling stuff is now broken  thanks MS! I also had to fight with Visual Studio 2015 to get debugging working.

[Ronski]

Actually as a work-a-round running the GUI with elevated privileges seems to fix the issues (Right click - rus as administrator)

You can also edit the programs properties and on the compatibility tab tick the checkbox to "Run this program as an administrator", and then clip apply. Each time you run the program you will get a UAC window pop up though (there are ways around this).