Base Product

The following issues relating to the Arcserve Backup base product are known to exist in this release:

Due to a NetBIOS limitation, computer names longer than 15 characters are truncated to 15 characters, including when you set up a host Server.
If you use the Master Setup to install Arcserve Backup remotely to a system in another Windows domain, you may receive a message indicating that the installation failed when it is successful. This behavior occurs because the Master Setup cannot accurately detect the activity on the remote machine in the other domain because of a firewall or due to a lost network connection. Check the installation status on the remote machine to verify that the installation succeeded.
If you import a DLTWORM-capable media into a library that has not converted to WORM, the Quick erase and Convert to WORM media option is disabled, then perform a full inventory of tapes to enable this option because this capability can be recognized only by reading the media.
If you use WORM media as the destination for any cross-platform jobs involving the Arcserve Backup for UNIX Agent for Oracle or the Arcserve Backup for Linux Agent for Oracle, these agents may not behave as expected. Because WORM media is not supported on the UNIX or Linux agents, these jobs may use destinations other than the WORM media.
Installing 32-bit components on a 64-bit machine generates two copies of the file PortsConfig.cfg on the machine. The PortsConfig.cfg file for the 32-bit components is in c:\Program Files (x86)\CA\SharedComponents\ARCserve Backup and the PortsConfig.cfg file for the 64-bit components is in c:\Program Files \CA\SharedComponents\ARCserve Backup. If you make changes to one, make the same changes to the other, or the components may not be able to contact one another.
If you install agents on cluster nodes, do not backup the physical nodes (the private drives C: and D:) or non-shared disks through preferred share using the virtual Server IP address, because virtual Servers can be moved from one node to another. For example, if virtual Server 1 resides on physical node 1 and you backed up virtual Server 1 through preferred share, the non-shared drives on physical node 1 are also backed up. If you move virtual Server 1 to physical node 2, and perform a Restore to Original Location, the non-shared drives from physical node 1 are restored to physical node 2.
The default TCP/IP protocol is recommended for ODBC communication. If this setting is changed to Named Pipe protocol, ODBC fails.
Special characters in media files will interfere with RMAN jobs. Avoid using special characters such as <,>.
Running RMAN scripts to backup remote installations of Arcserve Backup Agent for Oracle to the Arcserve Backup Server may fail if the remote machine was registered to Arcserve Backup Server with a fake name.
Job redirection is no longer supported. As an alternative, you can use the makeup job feature. For more information regarding makeup jobs, refer to the Administration Guide.
When the Windows security policy is enabled on the machine where Arcserve Backup is installed, an audit log is recorded in the event log at the time of a system application startup, such as Task Manager.
If you apply the license keys for two or more different Arcserve Backup suites on a single Arcserve Server, the license count on the Arcserve Server may not be correct. To resolve this problem, apply the licenses that you require and contact Technical Support at https://www.arcserve.com/support to correct the license count.
The Tape Compare utility does not support comparing tapes that were created using multiplexing or encryption.
- Broadcast Alerts do not function on systems running Microsoft Windows Server 2008. This behavior is observed because Microsoft Windows Server 2008 does not support messaging service.
After you restore the Arcserve 64-bit ASDB, you must perform at least one full backup of the Arcserve Backup database before you perform an incremental or a differential backup. This task helps ensure that Arcserve Backup database backup sessions contain the most current data. This task helps ensure that Arcserve Backup database backup sessions are current.
A NetBIOS name resolving problem between local and remote machines may prevent you from obtaining information from the Diagnostic Wizard. Diagnostic utilities use NetBIOS names to communicate. To avoid communication problems, verify that the remote system is on the network and that the machine name is correctly mapped to the IP address. You should also purge and reload the NetBIOS Remote Cache Name and NetBIOS Remote Machine Name tables. To do so, perform the following steps:
1. Confirm that the remote machine is reachable across the network and that the IP Address matches the remote machine name. Run the following commands to confirm:
  1. ping <MachineName>
  2. ping <IPAddress>
  3. ping <IPAddress>
