My C++/MFC program uses the CFileDialog class to retrieve a filename to open. If I comment out the DoModal() call, no Verifier Stops occur. If the dialog is opened (even if it is then simply Canceled), the stops are generated — three in a row. So I tried the Common File Dialog Sample: https://github.com/Microsoft/Windows-classic-samples/tree/master/Samples/Win7Samples/winui/shell/appplatform/commonfiledialog. Same ..
I encounter some very strange behavior and I don’t know how to handle it. I suspect that the behavior started to reproduce after last Windows upgrade. But I am not sure if it has anything related to it. (I discovered it when I tried to run maven, which uses java) The behavior is the following: ..
Simply, I cannot run App verifier (WOW or 64-bit). It simply does not start. Event viewer says: Faulting application name: appverif.exe, version: 10.0.18362.1, time stamp: 0x58ca3409 Faulting module name: ntdll.dll, version: 10.0.18362.1139, time stamp: 0x335bbdaf Exception code: 0xc0000374 Fault offset: 0x000dfa1d Faulting process ID: 0x2ad0 Faulting application start time: 0x01d6aa7ad4a12bf6 Faulting application path: C:WindowsSysWOW64appverif.exe Faulting ..
I’ve enabled application verifier on my application, and it created a registry value VerifierFlags with value 0x80000000 Where do I find a list of possible VerifierFlags values? I tried to lookup online, the only thing I found is about drives. Does anyone know? Source: Windows..