Veeam Endpoint Tray crashes after Creators Update

[gocyclist]

I just updated my PC to Windows 10 Creators Update and Veeam Endpoint is no longer functioning.
Went through the steps outlined in this KB https://www.veeam.com/kb2057, with no luck. My backup settings are intact after the KB steps, however the try still gets a "Veaam Endpoint Tray has stopped working" message.
I cannot create a support ID as I can't access the support section due to the crashing of the tray.

[Adam.Hinton]

Hello. Might be an issue with the Creators Update reading our tray icon. Could we try uninstalling Endpoint, rebooting the machine, and then reinstalling it afterwards? Also if there is any AV software installed, please see the following KB with regards to excluding Endpoint backup. Maybe the update is causing issue with the AV as well:

https://www.veeam.com/kb2034

[gocyclist]

Hello. Might be an issue with the Creators Update reading our tray icon. Could we try uninstalling Endpoint, rebooting the machine, and then reinstalling it afterwards? Also if there is any AV software installed, please see the following KB with regards to excluding Endpoint backup. Maybe the update is causing issue with the AV as well:

https://www.veeam.com/kb2034

Uninstalled Endpoint and attempted to re-install the application. I get a "Veeam.Setup.Endpoint has stopped working" when attempting to install the software. This is run as an administrator and I disabled real-time scanning for Windows Defender as well.

My error log shows the following 2 errors:
.NET Runtime

Code: Select all

Application: Veeam.Setup.Endpoint.dat
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFCF00BFD0C

Application Error

Code: Select all

Faulting application name: Veeam.Setup.Endpoint.dat, version: 1.5.0.306, time stamp: 0x56e0fcd6
Faulting module name: d3d9.dll, version: 10.0.15063.0, time stamp: 0x631de416
Exception code: 0xc0000005
Fault offset: 0x000000000000fd0c
Faulting process id: 0x16c
Faulting application start time: 0x01d2b94dd138b85e
Faulting application path: C:\Users\****\AppData\Local\Temp\RarSFX0\EndPoint\Suite\Veeam.Setup.Endpoint.dat
Faulting module path: C:\WINDOWS\SYSTEM32\d3d9.dll
Report Id: 801cd7e6-5439-4bd6-94f4-dafbf7b15166
Faulting package full name: 
Faulting package-relative application ID: 

[Dima P.]

Randy,

Try to recreate database like described in this post and let us know how it goes.

[gocyclist]

While I followed the steps listed, I still cannot re-install the program due to it crashing on running the installer.

[rweis]

For what it is worth, I also did the Creator's Update and my beta code of VAW is still running in system tray and my last backup was successful (yesterday).

[Dima P.]

Randy,

Please send me you contact email address via PM - I'll ask our support team to reach you.

[gocyclist]

PM sent.

[Dima P.]

Thanks! Support folks reported that the case was opened. Let us know how it goes.

[apronk]

Interestingly the 0xc0000005 seems to pop up quite frequently after the Creators Update.
For any number of programs. We've been having the same problem with KiXforms Classic.
The author managed a work around ignoring a new "hidden window" accessing the Events Loop in the program.
This stopped KiXforms Classic from crashing with the 0xc0000005 error code.
This "Hidden Window" is new to Windows 10 in the Creators Update.
A quick Google Search yields many results in the last month https://www.google.nl/search?q=0xc00000 ... &tbs=qdr:m
Same on the Technet forums: https://social.technet.microsoft.com/Fo ... 0000005%20

[rjaworski]

Gentlemen, please keep this thread updated. I'll hold off with pushing this update until the solution is known.

[apronk]

Safe mode fixes the 0xc0000005 error.
So seemingly there is a new "Inspection" in place in the Creators Update which blocks certain calls.

[gocyclist]

Does the application run normally after installing it in Safe Mode?

[Mike Resseler]

For the 0xc0000005 error. Does anyone with this have a support call open? I'm pretty sure our team wants to investigate the logs (for as much as we can see obviously when it gets) @apronk?

[gocyclist]

I currently have a ticket open with support (02133922). However the answer I've been given currently was to roll back the Creators update and re-install the software. Not the route I want to go with however.

[gocyclist]

Support was able to help me resolve the issue. I was on an older version of RivaTuner Statistics Server. Updating it to the 7.0 beta allowed me to install Endpoint and run the application with no errors.

[Mike Resseler]

Thanks gocyclist for coming back with the solution! I am sure this will help others on the forum also!

[willrun4fun]

Support was able to help me resolve the issue. I was on an older version of RivaTuner Statistics Server. Updating it to the 7.0 beta allowed me to install Endpoint and run the application with no errors.

Wow seems like a wild problem. I found this having the same issue. I installed MSI afterburner yesterday and didn't really think anything of it..... Updating Riva now and seems to have fixed it!

Thanks again.