2. If the remote system can be pinged and the name matches the IP address, the Diagnostic Wizard should experience no problems. If the system cannot be pinged at all, check the network connections and ensure the system is operational. If the name does not match the IP address, continue.
3. Open a command prompt and run ipconfig /all to show the current IP configurations and other network configurations of a machine. Examine the command output for mistakes in your configurations. If mistakes exist, the network cannot communicate properly.
4. Run the following command to check the NetBIOS Remote Cache Name Table:
5. (Optional) If you find a mismatch in the mapping between a System Name and IP Address, run the following command to purge the Server Name and IP address mapping on both the local and remote machines. Otherwise, skip to Step 5.
6. ipconfig /flushdns
7. Purge and reload the NetBIOS Remote Cache Name Table:
8. nbtstat -R
9. Run nbtstat -c again. The table should now be empty, or contain only a few new items with lives of about 600 seconds.
10. Check the NetBIOS Remote Machine Name Table:
11. nbtstat -a <RemoteName>
12. This command lists a remote machine name table for the provided machine name.
13. nbtstat -A <IPAddress>
14. This command lists a remote machine name table for the IP address provided.
15. The tables should show identical information: the name of the remote system as "Registered" for the IP Address.
16. If the steps above do not solve your NetBIOS communication problem, you must contact your WINS Server administrator to reconfigure the system.
The Arcserve Backup database may not contain up-to-date database information (for example, file lists and physical locations) and the Restore Manager, restore by Tree, source directory tree may not display up-to-date information immediately after you restore the Arcserve Backup database to its original location (original computer or original database instance) or to a different location (different computer or different database instance).
To resolve this problem, perform the following:

After you restore the Arcserve Backup database, use the Merge utility to merge the Arcserve Backup database backup sessions.
Close and then reopen the Restore Manager window to refresh the information that displays in the Restore by Tree source directory tree.

When you modify a makeup job that was automatically created after a full-node backup job has failed, you will see that the MSDEWriter, SQLServerWriter and WMIWriter objects have been selected in the Backup Manager, Source directory tree. These objects are displayed with excluded text which will not be backed up when the makeup job is submitted.
When you log off an interactive Windows session while a message (such as tape mount) is still displayed, some temporary files will remain in the Arcserve Backup Temp folder.
Backup jobs performed with Windows 2008 system may include the following files that Microsoft recommends not be backed up, even if they are specified in the FilesNotToBackup registry key:
- index.dat
- MsDtc.log
- dtctrace.log
You should skip these files when restoring the database.
Arcserve Backup operations executed on the same tapekey after tapecopy has been executed could affect either the source or the destination tape. Job failure may also occur if a session is added to either the source or destination tape after tapecopy because Arcserve Backup may not be able to restore that added session as the tape is identified by three items: the tape name, the random ID, and the sequence number. The combination of these three tape identifiers is called the tapekey. When submitting a tapecopy job with a command such as “tapecopy –s –d –t”, Arcserve Backup automatically assumes the tapekey of the destination tape is the same as the source tape and views it as if only one tape exists.
If you do not want the destination tape to be the exact same as the source tape, then include the –idr switch with the tapecopy command so that Arcserve Backup automatically assigns a different random ID to the destination tape and ensures that the destination tape is not exactly the same as the source tape.

If you include the –idr switch with the tapecopy command, the random ID of the destination tape will not be the same as the source tape and as a result, the destination tape could not be used at a later time for disaster recovery purposes.
If you do not include -idr switch with the tapecopy command, then use the destination tape at a later time to perform a disaster recovery operation because the destination tape will be exactly the same as the source tape.

