Release notes for N2W v4.6.1 [June 2026]

Summary

This document introduces N2W fix patch version 4.6.1.
Patch upgrade is available from versions 4.6.0.

Patch upgrade is available from versions 4.6.x to version 4.6.1

Support article: Patch upgrade instructions

Patch File: N2W_Upgrade_4.6.0_to_4.6.1.patch

Should you require further assistance our Support Team is available to help.

Issues Fixed

N2W-29329 - Instance restore fails when the original Security Group was deleted.

N2W-29379 - Added ability to exclude specific regions from unprotected resource scan; Bahrain region excluded by default.

N2W-29265 - Monthly backup may not be correctly selected according to user specifications.

N2W-29272 - Retention settings for DR snapshots may not be honored if different from the original settings.

N2W-29074 - Intermittent error while reading data directly from snapshot during Copy to Repository.

N2W-29114 - Added option in General Settings → Capture Network Environments to configure how many days captured logs should be kept.

N2W-29281 - After a fresh CPM installation on Azure, when running ASAP on the CPMDATA policy, the backup may not start.

N2W-29258 - Azure Resource Control Operations report download stalls at 0 bytes.

N2W-29246 - Clicking the account link in Azure Security Principal page shows incorrect accounts

N2W-29282 - General Settings → Capture Network Environments tab not displayed after disabling AWS cloud on Azure CPM.

N2W-27777 - Azure DR prematurely marked as completed successfully while copies are still running.

N2W-29292 - DR of EKS workload to some new AWS regions failed.

N2W-27969 - During Azure tag scan, a false alert may be shown “Policy [policy] doesn't exist/attached to account [account]”.