DATS V3 problem

I have the Dayton Audio DATS V3 speaker tester where the software works on a Windows 10 PC.

I went to install it on another Windows 10 PC and the software starts, but says not responding then closes.

The Windows 10 PC it works on and the one it doesn't work on:

1. Are the same model.
2. Have the same exact hardware configuration. Same model RAM, same processor, same hard drive ETC...
3. Have the same exact software configuration.

By identical I mean that I can swap hard drives between the two and the only thing I might have to do is reactivate Windows.

Also given the PCs are so identical, it should not be possible for me to be having this problem, yet I have it.

Any reason for it not to run on another identical PC?
 
Last edited:
Here's what event viewer shows.

Faulting application name: DATS.exe, version: 3.1.6.0, time stamp: 0x61422597
Faulting module name: DATS.exe, version: 3.1.6.0, time stamp: 0x61422597
Exception code: 0xc000041d
Fault offset: 0x0006d583
Faulting process id: 0x1070
Faulting application start time: 0x01db99d05dcc69d4
Faulting application path: C:\Program Files (x86)\DATS_V3\DATS.exe
Faulting module path: C:\Program Files (x86)\DATS_V3\DATS.exe
Report Id: d2f90070-80f2-4647-8603-b970d0bae351
Faulting package full name:
Faulting package-relative application ID:


Fault bucket 1621159902348191342, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: DATS.exe
P2: 3.1.6.0
P3: 61422597
P4: DATS.exe
P5: 3.1.6.0
P6: 61422597
P7: c000041d
P8: 0006d583
P9:
P10:

Analysis symbol:
Rechecking for solution: 0
Report Id: d2f90070-80f2-4647-8603-b970d0bae351
Report Status: 268435456
Hashed bucket: e3b6451b44016483867f84578792266e
Cab Guid: 0
 
I tried compatibility mode but that didn't work.

I already have all those permissions, yet I get the following no matter what I do:


111.png



222.png



333.png



444.png



What good is having event viewer list a folder that I cannot view even when I have direct ownership?
 
NTFS permissions are hierarchical in that certain attributes can override others. If there is an explicit “Deny” permission set somewhere that will take precedence and your read permissions will be ignored. This is by design.

Certain attributes like “hidden” and “system” sometimes block some actions.

If you are lucky, you never get to find out about this 🙂.

It can take a lot of patient investigation to get to the bottom of these issues and it is years since I had to do it.

In the back of my mind there is something about “Trusted Installer” rights that can also get in the way.

I wish you luck, these issues are not the ones that bring joy ☹️.

Jeff.
 
I did that and the admin account I use has all access that is shown on that tab.

It's acting like I am not the owner of said folder even though I am given each time I try to view the folder I have to do the same steps again except changing the owner as it shows my account as owner.

That said why would event viewer call out a folder that cannot be viewed even when the admin account I am on is owner of said folder.
 
The Advanced Security Settings for AppCrash.... form shows:

Name: mylogon/name

Owner: Unable to display current owner

Permissions tab:

You must have Read permissions to view the properties of this object.

Click Continue to attempt the operation with administrative permissions.


I press <Continue>

The Advanced Security Settings for AppCrash.... form now shows:

Name: mylogon/name

Owner: now shows my id

Integrity level: High Mandatory Level

Permissions tab:

Now shows I have the following:

Type: Allow

Access: Full Control

Inherited From: None

Applies to: This folder, subfolders and files

Press <Edit> shows:

Basic permissions shows all checked except Special permissions (not ticked, not enabled)

Advanced permissions shows everything (both columns) checked.

I then <OK> back on each page/form to return to the folder, and still get a permissions error.

https://learn.microsoft.com/en-us/answers/questions/2192961/werreportarchive-permissions

Pretty much exactly what I'm seeing.