This release of Arcserve Backup automatically creates a new media pool with the same name given to media in an r12 or prior environment and inventoried in the current environment.
When you run ca_recoverdb.exe to recover the Arcserve Backup database, you may receive the following warning message:
W5110 The Database is no longer available
During recovery, the Arcserve Backup database is offline and client programs cannot access the data base during this period. This message does not prevent recovery from completing successfully.
If you are performing backup jobs on a Windows 2008 or Vista system and have specified Pre and Post job commands in the Global Options dialog, Arcserve Backup ignores the user name and password on the Pre/Post tab and executes the commands even if you enter an invalid user name and password combination. Security validation is performed only on Windows 2008 or XP systems.
In Citrix 4.5, you must enable Read/Execute privileges on the Arcserve Backup Home folder to publish the product.
The first job run after you successfully recover the Arcserve Backup database appears in the Status Manager with the same Job ID as the ASDB restore job because of the Job ID assigned to the ASDB restore job is lost after the ASDB is restored successfully.
When the Catalog database folder is changed to a long path name (greater than 140 characters) and backed up, the catalog files may not be kept in the catalog database and an E3408 error is recorded in the Activity Log.
Client Agent Password Security is only supported for the Client Agent for Windows, including the Arcserve Backup Agent for Open Files and VSS Writers. If Password Security is enabled and any database, application, or messaging Agent is installed on the same machine as the Client Agent, whole node backup is not supported. System Security is the default setting. If you have enabled Password Security on the Arcserve Backup Primary or Standalone Server, the automatically-generated Database Protection Job fails for the job queue and Arcserve Catalog Database. You must not enable Password Security in the Agent Configuration on any machine running a database, application, or messaging Agent before submitting the job.
The following issues related to SIS (single instance storage) are known to exist in this release:
- Files in the \SIS Common Store are normally excluded from jobs by the registry key, FilesNotToBackup, and should not be backed up or restored unless they are *.sis files. However:
  - When you perform a remote backup of an entire drive on which Single Instance Storage was activated as the backup source, the job fails and AW0004 is recorded. The reason being Arcserve Backup is attempting to backup files that should have been excluded. Restoring the entire session to its original location also restored files that should have been excluded.
  - When you perform a restore of an entire session, files in the \SIS Common Store that should not have been backed up are now skipped
- Note: If you select only the \SIS Common Store to backup, excluded files are not backed up, as expected.
- When you restore SIS links using the global option "log all activity" set to on, the Job Log shows only the links have been restored, not the data files.
- Note: If data files are already in the \SIS Common Store, those files will not be restored.
- When restoring the \SIS Common Store that was remotely backed up and you have deleted all the link files corresponding to the restored common store files, the common store files are not deleted. The Remote Restore Job Log shows the files as restored.
For jobs shown in the Activity Log, the Media Compression Ratio and the Media Remaining Capacity display as 0 because these parameters are not supported by the backup device.
Arcserve Backup does not support Windows passwords that are 24 characters and longer. When you add a Windows Agent machine to Arcserve Backup, you are prompted for a hostname and password. Even though Windows supports a long password here, Arcserve Backup does not and login fails.
Arcserve Backup does not support restoring a Job Queue session to its original location using normal data recovery processes.

Due to a known issue regarding the startup sequence of Arcserve Backup and Microsoft SQL Express, or SQL Server installed on the same machine as Arcserve Backup, the Event Log may show the following errors after a system reboot:

Failure Audit: 18456 (Source MSSQL$ARCSERVE_DB) - The SQL Server service is not running but client programs are trying to log in, and so, fail.
Error: 17187 (Source MSSQL$ARCSERVE_DB) - The SQL Server service is not running, so it cannot accept a client connection.
Warning 3: (Source SQLBrowser) - This warning is recorded because service starts automatically. Although Arcserve Backup does not use the service setting, the installer changes it. This service should not have been changed to startup automatically. Set the SQL Server Browser service to 'disabled' to avoid this warning.
To eliminate Warning 3, perform the following steps:

Click Start, Control Panel, Administrative Tools, Services.
From the list of services, double-click SQL Server Browser service to open its properties.
Change the startup type to Disabled.
Click OK. Rebooting should now proceed without this warning.

These errors are related to the sequence in which Arcserve Backup and SQL Server services are started and can be eliminated if you adjust the following Arcserve Backup services that depend on SQL Service to start:

Arcserve Backup Database Engine
Arcserve Backup Management Service
Arcserve Backup Universal Agent
Arcserve Backup Tape Engine

Note: If SQL Server is installed on a remote machine, rebooting Arcserve Backup does not affect it.
To adjust Arcserve Backup services
1. Determine SQL Server service name.
2. Find the following registry key:
3. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLXXXX, where XXXX is the unique name of the SQL Server and MSSQLXXXX is the SQL Server Service name.
4. Set Arcserve Backup services to depend on SQL Server service to startup by using the Microsoft sc utility (see Using Utility steps a through c, below) or by manually setting the registry keys (see Manually editing the registry, below).
5. Using the utility:
  1. Install the Windows support tool, "SUPTOOLS.MSI" from your Windows installation CD. Navigate to the <CD-ROOT>\SUPPORT\TOOLS\ directory.
  2. Run the Command Prompt: Start, All Programs, Windows Support Tools, Command Prompt.
  3. Type the following in the open Command Prompt window:
  4. Navigate to step 3.
