Hi @rene_pvh ,
Welcome to the community!
I am sorry that you had some bad experiences with the latest AS version.
Did you install AS 6.5.1.17 today or last week/s?
Have you installed other sw or some windows upgrades after your AS installation?
Are you using AS code too?
I don’t that problem on my pc, same with few customers that are working with the same release.
If you edit your code with just AS and not with other editors (and no AS code) do you see same problem?
Thanks
Ciao
Valerio
The last windows update was a few weeks ago and I have not installed any new software the last days.
I normally don’t use AS code, today I have opened it a few times after I stumbled on the error above.
I does not matter if I only edit in AS or I edit with other editors as well.
not sure if my comment will help you, but I think about your note regarding “Building a project“ , I would like to share few notes made by my local Support in US focus on B&R Antivirus Exclusions:
During the build process, AS needs write access to the following directories, which should be excluded from virus scanners if there are significant performance impacts on build time:
· Temporary directory of the Automation Studio project. This is by default within the project ( \ temp) but can also be placed outside the project by the user.
· Temporary directory of the user who is logged on to the Windows system: C: \ Users \ \ AppData \ Roaming
· Temporary directory of the user who is logged on to the Windows system: C: \ Users \ \ AppData \ Local \ Temp
· Windows temporary directory: C: \ Windows \ Temp
When using fieldbus devices and DTM devices, there is write access to the following directories:
Can you see the source of the error in the Windows event logs? (Windows Event Viewer → Windows Logs → Application)
If you create a new user with admin rights on the same PC, do you have the same problems with the new user?
I have created an empty test project, without any warning or errors, after building is receive in the build, after building I am not able to open st files.
Hi @rene_pvh ,
I asked AI help and below the answer:
Exception code 0xc000041d represents STATUS_FATAL_USER_CALLBACK_EXCEPTION. It occurs when an unhandled exception is encountered during a user callback.
While KERNELBASE.dll is often listed as the “faulting module,” it is typically a “victim” rather than the cause; the error occurs because an application or driver made a request to a Windows API that failed to handle a subsequent error.
Common Causes
Coding Errors: A null pointer exception or an unhandled error within a program’s callback function (common in web-based apps or custom software).
Dependency Issues: Corrupted or missing versions of the .NET Framework.
Software Conflicts: Antivirus software interfering with an application’s anti-cheat or security measures.
System Corruption: Damaged system files or a corrupted Windows user profile.
Recommended Solutions
Run Compatibility Troubleshooter: Right-click the application shortcut, go to Properties > Compatibility, and run the troubleshooter.
Repair .NET Framework: Use the Microsoft .NET Framework Repair Tool to fix dependency errors.
Check for Updates: Install the latest Windows Updates and application-specific patches.
Scan System Files: Open Command Prompt as Administrator and run sfc /scannow followed by DISM.exe /Online /Cleanup-image /Restorehealth to repair corrupted OS files.
Create a New User Profile: If the error persists across multiple apps, the current Windows profile may be corrupt; try running the app from a new Windows user account.
I did a test with your prj and as you see in the video no issue on my laptop.
@rene_pvh I’m not sure what more we can do from Community point of view, you have done a lot, you have crash report, so I think it is time to provide all of these (including link to this discussion) to support team of your local B&R office. Maybe R&D team can read more from crash report.
