Direkt zum Inhalt

%1 is not a valid win32 application

Thread needs solution
Beginner
Beiträge: 1
Kommentare: 6

Hi Folks,

Acronis support hasn't come up with anything in 2+ weeks so i thought i'd try posting here.

I have a NEW DELL Precision 3620 I7-7700k Win 10 Pro and trying with a fresh factory WIN 10 Pro image.  I'm trying to install Acronis True Image 2017 on it and get the %1 is not a valid win32 application error message.  The install puts the shortcut on the desktop momentarily and then the install rolls back.

Install log shows:

CustomAction MsiTibInstall_TibApiDll__I returned actual error code 1603

I've tried disabling windows defender, firewall, etc.  No luck at all.

I've included more of the install log below in case it might be helpful.

Any help would be much appreciated.

Thanks!

Dennis

 

 

 

1: 15:49:25.179: MSI_TRACE(tib): Installer::InfFile::InstallServicesFromSection: the operation for section DefaultInstall.Services was performed with status 0
1: 15:49:25.179: MSI_TRACE(tib): Ignore reboot requirement
1: 15:49:25.179: MSI_TRACE(tib): Try to cancel postponed deletion of file '\??\C:\windows\system32\DRIVERS\tib.sys'
1: 15:49:25.179: MSI_TRACE(tib): Postponed file deletion is not scheduled for path '\??\C:\windows\system32\DRIVERS\tib.sys'
1: 15:49:25.179: MSI_TRACE(tib): FlushFileBuffers
1: 15:49:25.179: MSI_TRACE(tib): Failed to open control device '\\.\Global\TibControl': status 2
1: 15:49:25.179: MSI_TRACE(tib): TibControl::GetRunningDriverBuildNumber: DriverApiClient Init failed with status 0x2
1: 15:49:25.179: MSI_TRACE(tib): Driver::Start
1: 15:49:25.211: MSI_TRACE(tib): StartWindowsService: failed to start service tib, error: Error 0x1
| line: 0xb1fa94636fb34156
| file: k:\1751\kernel\win\framework\usermode\service.cpp:59
| function: Kernel::UserMode::Service::Start
| $module: tib_msi_vs_s_1751
|
| error 0xfff0: %1 is not a valid Win32 application
| line: 0xbd28fdbd64edb8f1
| file: k:\1751\common\error.cpp:307
| function: Common::Error::AddWindowsError
| code: 0x800700c1
| $module: tib_msi_vs_s_1751
1: 15:49:25.211: MSI_TRACE(tib): Failed to install: status 193.
1: 15:49:25.211: MSI_TRACE(tib): Already detected as stoppable
1: 15:49:25.211: MSI_TRACE(tib): Uninstall stoppable driver
1: 15:49:25.211: MSI_TRACE(tib): StopWindowsService: tib is already stopped
1: 15:49:25.211: MSI_TRACE(tib): Start simple uninstall procedure
1: 15:49:25.211: MSI_TRACE(tib): Installer::InstallByDefault(C:\Users\ADMIN\AppData\Local\Temp\40257281-A7D3-4048-9D68-C55FAB5B6891\tib_uninstall.inf)
1: 15:49:25.211: MSI_TRACE(tib): defaultInstallSection=DefaultInstall
1: 15:49:25.211: MSI_TRACE(tib): Installer::InfFile::InstallServicesFromSection: the operation for section DefaultInstall.Services was performed with status 0
1: 15:49:25.211: MSI_TRACE(tib): Installer::ServiceInformation::Query
1: 15:49:25.211: MSI_TRACE(tib): Service tib does not exist
1: 15:49:25.211: MSI_TRACE(tib): Installer::DeleteService for tib
1: 15:49:25.211: MSI_TRACE(tib): Service tib does not exist
1: 15:49:25.211: MSI_TRACE(tib): Installer::ServiceInformation::Query
1: 15:49:25.211: MSI_TRACE(tib): Service tib does not exist
1: 15:49:25.211: MSI_TRACE(tib): Driver file 'C:\windows\system32\DRIVERS\tib.sys' has just been deleted
1: 15:49:25.226: MSI_TRACE(tib): Driver uninstalled due to rollback with status 0.
1: 15:49:25.226: MSI_TRACE(tib): Action handler failed with status 193.
1: 15:49:25.226: MSI_TRACE(tib): Operation failed with status 193
1: MSIGEN:SendMessageToInstaller: started
1: MSIGEN:SendMessageToInstaller: MsiCreateRecord succeeded
1: MSIGEN:SendMessageToInstaller: MsiRecordSetStringW succeeded
{09FC4C04-FD7F-4f4c-967A-62597EBA9218} Common::Error (Base64) = 77u/PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiID8+DQo8WE1MX1NFUklBTElaRVI+DQoJPFNlcmlhbGl6ZWRPYmplY3Q+QWZEL0FBQkM3dnkrZFF3WXdTVXhJR2x6SUc1dmRDQmhJSFpoYkdsa0lGZHBiak15SUdGd2NHeHBZMkYwYVc5dUFHTnZaR1VBVHNFQUI0QUFBQUFBSkcxdlpIVnNaUUJCZEdsaVgyMXphVjkyYzE5elh6RTNOVEVBSkdacGJHVUFRV3M2WERFM05URmNhMlZ5Ym1Wc1hIZHBibHhtY21GdFpYZHZjbXRjZFhObGNtMXZaR1ZjYlhOcFhHeGxaMkZqZVZ4amRYTjBiMjFmWVdOMGFXOXVMbU53Y0FBa1puVnVZd0JCWUdGdWIyNTViVzkxY3kxdVlXMWxjM0JoWTJVbk9qcERkWE4wYjIxQlkzUnBiMjVRY205alpYTnpiM0k2T2xCeWIyTmxjM01BSkd4cGJtVUFUaE1CQUFBQUFBQUFBQT09PC9TZXJpYWxpemVkT2JqZWN0Pg0KPC9YTUxfU0VSSUFMSVpFUj4NCg==
1: MSIGEN:SendMessageToInstaller: message sent
CustomAction MsiTibInstall_TibApiDll__I returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 15:49:25: InstallFinalize. Return value 3.
MSI (s) (70:04) [15:49:25:242]: Note: 1: 2265 2:  3: -2147287035
MSI (s) (70:04) [15:49:25:242]: User policy value 'DisableRollback' is 0
MSI (s) (70:04) [15:49:25:242]: Machine policy value 'DisableRollback' is 0
MSI (s) (70:04) [15:49:25:242]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1251049002,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (70:04) [15:49:25:242]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (70:04) [15:49:25:242]: Executing op: DialogInfo(Type=1,Argument=Acronis True Image)
MSI (s) (70:04) [15:49:25:242]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (70:04) [15:49:25:242]: Executing op: ActionStart(Name=MsiTibInstall_TibApiDll__I,,)
MSI (s) (70:04) [15:49:25:242]: Executing op: ProductInfo(ProductKey={EC52AEF1-B059-49B8-95C1-72296732005C},ProductName=Acronis True Image,PackageName=AcronisTrueImage.msi,Language=1033,Version=335552361,Assignment=1,ObsoleteArg=0,ProductIcon=product.ico,,PackageCode={307FA17F-A18B-48A5-B74C-BBEA3E47451C},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
MSI (s) (70:04) [15:49:25:242]: Executing op: ActionStart(Name=MsiTibInstall_TibApiDll__IR,,)
MSI (s) (70:04) [15:49:25:257]: Executing op: CustomActionRollback(Action=MsiTibInstall_TibApiDll__IR,ActionType=3329,Source=BinaryData,Target=MsiTibRollbackInstall,CustomActionData=C:\Users\ADMIN\AppData\Local\Temp\tmpD720.tmp)
MSI (s) (70:9C) [15:49:25:257]: Invoking remote custom action. DLL: C:\windows\Installer\MSI4EF.tmp, Entrypoint: MsiTibRollbackInstall
1: BaseCustomActionData: OpenDataFile OpenIO(C:\Users\ADMIN\AppData\Local\Temp\tmpD720.tmp), win32 code: 0
1: 15:49:25.304: MSI_TRACE(tib): MsiTibRollbackInstall: build number 1751
1: 15:49:25.304: MSI_TRACE(tib): CustomActionProcessor::RollbackInstall()...
1: 15:49:25.304: MSI_TRACE(tib): Create HybridDriver
1: 15:49:25.304: MSI_TRACE(tib): Service binary: tib
1: 15:49:25.304: MSI_TRACE(tib): 64-bit subkey System\CurrentControlSet\Services\tib has not been found
1: 15:49:25.304: MSI_TRACE(tib): 32-bit subkey System\CurrentControlSet\Services\tib has not been found
1: 15:49:25.304: MSI_TRACE(tib): Failed to open registry key: 2
1: 15:49:25.304: MSI_TRACE(tib): Failed to read driver path 'tib' from the registry: status 2
1: 15:49:25.304: MSI_TRACE(tib): Driver name=tib version=1188 infFile=C:\Users\ADMIN\AppData\Local\Temp\AA038C20-A228-486B-B96D-20DD0AB60383\tib.x64.inf binPath=tib
1: 15:49:25.304: MSI_TRACE(tib): Installer::ServiceInformation::Query
1: 15:49:25.304: MSI_TRACE(tib): Service tib does not exist
1: 15:49:25.304: MSI_TRACE(tib): 64-bit subkey Software\Acronis\tib has not been found
1: 15:49:25.304: MSI_TRACE(tib): 32-bit subkey Software\Acronis\tib has not been found
1: 15:49:25.304: MSI_TRACE(tib): Failed to open registry key: 2
1: 15:49:25.304: MSI_TRACE(tib): No installed driver found
1: 15:49:25.304: MSI_TRACE(tib): Hybrid driver constructed without version restrictions (0 >= 0)
1: 15:49:25.304: MSI_TRACE(tib): HybridDriver: detect stoppable tib
1: 15:49:25.304: MSI_TRACE(tib): Uninstall stoppable driver
1: 15:49:25.304: MSI_TRACE(tib): Start simple uninstall procedure
1: 15:49:25.304: MSI_TRACE(tib): Installer::InstallByDefault(C:\Users\ADMIN\AppData\Local\Temp\AA038C20-A228-486B-B96D-20DD0AB60383\tib_uninstall.inf)
1: 15:49:25.304: MSI_TRACE(tib): defaultInstallSection=DefaultInstall
1: 15:49:25.304: MSI_TRACE(tib): Installer::InfFile::InstallServicesFromSection: the operation for section DefaultInstall.Services was performed with status 0
1: 15:49:25.320: MSI_TRACE(tib): Installer::ServiceInformation::Query
1: 15:49:25.320: MSI_TRACE(tib): Service tib does not exist
1: 15:49:25.320: MSI_TRACE(tib): Installer::DeleteService for tib
1: 15:49:25.320: MSI_TRACE(tib): Service tib does not exist
1: 15:49:25.320: MSI_TRACE(tib): Installer::ServiceInformation::Query
1: 15:49:25.320: MSI_TRACE(tib): Service tib does not exist
1: 15:49:25.320: MSI_TRACE(tib): Warning: Driver::RemoveDriverFile skip the removing of driver file, driver path is empty
1: 15:49:25.320: MSI_TRACE(tib): Driver uninstalled due to rollback with status 0.
MSI (s) (70:04) [15:49:25:320]: Executing op: ActionStart(Name=MsiSyncAgentServiceInstall_SyncAgent__I,,)
MSI (s) (70:04) [15:49:25:320]: Executing op: ActionStart(Name=MsiSyncAgentServiceInstall_SyncAgent__IR,,)
MSI (s) (70:04) [15:49:25:320]: Executing op: CustomActionRollback(Action=MsiSyncAgentServiceInstall_SyncAgent__IR,ActionType=3329,Source=BinaryData,Target=MsiSyncAgentServiceInstallRollback,CustomActionData=C:\Users\ADMIN\AppData\Local\Temp\tmpD720.tmp)
MSI (s) (70:A8) [15:49:25:336]: Invoking remote custom action. DLL: C:\windows\Installer\MSI52E.tmp, Entrypoint: MsiSyncAgentServiceInstallRollback
1: MSIGEN:MsiSyncAgentServiceInstallRollback: operation started.
MSI (s) (70:04) [15:49:25:492]: Executing op: ActionStart(Name=MsiSchedul2Install_Scheduler64__I,,)
MSI (s) (70:04) [15:49:25:492]: Executing op: ActionStart(Name=MsiSnapmanInstall_SnapAPI32__I,,)
MSI (s) (70:04) [15:49:25:492]: Executing op: ActionStart(Name=MsiSnapmanInstall_SnapAPI32__IR,,)
MSI (s) (70:04) [15:49:25:492]: Executing op: CustomActionRollback(Action=MsiSnapmanInstall_SnapAPI32__IR,ActionType=3329,Source=BinaryData,Target=MsiSnapmanRollbackInstall,CustomActionData=C:\Users\ADMIN\AppData\Local\Temp\tmpD720.tmp)
MSI (s) (70:DC) [15:49:25:507]: Invoking remote custom action. DLL: C:\windows\Installer\MSI5DB.tmp, Entrypoint: MsiSnapmanRollbackInstall
1: BaseCustomActionData: OpenDataFile OpenIO(C:\Users\ADMIN\AppData\Local\Temp\tmpD720.tmp), win32 code: 0
1: 15:49:25.523: MSI_TRACE(snapman): MsiSnapmanRollbackInstall: build number 2767
1: 15:49:25.523: MSI_TRACE(snapman): CustomActionProcessor::RollbackInstall()...
1: 15:49:25.523: MSI_TRACE(snapman): Create HybridDriver
1: 15:49:25.539: MSI_TRACE(snapman): Service binary: snapman
1: 15:49:25.539: MSI_TRACE(snapman): Driver name=snapman version=2541 infFile=C:\Users\ADMIN\AppData\Local\Temp\B210DFC7-F285-4EEE-8D3F-5D792352A78C\snapman.x64.inf binPath=snapman
1: 15:49:25.539: MSI_TRACE(snapman): Installer::ServiceInformation::Query
1: 15:49:25.539: MSI_TRACE(snapman): SERVICE_STATUS for service snapman:
1: 15:49:25.539: MSI_TRACE(snapman): ---------------------------------
1: 15:49:25.539: MSI_TRACE(snapman): ServiceType: KERNEL_DRIVER
1: 15:49:25.539: MSI_TRACE(snapman): CurrentState: RUNNING
1: 15:49:25.539: MSI_TRACE(snapman): ControlsAccepted: STOP
1: 15:49:25.539: MSI_TRACE(snapman): Win32ExitCode: 0
1: 15:49:25.539: MSI_TRACE(snapman): ServiceSpecificExitCode: 0
1: 15:49:25.539: MSI_TRACE(snapman): CheckPoint: 0
1: 15:49:25.539: MSI_TRACE(snapman): WaitHint: 0
1: 15:49:25.539: MSI_TRACE(snapman): ---------------------------------
1: 15:49:25.539: MSI_TRACE(snapman): Service snapman is installed
1: 15:49:25.539: MSI_TRACE(snapman): Installed version: 2541
1: 15:49:25.539: MSI_TRACE(snapman): Hybrid driver constructed without version restrictions (2541 >= 2420)
1: 15:49:25.554: MSI_TRACE(snapman): StopWindowsService: snapman succeeded
1: 15:49:25.554: MSI_TRACE(snapman): HybridDriver: detect stoppable snapman
1: 15:49:25.554: MSI_TRACE(snapman): Uninstall stoppable driver
1: 15:49:25.554: MSI_TRACE(snapman): StopWindowsService: snapman is already stopped
1: 15:49:25.554: MSI_TRACE(snapman): Start simple uninstall procedure
1: 15:49:25.554: MSI_TRACE(snapman): Installer::InstallByDefault(C:\Users\ADMIN\AppData\Local\Temp\B210DFC7-F285-4EEE-8D3F-5D792352A78C\snapman_uninstall.inf)
1: 15:49:25.554: MSI_TRACE(snapman): defaultInstallSection=DefaultInstall
1: 15:49:25.554: MSI_TRACE(snapman): Installer::InfFile::InstallServicesFromSection: the operation for section DefaultInstall.Services was performed with status 0
1: 15:49:25.554: MSI_TRACE(snapman): Installer::ServiceInformation::Query
1: 15:49:25.554: MSI_TRACE(snapman): Service snapman does not exist
1: 15:49:25.554: MSI_TRACE(snapman): Installer::DeleteService for snapman
1: 15:49:25.554: MSI_TRACE(snapman): Service snapman does not exist
1: 15:49:25.554: MSI_TRACE(snapman): Installer::ServiceInformation::Query
1: 15:49:25.554: MSI_TRACE(snapman): Service snapman does not exist
1: 15:49:25.554: MSI_TRACE(snapman): Driver file 'C:\windows\system32\DRIVERS\snapman.sys' has just been deleted
1: 15:49:25.554: MSI_TRACE(snapman): Driver uninstalled due to rollback with status 0.
MSI (s) (70:04) [15:49:25:570]: Executing op: ActionStart(Name=MsiFltSrvInstall64_fltsrv_component__I,,)
MSI (s) (70:04) [15:49:25:570]: Executing op: ActionStart(Name=MsiFltSrvInstall64_fltsrv_component__IR,,)
MSI (s) (70:04) [15:49:25:570]: Executing op: CustomActionRollback(Action=MsiFltSrvInstall64_fltsrv_component__IR,ActionType=3329,Source=BinaryData,Target=MsiFltSrvRollbackInstall64,CustomActionData=C:\Users\ADMIN\AppData\Local\Temp\tmpD720.tmp)
MSI (s) (70:CC) [15:49:25:570]: Invoking remote custom action. DLL: C:\windows\Installer\MSI62A.tmp, Entrypoint: MsiFltSrvRollbackInstall64
1: BaseCustomActionData: OpenDataFile OpenIO(C:\Users\ADMIN\AppData\Local\Temp\tmpD720.tmp), win32 code: 0
1: 15:49:25.601: MSI_TRACE(fltsrv): MsiFltSrvRollbackInstall: build number 2402
1: 15:49:25.601: MSI_TRACE(fltsrv): CustomActionProcessor::RollbackInstall()...
1: 15:49:25.601: MSI_TRACE(fltsrv): Create UnstoppableDriver
1: 15:49:25.617: MSI_TRACE(fltsrv): Service binary: fltsrv
1: 15:49:25.617: MSI_TRACE(fltsrv): Driver name=fltsrv version=2274 infFile=C:\Users\ADMIN\AppData\Local\Temp\50DC3B64-5D5D-437F-8528-4A05593478CD\fltsrv.x64.inf binPath=fltsrv
1: 15:49:25.617: MSI_TRACE(fltsrv): Rollback just installed updates
1: 15:49:25.617: MSI_TRACE(fltsrv): No obsolete version found to restore
1: 15:49:25.617: MSI_TRACE(fltsrv): Copy file 'C:\Users\ADMIN\AppData\Local\Temp\0F978B09-E18B-410A-8ACD-08ABC73F5DE7' to 'C:\windows\system32\DRIVERS\fltsrv.sys'
1: 15:49:25.632: MSI_TRACE(fltsrv): Driver restored: 'C:\Users\ADMIN\AppData\Local\Temp\0F978B09-E18B-410A-8ACD-08ABC73F5DE7'-->'C:\windows\system32\DRIVERS\fltsrv.sys'
1: 15:49:25.632: MSI_TRACE(fltsrv): Image path restored as expanded string: 'system32\DRIVERS\fltsrv.sys'
1: 15:49:25.632: MSI_TRACE(fltsrv): Rollback update of unstoppable driver
1: 15:49:25.632: MSI_TRACE(fltsrv): Control device '\\.\Global\StorageFilterControl' handle=804
1: 15:49:25.632: MSI_TRACE(fltsrv): Control device handle 804 has been closed
MSI (s) (70:04) [15:49:25:632]: Executing op: ActionStart(Name=MsiCreateTrialRegistry_TrueImageDemon__I,,)
MSI (s) (70:04) [15:49:25:632]: Executing op: ActionStart(Name=MsiCreateTrialRegistry_TrueImageDemon__IR,,)
MSI (s) (70:04) [15:49:25:632]: Executing op: CustomActionRollback(Action=MsiCreateTrialRegistry_TrueImageDemon__IR,ActionType=3329,Source=BinaryData,Target=MsiCreateTrialRegistryRollback,CustomActionData=C:\Users\ADMIN\AppData\Local\Temp\tmpD720.tmp)
MSI (s) (70:AC) [15:49:25:648]: Invoking remote custom action. DLL: C:\windows\Installer\MSI66A.tmp, Entrypoint: MsiCreateTrialRegistryRollback
 

0 Users found this helpful
Frequent Poster
Beiträge: 103
Kommentare: 750

#1

Did you run the install as Administator?

Forum Hero
Beiträge: 36
Kommentare: 7247

#2

Look here: https://support.microsoft.com/en-us/help/834484/you-receive-an-error-1603-a-fatal-error-occurred-during-installation-error-message-when-you-try-to-install-a-windows-installer-package

Beginner
Beiträge: 1
Kommentare: 6

#3

Yes, run as administrator with same results.

Beginner
Beiträge: 1
Kommentare: 6

#4

Yes, I've reviewed that post as well.  No encryption is being used yet, system account has full control of the entire c: drive, and no other versions of the software exist.  I did a complete factory image reinstall with the same results.

Thanks!

 

Enchantech wrote:

Look here: https://support.microsoft.com/en-us/help/834484/you-receive-an-error-1603-a-fatal-error-occurred-during-installation-error-message-when-you-try-to-install-a-windows-installer-package

Legend
Beiträge: 81
Kommentare: 17565

#5

Dennis, what type of user account is the install being run from?  Is this an Administrator account as that is needed here?

Beginner
Beiträge: 1
Kommentare: 6

#6

Yes, run from the administrator account.

Thanks!

 

Steve Smith wrote:

Dennis, what type of user account is the install being run from?  Is this an Administrator account as that is needed here?

Legend
Beiträge: 81
Kommentare: 17565

#7

Dennis, I can only suggest going back to basics here.

Download and run the Acronis Cleanup Tool as Administrator to clean up any residue from your failed install attempts (link in my signature).  Restart the computer to complete this action.

Download the full ATIH 2017 latest build installer from your Acronis account download page (8053 Standard or 6206 for New Generation).  Verify the checksum for the downloaded installer program.

Run the installer as Administrator.

Beginner
Beiträge: 1
Kommentare: 6

#8

Thanks, Yes, using the 8053 build.  No need to use the cleanup utility as i've attempted with a fresh factory reset of windows 10 from DELL.  The downloads are fine.  I've tried a couple different version sent to me by Acronis prior to the 8053, I even attempted to install the 2015 HD version that came with a Crucial SSD drive.  It returns the same error :(

 

Steve Smith wrote:

Dennis, I can only suggest going back to basics here.

Download and run the Acronis Cleanup Tool as Administrator to clean up any residue from your failed install attempts (link in my signature).  Restart the computer to complete this action.

Download the full ATIH 2017 latest build installer from your Acronis account download page (8053 Standard or 6206 for New Generation).  Verify the checksum for the downloaded installer program.

Run the installer as Administrator.

Legend
Beiträge: 81
Kommentare: 17565

#9

Dennis, in your original post with the install log detail, there is mention of sandbox in there?  Is there a possibility here that the install process was sandboxed by any security software?

See KB 8305: Installation of Acronis Product Fails with "...not a valid Win32 application" which was written for a much older version of the product but may have some pointers?

See also Forum post: 127617: Help error installing acronis 2017 build 5554 windows 10 1607 for the same error on build 5554 of ATIH 2017 but with no solution posted - may be worth posting to that topic to see if the OP Joshua received a solution to his problem from Acronis development?

Beginner
Beiträge: 0
Kommentare: 2

#10

Hi!

Its been more than a year and this issue still exists.

I have a fresh Windows 10 installation and I am not able install TrueImage 2018. The error message is the same as above.

I have tried all recommended way but it still fails.

Will this ever be addressed by Acronis!?

Legend
Beiträge: 81
Kommentare: 17565

#11

Tommy, welcome to these User Forums.

Please see this forum topic where one user found one cause of this issue

If you still have the same error, then more information will be needed.

Beginner
Beiträge: 0
Kommentare: 2

#12

Hi Steve,

Yes, I have seen it but I haven't disabled Device Security in Defender before and my testing failed. 

IT WORKS NOW! Thanks!

Very good spotting from this user. I have listed below steps as above thread needs some googling to find the right places.

1. Run GPEDIT.MSC as admin and go to:

Computer Configuration\Administrative Templates\System\Device Guard

disable - > Turn On Virtualization Based Security

2. Open Windows Defender and go to Device Security

Then to "Core Isolation Details" and Turn Off "Memory Integrity"

 

That fixed the issue. It also fixes it for True Image 2019.

 

I think Acronis should update their knowledge base to ensure users are able to find this work around in the documentation. Ignoring this is not very helpful and professional from the Vendor who is getting paid for the product.

Cheers!

Forum Star
Beiträge: 130
Kommentare: 2914

#13
Tommy wrote:

I think Acronis should update their knowledge base to ensure users are able to find this work around in the documentation. Ignoring this is not very helpful and professional from the Vendor who is getting paid for the product.

Cheers!

I suggest you seen in-App feedback asking that appropriate documentation be developed.

Unfortunately much of the documentation for ATI is alarmingly superficial.

Ian 

Forum Moderator
Beiträge: 122
Kommentare: 4633

#14

Hello Everyone,

the issue is now documented in https://kb.acronis.com/content/61700