6. Edit the registry manually:
7. Create a Multi-String value named "DependOnService" under each of the following keys and set its value to your SQL service name (see step 1).
8. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CASDBEngine
9. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CASMgmtSvc
10. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CASUniversalAgent
11. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CASTapeEngine
12. Reboot the computer.

To avoid problems expanding the Microsoft Network in Arcserve Backup Manager on Windows Server 2008 machines, ensure Computer Browser service is enabled and started. This service is disabled on Windows Server 2008 systems by default.
When you install this release of Arcserve Backup on the cluster node of a Windows Server 2008 cluster or a Windows Server 2012 cluster, the Arcserve Backup Database is listed in the cluster virtual name on the Backup Manager.
When default collation is selected from Language Support Options, look in directory field on the Restore by Query screen is Kana-insensitive, Width-insensitive and Case-insensitive. When Japanese collation is selected, operations are Kana-sensitive, Width-sensitive and Case-sensitive. For the Look in Directory field on the Restore by Query screen, and the Volume field on the Search dialog, you may specify only uppercase drive letters.
Security information for the Agent for Microsoft SQL is not automatically loaded after upgrading from earlier Arcserve Backup versions to this release. You must retype password to continue.
Arcserve Backup does not support integration with the Microsoft Management Console.
If the Arcserve Backup database is configured to use SQL Server, the Database Protection Job may not be able to successfully backup the Arcserve Backup database in a clustered environment when failover happens from one node to another node. If such a situation occurs, run the Database Protection Job again manually to verify the Arcserve Backup database is being successfully backed up.
When performing a full node backup, you may skip the system state by adding the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\ClientAgent\Parameters
Value Name: SkipSystemStateBkup
Data Type: REG_DWORD
Value: 1
For 32-bit OS, local backup jobs, add the key here:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\Base\Task\Backup
Value Name: SkipSystemStateBkup
Data Type: REG_DWORD
Value: 1
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe Backup\Base\Task\Backup
Value Name: SkipSubmitDetailEX
Data Type: REG_DWORD
Value: 1
Microsoft does not recommend backing up symbolic links on Windows Vista, Windows Server 2008, Windows Server 2008 R2, and Windows 7 systems. This approach is not recommended because the default locations for user data and system data (for example, the Documents and Settings folder) are different than that of previous Windows operating systems. As a best practice, you should backup the folders that are referenced by the symbolic link, rather than the link itself.
When restoring Hyper-V virtual machines to an alternate location, Arcserve Backup may not be able to power on the target if the CD/DVD name is not the same as that of the original backup. To resolve this problem, verify that the CD/DVD name of the destination is the same as the source location before you submit the restore. An alternate solution is to edit VM settings after restore is complete and change the CD/DVD location to one available on the destination Server.
When restoring Hyper-V virtual machines to an alternate location, Arcserve Backup may not be able to power on the target if the friendly name of the network switch is not the same as that of the original backup. To resolve this problem, verify that the friendly name of the network switch of the destination is the same as the source location before you submit the restore. An alternate solution is to edit VM settings after restore is complete and change the network switch name to one available on the destination Server.
When you submit backup jobs to removable media such as RDX, avoid setting both Eject Media and Export Options. Export options override the Eject Media options but because this device does not support exporting, the device is not ejected upon job completion.
In Job History, no device/media information is provided for sessions backed up to a RAID group because a RAID group typically contains multiple devices, yet appears as a single device to the application.
When saving a Data Mover backup job script from the Backup Manager console, the Data Mover's source, destination, and global options checks are not executed. Therefore, the GUI will not show any messages to warn the user or block the user from submitting the job and removing the unsupported options. If you reload the saved job script from the Job Status Manager, the job fails.
Select one of the following options as a workaround:

