Case #05276753 File level recovery crashes computer.

[Boize]

Trying to perform file level recovery causes computer to crash at browse stage. It runs for a few seconds and then computer restarts. Disabled antivirus and there was no change.

From Veeam
2/9/2022 8:42:43 PM Mounting restore point
2/9/2022 8:46:20 PM Error Job has failed unexpectedly

Windows error First this

Alternative log directory setting error :
System.UnauthorizedAccessException: Access to the registry key 'HKEY_LOCAL_MACHINESOFTWAREVeeamVeeam Backup and Replication' is denied.
at Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str)
at Microsoft.Win32.RegistryKey.CreateSubKeyInternal(String subkey, RegistryKeyPermissionCheck permissionCheck, Object registrySecurityObj, RegistryOptions registryOptions)
at Microsoft.Win32.RegistryKey.CreateSubKey(String subkey, RegistryKeyPermissionCheck permissionCheck)
at Veeam.Backup.Configuration.RegistryConfigurationController.CreateInternalWithFailover(String subKey, Boolean writable, Boolean enableFailover, RegistryView registryView)
at Veeam.Backup.Configuration.BackupProduct.Veeam.Backup.Configuration.IProduct.CreateRegistryController(Boolean writable, RegistryView registryView, Boolean enableFailover)
at Veeam.Backup.Common.LogFactory.GetComponentLogDirectory(SpecialFolder logFolder)

Using default directory : C:\ProgramData\Veeam\Backup

THEN CRASH ERROR

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user VEEAMSRVitadmin SID (S-1-5-21-734383247-3852121207-1375234751-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

[HannesK]

Hello,
and welcome to the forums.

It sounds like a permission error (at least that's the error message), but that should not crash any machine. As it makes no sense to do guessing on that kind of error on a forum, I can only recommend to continue with support.

Best regards,
Hannes