[SOLVED] (Lack of) Admin Privileges Crash Loop

[micycle]

Windows 7 has decided that I'm no longer an admin on my own PC. As Whatpulse was set to run with admin privileges (through the client before) it can no longer open and runs and crashes in a loop:

Code:

13-12-2014 02:28:14.805  INFO "Starting WhatPulse 2.5..."
13-12-2014 02:28:14.832 DEBUG Installed CrashRpt!
13-12-2014 02:28:20.151 DEBUG Database file:  "C:/Users/Mike/AppData/Local/WhatPulse/whatpulse.db"
13-12-2014 02:28:20.671 DEBUG Database check:  "ok"
13-12-2014 02:28:20.671 DEBUG Opened database in:  520 ms
13-12-2014 02:28:20.676 DEBUG Not running WhatPulse as Administrator! :-(
13-12-2014 02:28:20.676 DEBUG Elevating client to Administrator rights!
13-12-2014 02:28:20.701 DEBUG Shutting down client, we've had enough!
13-12-2014 02:28:20.702 DEBUG Unable to stop watchdog: process not found.
REPEAT: 13-12-2014 02:28:20.731  INFO "Starting WhatPulse 2.5..."

I need a way to reset my client settings without being within the client, so that I can prevent Whatpulse from trying to run with admin privileges. Would this be as simple as deleting a config file somewhere?

Oh, and I need to be an admin to enable the system admin account... sigh.

[Robby250]

I'm pretty sure the configs are stored in whatpulse.db; so cut whatpulse.db and whatpulse.db.backup from C:\Users\YOURUSER\AppData\Local\whatpulse to somewhere else and then run whatpulse again to generate a new database. You'll lose your local stats and settings though, but you can copy the old database back when you have admin privileges.

[smitmartijn]

The settings are stored in the whatpulse.db correct, if you remove that you'll have the default settings, but also your local stats will be gone.

There's another option: edit the whatpulse.db file. Download a SQLite Browser (for example: http://sourceforge.net/projects/sqlitebrowser/), open the database, then the 'settings' table and look for the record that has 'administrator' and 'startup' in it (can't remember the exact name off-hand). Turn that to false and save the database.