SwiftKit not working

[Dropbox]

http://prntscr.com/715od4

 

[Stidor]

Follow the instructions.

[Dropbox]

Can't find that file.

[Dropbox]

Had to reboot, sorry.

[Marius]

Make sure you install and run SwiftKit as an administrator (Right click > Run as Administrator)

[Dropbox]

I do/did?

[Marius]

Then we really need the debug data from the file, if it's not being written there's something inherently wrong with your system beyond the support we provide I'm afraid.

[D. V. Devnull]

Then we really need the debug data from the file, if it's not being written there's something inherently wrong with your system beyond the support we provide I'm afraid.

I might be able to suggest a workaround for their issue, even though it's a bit off-the-wall.  They'll just have to re-permission the directory that SwiftKit is installed in with...

 

SYSTEM - Full Control

Administrators - Full Control

Everyone - Full Control

 

...make sure it trickles into all the subdirectories/files of that directory area only, and that should give SwiftKit a fair chance to either update or spit back a Debug Information file.  Which brings me to ask, why don't you just preset permissions similar to these when the program is first installed? :(

 

~D. V. "seeing one too many of this type of thread created" Devnull

[Marius]

We don't force permissions because it's inherently insecure and circumverts the security processes in place by AUC in the first place.

 

We want to be advocates of good security practices as well as provide a great tool after all :)

[D. V. Devnull]

Hmm... That's understandable.  I don't like to sacrifice security, provided that can be avoided, as well. :-k

 

There's got to be some way, however, to dodge making people have to "Run As Admin" as many times as there have been?  Doing so creates an even larger dangerous exploit, as the program scope and permissions (at least as I understand them from having been a WinXP user for some time) become unconfined from the User Account that it's running on. :?

 

Could you (or someone else in the SwiftKit team) perhaps design a system service program that only your application could connect with, would only run while your application is up, but could handle the updating work?  Maybe then like Valve's Steam client (which kind of gave me this idea, but I'm thinking a little less aggressively), then the critical part that hits all these errors might be able to do its' job, but without having to open up the main program in Admin mode. :huh:

 

~D. V. "Trying to think of a way to help end the problem..." Devnull