issue with Export-VBRAudit for dates after 31-dec-2025

[AlexL]

Export-VBRAudit does not give all results as expected. See the example and error below:

Export-VBRAudit -From 1-jan-2026 -To 31-jan-2026 -FileFullPath c:\temp\audit.csv

Export-VBRAudit : Cannot validate argument on parameter 'From'. Specify DateTime prior to 31-12-2025 00:00:00
At line:1 char:23
+ Export-VBRAudit -From 1-jan-2026 -To 31-jan-2026 -FileFullPath c:\tem ...
+ ~~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [Export-VBRAudit], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationError,Veeam.Backup.PowerShell.Cmdlets.ExportVBRAudit

This seems to be a bug (using 12.3.2.4165).

[david.domask]

Hi Alex,

It's indeed a known issue (affects v13.0.1 P1 and earlier as well).

We will fix it in an upcoming release.

[AlexL]

this helps a little, for now: post420371.html#p420371

[sdv]

Latest release 12.3.2.4854 in June 2026 | Does not tell it is fixed in the release notes.
https://www.veeam.com/kb4869

And the later builds of V13 (13.0.2.29 - May 2026) is not mentioning the fix in the change logs either.
https://www.veeam.com/kb4738

This functionality already broke in (at least) build: 12.3.2.3617 (June 2025).

Its interesting that this functionality has been broken for over a year while security itself is high on the calendar of many organizations.

@Veeam, can anyone confirm which build it will be fixed?

[david.domask]

Hi sdv,

The fix was marked as implemented in 13.0.1.2067, so if you're on 13.0.2 it should be fixed.

[AlexL]

Just tried it on a Windows installation of v13.0.2.29, now I don't get a date error but some sort of permissions error?!?
That was while "running as administrator".

Export-VBRAudit -From 1-jan-2026 -To 31-jan-2026 -FileFullPath c:\temp\audit.csv
Export-VBRAudit: Failed to get write access to C:\ProgramData\Veeam\Backup\Audit\audit_586d76de-90b0-4a74-bedb-84ea9b5de23c.csv: Write access to the file system is not allowed on the Veeam Software Appliance

[david.domask]

Hi AlexL,

Tested and got same issue as well, looks like while the date issue was fixed, but there is a new issue related to VSA security settings here :/

We already have an issue filed & resolved in 13.1 (just tested successfully on beta)

Very sorry for the continuous issues here, but it works as expected in 13.1, which we expect soon (within weeks)