(imported topic written by SystemAdmin)
I am running Windows 7 64-bit. I have created a directory “C:\Program Files (x86)\BigFix Enterprise\FixletDebugger” and exploded the ZIP file there. When I try to run the debugger, Windows tells me the program had a fatal error. Is there anything special I need to do to run the Fixlet Debugger on 64-bit Windows?
Thanks!
(imported comment written by SystemAdmin)
Further clarification:
The debugger opens properly, but when I try to evaluate something, I get the following pop-up:
Microsoft Visual C++ Runtime Library:
Runtime Error!
The application has requested the Runtime to terminate in an unusual way.
Any ideas where this is coming from? Do I need to load a particular version of the C++ runtime?
(imported comment written by SystemAdmin)
Where did you get the fixlet debugger binary/zip from?
There may be a packaging error in some specific version as I’m not able to reproduce this.
(imported comment written by SystemAdmin)
I downloaded directly from BigFix. UnZipped to a folder, ran as administrator, crash.
What else can I tell you?
(imported comment written by SystemAdmin)
I get the exact same thing. It will work though if I log on with an account in the Administrators group or use the “runas /user:domain\user FixletDebugger.exe” and that seems to work. I am not sure why the right click option to “Run as administrator” does not work. Probably some UAC thing 
Martin Carnegie
Gulf Breeze Software Partners
(imported comment written by SystemAdmin)
When you use the option to “Run as administrator”, do you get a prompt to type in a user/password? If the user you are logged into Windows is an administrator, you won’t see a prompt.
(imported comment written by SystemAdmin)
Logged on as a user, running as administrator prompts for the credentials.
Logged on as an administrator, running as administrator prompts for yes/no.
Either way, the program still crashes.
(imported comment written by SystemAdmin)
Can you be more specific about what URL you downloaded this from? What version of the executable you have etc?
Thanks
(imported comment written by SystemAdmin)
I downloaded http://software.bigfix.com/download/bes/82/FixletDebugger-8.2.1310.0.zip
My systems have group policies applied (I don’t know what). I haven’t tried running the software on a plain 64-bit Windows 7 system yet, so I will attempt that today if I have time.
(imported comment written by SystemAdmin)
What does the debugger
need
access to to function properly? What registry keys, what files, and what permissions to those items?
Our systems are locked down, so I want to see if I can find out what areas to unlock.
(imported comment written by SystemAdmin)
Problem solved. Our security settings required the following:
Local Security Policy -> Computer Configuration/Windows Settings/Security Settings/Local Policies/User Rights Assignment -> Debug Programs = null
Adding the appropriate users/groups fixed the problem.
(imported comment written by SystemAdmin)
For other possibilities, see http://www-01.ibm.com/support/docview.wss?uid=swg21624120.
Please note, this problem is not specific to Windows 7 or 64-bit operating systems. In our case, it was due to a security setting in Local Policies.