Important Update: Cohesity Products Documentation
All Cohesity product documentation are now managed via the Cohesity Docs Portal: https://docs.cohesity.com/HomePage/Content/home.htm. Some documentation available here may not reflect the latest information or may no longer be accessible.
NetBackup™ Release Notes
- About NetBackup 11.1.0.2
- New features, enhancements, and changes
- About new enhancements and changes in NetBackup
- NetBackup 11.1.0.2 new features, changes, and enhancements
- Changes in Cohesity terminology
- Update cloud configuration file on the primary and media server immediately after install or upgrade to NetBackup 11.1.0.2
- Several shutdown commands to be deprecated in a future release
- NetBackup 11.1.0.2 support additions and changes
- NetBackup 11.1 and earlier support additions and changes
- Support for malware scanning of hypervisor backups on OST targets
- Simplified Cloud Scale upgrade
- BMR now uses Windows ADK 10.1.22621 (ADK 2022)
- Operational notes
- About NetBackup 11.1.0.2 operational notes
- NetBackup installation and upgrade operational notes
- If NetBackup 11.1.0.2 upgrade fails on Windows, revert to previous log folder structure
- Native installation requirements
- NetBackup servers must use a host name that is compliant with RFC 1123 and RFC 952
- About support for HP-UX Itanium vPars SRP containers
- Change in the default path for NetBackup installation
- NetBackup administration interface operational notes
- NetBackup Bare Metal Restore operational notes
- After PIT restore, "The host ID does not exist" error appears
- NetBackup services may not start automatically after BMR restore on a Linux client
- NetBackup Bare Metal Restore on AWS hangs when restoring a Windows 2025 client
- Mirrored dynamic volume may not receive a drive letter after Windows BMR DDR restore
- BMR Restore Failure for ReFS Volumes on Windows (2016 - 2025)
- Post Bare Metal Restore (BMR) operation, windows Start Menu and Search not functioning
- NetBackup Cloud Object Store Workload operational notes
- Full backup after upgrading from a version prior to NetBackup 11.1
- Supported version of RHEL media server as backup host
- Auto Image Replication (AIR) from NetBackup version 11.1.0.2 requires NetBackup 10.2 or later
- Backup jobs become unresponsive and consume significant space on the temporary staging location.
- NetBackup NAS operational notes
- NetBackup Cloud workload operational notes
- NetBackup internationalization and localization operational notes
- Appendix A. About SORT for NetBackup Users
- Appendix B. NetBackup installation requirements
- Appendix C. NetBackup compatibility requirements
- Appendix D. Other NetBackup documentation and related documents
Post Bare Metal Restore (BMR) operation, windows Start Menu and Search not functioning
Post Bare Metal Restore (BMR) operation, windows Start Menu and Search not functioning.
This behavior has been observed on the Windows Server 2019 (2K19) EFI client.
The most probable cause is that the AppX State Repository database was not properly updated during the recovery process.
While application files were successfully restored, the system's internal registration database was not synchronized, leading to failures in initializing built-in Windows components.
Follow the Microsoft's documentation and recommendations for registering the Appx Package.
Apart from official documentation, the following procedure may assist in resolving registration-related inconsistencies.
Recovery Procedure
- Open PowerShell as an administrator.
- Run the following command:
Get-AppXPackage -AllUsers | Foreach { Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" }This command re-registers all installed AppX packages by reading their respective
AppXManifest.xmlfiles and rebuilding the associated registration data
Executing this command performs the following actions:
Enumerates all installed AppX packages across all user profiles
Parses each
AppXManifest.xmlRebuilds package activation and identity mappings
Re-indexes packages in the Windows State Repository
Re-applies required security identifiers (including ALL APPLICATION PACKAGES)
Reconstructs AppX deployment metadata
This process helps resolve AppX package registration mismatches and related shell initialization issues.
After completing the re-registration:
Restart the Windows Shell by restarting the
explorer.exeprocess to ensure the updated registrations are applied.
Before performing AppX package re-registration, verify the following:
AppLocker Configuration
Ensure no AppLocker Deny rules are blocking packaged applications.
Open secpol.msc and navigate to: Application Control Policies → AppLocker
Confirm that no rules deny execution of Packaged Apps.
Required Directories
Ensure the following directories exist:
C:\Windows\System32\AppLocker
C:\Windows\AUInstallAgent
If missing, create them.
Do not delete these directories if they already exist.
AppReadiness Directory
Verify that
C:\Windows\AppReadinessexists.If missing, create the directory.
This location is required for AppX staging operations.
Registry Validation
Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx
Confirm that the PackageRoot registry value points to:C:\Program Files\WindowsApps
Optional Service Restart
If required, restart the AppX deployment service before or after package re-registration:
Restart-Service AppXSVC -Force
0x80073CF9 (Install Failed): Officially defined as "The package deployment failed because the staging operation could not be completed.".
In a BMR Scenario:
This typically indicates that:
The Staging Operation is the process where Windows prepares the application before committing it to the State Repository.
The AppReadiness directory is missing
The AUInstallAgent staging directory is missing
Directory permissions are incorrect
0x80070003 (Path Not Found): Officially refers to a "Deployment Target Access failure."
In a BMR Scenario:
This confirms that: may be missing or inaccessible due to stripped or incorrect SIDs.
This indicates that the database contains registration references, but the physical directory structure is either missing or inaccessible.
The AppX database cannot locate the required directory structure
C:\Windows\SystemApps or
C:\Program Files\WindowsApps