From the Backup Manager console, click the Submit button to submit your job. The Security and Agent dialog opens. Click OK and the Submit Job dialog opens. Click the Save Job button to save the job script.
If you select the Save or Save As menu to save the job script, you can reload the job and modify this job in the Job Status Manager, and then re-submit the job. All checks will then be executed.
If you select the Save or Save As menu to save the job script, you can click the Open menu from the Backup Manager console to open the job script and then click the Submit button to submit the job. All checks will then be executed.

Arcserve Backup supports only one writer (e.g., Oracle, MSDE) as a source disk in one backup job through Transportable Shadow Copies, i.e., HDVSS. If you include other types of source disks to this one backup job, the job fails.
When you select Add Agent/Import/Export menu from Arcserve Backup to register a server that has multi IP addresses, Arcserve Backup Group View will only recognize the first IP address. Arcserve Backup Group View will not be able to change an IP address after a node is registered. In the case of Classic View, you can change it by selecting Agent Modification from the Context menu.
The Job Status Manager cannot display Activity Log data for data mover Servers when the Group by Job option on the Activity Log tab is specified.
Important! This behavior occurs only when jobs are submitted using UNIX/Linux Data Mover backup on the Backup Manager Start tab.
If the Arcserve Backup uses SQL Server as its database and the SQL instance name is "ARCSERVE_DB", use ca_recoverdb.exe to recover your Arcserve Backup database, instead of Database Recovery wizard.
When adding a cloud connection from the Device Manager and you enter the domain password and proxy credentials, the system caches the credentials. If you add another connection and specify incorrect domain password and proxy credentials or leave it blank, the system picks up the cached credentials and successfully adds the cloud connection.
As a workaround, you can delete the cookies from the computer you are working from or reboot. This will cancel out the cached credentials.
After migration job completes for a disk staging job, the restore by session method searches for the specific file in two sessions (staging session and migration session), while the restore by query method searches the file in only one session (staging session or migration session, not both).
Note: Creating a vault after migration completes specifies the requested file in only one session (staging session or migration session, not both) which places only one tape into the vault.
If your computer credentials have changed, you cannot open the Copy, Purge, or Count Utilities from Arcserve Backup Manager. Due to Windows restriction, if you use an existing user name to create a connection to a shared resource, then any other user name fails to create the connection to the same resource.
When you submit a staging job with FSD as the staging location and Cloud Device as its destination, the migration job does not resume after an unplanned cluster failover occurs as the tape engine needs time to initialize the cloud device.
As a workaround, Arcserve Backup creates a makeup job for the failed migration job to continue the migration process.
For the reason that Windows cannot access binary files after a failover on a cluster environment due to the back-end process of a failed caauthd.exe file, you will not be able to log into Arcserve Backup with a valid user name and password.
As a workaround, restart the Arcserve Backup Domain Server Service.
To recover data from backup sessions that were migrated to Eucalyptus Cloud devices using a prerelease version of Arcserve Backup r16, add the following property to the CCIConfig initialization file.
File location:
<BAB_HOME>\CCI\Config\CCIConfig.ini

Property:

