Error viewing .Exe Exported files
Answered
I am a detective with the Las Vegas Metropolitan Police Department in Las Vegas, NV. I am working with a business who utilizes your Nx Witness Client to recover video from a high value burglary. Video was exported in a .exe format (not the .nov format). I am having issues opening the video from the .exe file. I receive a notice "This app cannot run on your PC. To find a version for your PC, check with the software publisher."
This video is critical to our investigation. There have been over 20 days worth of video exported (24 hour increments) and older video has already been overwritten. I am seeking a way to view/open these .exe files to view the available footage.
Scott Ambrose P#6082
Detective
Digital Investigations Bureau
Las Vegas Metropolitan Police Department
400 South Martin Luther King Boulevard, Las Vegas, Nevada 89106
( 702.828.6766 office│ ( 702.817.5423 mobile│ * s6082a@lvmpd.com
DFL 24 RDO’s FSS
-
Hi Scott Ambrose,
I'm sorry to read about the issue you encounter. If the export is made and confirmed, I'm sure there must be a way to make it available to you as well.
Can you answer some questions for me?
- Can you share a screenshot of the notification?
- Can you tell us from which version of the software the data was exported?
- Also, are you sure that the export was made on a Nx Witness system and could be opened on a Nx Witness system? Typically, Nx Witness isn't available in the US, and only the OEM versions of our software are sold in the US, and you would need the client of the OEM to play the *. exe files.
- Can you tell us a bit more about your computer?
Which operating system are you using? 32-Bit or 64-Bit?
-
Hi Scott Ambrose,
It has been a few days since we heard from you.
Has the issue been resolved in the meantime? -
1) See below attached photos for Nx Client Info and Screen Error
2) The .exe files were exported from Nx Witness Client version 4.2.0.32840 (for Windows 64).
3) The files were exported from the Nx Witness Client via the .exe method. I do not know if the .exe was able to be opened on the system from which it was exported.
4) My system is Windows 64 bit running Windows 10 Pro
-
Hello Scott Ambrose,
I assume the top window is from the user and the bottom one is yours, right?
Perhaps you are using an ARM based Windows system, like some Microsoft Surface devices use?
In the meantime, I do not know at the moment what is causing the issue, but I share the questions also internally.
Can you try the following? Right-click the file and try to open it as Administrator.
I also found an online article that contains a few options to resolve the issue, you can find it HERE.
My bet would option 3 or 4. -
Yes top is from the business PC running Nx Witness Client and bottom is my Windows PC (Tolino Forensic Machine. Also tried on my Windows bootcamp MacBook Pro).
Tried the administrator and received same error.
Followed the steps provided in the link with no success.
Is there any proprietary player that Nx Witness Client offers that can open/view the .exe?
-
Hello Scott Ambrose,
Strange issue.
There is no proprietary player. The *.exe file contains the player and should open, and you should be able to view the footage of any included device, export or bookmark relevant parts, etc.
I have set up a Windows system with a client with an attempt to reproduce the issue, which I unfortunately wasn't able to.
What I try as well is if I could open a *.exe file in an installed Desktop client, and that was possible.
I would suggest trying that as well.
You can download the installation package through this LINK.
Assuming you are able to successfully install the desktop client, you can proceed with the following steps;
- Click on the Main menu icon (1)
- Select Open... (2)
- Select Files... (3)
The following menu should appear:
- First select All Files (*.*) (1)
- Select the location and file (2)
- Select Open (3)
In case of large files, please allow the system some time to open (seconds to minutes).
-
Hi Scott Ambrose,
Thank you for the feedback. You made my day.
It remains a weird issue you encountered, but I'm happy we found a solution.
Please sign in to leave a comment.
Comments
8 comments