[Eucalyptus_Config]
UseOldDecode=1
Note: Set the value of the UseOldDecode property to 0 to use the new devices. By default, the UseOldDecode property is not present in the CCIConfig initialization file. The default value of UseOldDecode is 0.
Backward Compatibility is not supported for proxy Servers and agents running on virtual machines with different versions of Arcserve Backup.
Thin Provisioning in the Windows 8 and Windows Server 2012 operating system requires you to have the physical disk space equivalent to the size of the volume that is being backed up for Raw Volume/Disk restores.
To browse and backup drives that are protected by BitLocker Drive Encryption, log in to the operating system to unlock the volume before you submit the backup job. With BitLocker Drive Encryption, the Backup Manager cannot display the individual directories and files contained in the drive, which prevents you from submitting backups. This behavior also applies to the process of restoring data to BitLocker protected drives: Log in to the operating system to unlock the volume before you submit the restore job.
When you backup optimized NTFS Deduplication Volumes, the Job Monitor displays false results. This behavior occurs because Arcserve Backup calculates the logical sizes rather than the physical sizes of the files from the Job Monitor. You can find the accurate data at the end of the job in the activity log.
On Windows Server 2008 R2 or Windows Server 2008 R2 SP1 systems, Hyper-V VSS writer backups can fail when the state of Cluster Shared Volumes is set to the Redirected mode. To correct this behavior, install Windows Server hotfix 2674551. With the hotfix applied to the server, you can set the state to online and Hyper-V VSS Writer backup jobs will complete successfully.
When you restore physical disk/volume backup sessions of a specific sector size (4k) to another physical disk/volume of a different sector size (512 bytes) the restore job fails because the geometry of disk devices and media in the backup session does not match the destination device where the files and folders are being restored to.
Scan backup media contents and compare backup media contents to disk are not supported for Raw backups.
After restoring NTFS Deduplication optimized sessions, the quantity of bytes restored to the disk are not the actual size of the file that were restored. This behavior occurs when the data for the user files are spread across multiple NTFS Deduplication metadata files.
Due to a known SQL Server Management Studio 2012 SP1 issue; when you first install Arcserve Backup or upgrade to the latest release using Setup, Silent, Agent Deployment, or Remote installation; uninstalling the application may fail when SQL Server Management Studio 2012 SP1 is installed on the target machine. For more information, see Article 770630 on the Microsoft website.
To correct this behavior, uninstall the Management Tools feature for both Basic and Complete versions only if the article specified in the link applies to you.
When you submit backups for Arcserve D2D nodes with the (global backup) Compare backup media to disk option specified, the job completes successfully, however, the job status displays failed and the following message appears in the Activity Log:
The Client Agent does not support comparing Arcserve D2D sessions.
Note: The Compare option is not supported for Arcserve D2D sessions.
The Arcserve Backup installation screens may stop responding when the installation media (ISO image or DVD) is mounted on a remote location. When you encounter this behavior, mount the installation media on a local location.
While backup jobs of virtual machines are running from backup Servers running Windows Server 2012, the status for all virtual machines always appears as Backing Up. This behavior occurs only when you perform full node backups of Hyper-V Servers using the Client Agent for Windows, or using the Hyper-V VSS writer to backup the virtual machines. In addition, you cannot perform various tasks on the virtual machines such as power on, power off, save, pause, reset, rename, and enable replication.
When using tapecopy to copy the sessions from a source tape to a destination tape where the destination tape is a blank media, use the -idr parameter to generate a new random ID on the destination tape to avoid any errors during spanning of tapes. For more details, see the related Arcserve Backup KB article.
When installing Arcserve Backup for the first time on a Windows Server 2012 R2 machine, whether it is a local or remote installation, a delay in warning messages for the Configuration process occurs. It is recommended to wait for these messages to appear before canceling the install. In the meantime, we are working to resolve this problem.
Arcserve Backup does not support multi-byte characters and unicode characters when specifying the Duplicate Media Prefix in the Backup Manager Destination tab.
Microsoft Windows 10 Edge browser is not supported to view Arcserve Backup reports.

Compression ratio display fails when you use software compression at local option.
Arcserve Backup does not support backup for Posix TAR and Posix CPIO media formats.
For more information, refer to link.
The restore manager options Restore by Tree and Restore by Session do not display any folders or files for huge amount of files and/or directories when backup or merge job is completed without any error in the log files. The problem happens due to the limitation of the catalog merge utility mergecat.exe. As a workaround, use one of the following options to restore from the backup media.
- Use Restore by Media with the Filter feature to specify what to restore.
- Use the ca_restore.exe command line utility with "source" option to specify what to restore.
Windows Defender (Windows Server 2019 / Windows Server 2016) causes system drive and system state restore failures.
Restore of system volume (C:/) to original location finishes with incomplete status and generates errors: AE0066 and AE0070.
Symptom
Windows Defender protects the system files and directories. As the restore option doesn't have access to overwrite the files, an error occurs while restoring system files and directories.

Solution
Turn off Windows Defender using Group Policy Editor on the Windows Server 2019 / Windows Server 2016 before you start the system restore.

To open the Local Group Policy Editor, go to Start and search for gpedit.msc.
Navigate to the folder: Computer Configuration > Administrative Templates > Windows Components > Windows Defender Antivirus.
On the right pane, select and double-click the Turn off Windows Defender Antivirus option.
Click Enabled, and then click OK.
Close the Local Group Policy Editor, and run the group policy update command (gpupdate/force).