Incompatibility with Windows 10 19043 (21H1)

[TheMMC]

Hi there,
yesterday I upgraded to B&R v11 and Agent v5 and it just stopped working.
I'm using the release-preview/beta channel for my Windows 10 so I am already on 21H1 build 19043.844. Server-managed Veeam Agent v4 recognized that as 20H2 and just worked. 20H2 to 21H1 is a minor update via an "enablement package" (build 19042 to 19043) without major changes to Windows itself and, while not officially supported, Veeam operated without any problems.
With B&R v11 I just get the "host OS not supported"-error while deploying/configuring the agent. Using the agent in standalone mode (without the B&R server) on 21H1 seems to be fine though.
Is there a workaround for this? I know 21H1 isn't officially supported yet, but I already upgraded some of my machines to 21H1 because, you know, I tested everything including doing backups with veeam.
So basically B&R v10 worked flawlessly and upgrading to v11 broke the backup functionality for half my network
Is there some way of testing v11 with 21H1 at my own risk?

[Dima P.]

Hello Ralf,

Can you please raise a support case and share the ID with me. Meanwhile I'll check with QA team. Thank you in advance!

[TheMMC]

I'll raise a support case as soon as I am back at the office, but that could take some days (I got to a minor injury and need some days off). I came across this issue at home while using the community edition. I always test new releases in my homelab before upgrading our installation at work.

[Dima P.]

Thank for quick update Ralf. We are investigating this issue from our side but will await for your case and debug logs as well. Cheers!

[Dima P.]

Hello Ralf,

Case is no longer required: we confirmed the issue our lab. Looks like due to the recent changes in MS build number our code that validates build versions is now misbehaving and as a result all inner circle beta builds are blocked for agent deployment.

We've concluded that even though the beta builds are not supported till go GA and are verified by our QA teams, we wont block the agent installation starting for the next update. Mind me asking if such approach is ok for you? Thank you in advance!

[TheMMC]

Hello Dima,
thanks for looking into that issue. I "fixed" my problem by just uninstalling the enablement package, it's just my homelab after all. We are not using windows-beta-updates in our production environment so I'll just wait for the next agent release.
Have a nice day

[TheMMC]

Just a quick heads-up:
https://techcommunity.microsoft.com/t5/ ... -p/2220577
"Windows 10, version 21H1, is now available for commercial customers to begin feature exploration and validation prior to being released for general availability."
Compatibility ist still broken, even with the 210401 patch for B&R. General availability is rumored to be this month, that could be a potential issue for everyone using the "unfiltered" Windows Update (not using WSUS or anything).

[Dima P.]

Hello Ralf,

Thank you for the heads up! We will have the fix to allow the component deployment to all new operating systems ready in the upcoming cumulative patch 2, the official support is planned for the next Veeam B&R update.

[gfox]

Hello,

Can you please provide an update? We just upgraded to 11 and now have a node that cannot be backed up.

[Dima P.]

Hello gfox,

No updates to share right now, but the plan remains the same.

[Gostev]

Can you please provide an update? We just upgraded to 11 and now have a node that cannot be backed up.

According to Google, Windows 10 21H1 will only be released in June... are you sure you have it already?

[TheMMC]

@Gostev
Better check directly at Microsoft and not at Tech Advisor
https://blogs.windows.com/windows-insid ... r-release/
19043.928 will be the "final" 21H1, insiders can download the ISOs right now:
https://www.microsoft.com/en-us/softwar ... previewiso
And 21H1 has been availabe for business evaluation since march:
https://techcommunity.microsoft.com/t5/ ... -p/2220577

Or you can upgrade your existing 20H2 with KB5000736, that's the 21h1-enablement-package.

All that's missing now is the deployment for the general public via Windows Update.

[Gostev]

Actually, believe or not but I did check at Microsoft first, but I could not find any definite information about either the general availability date or the GA build number. Which is exactly why I resorted to Googling. Do you have a better information than Tech Advisor? I only referenced them because Google could not find anything fresher that references GA date.

Likewise, I could not find any information on the official sign off of any particular build as the RTM build of Windows 10 21H1. Even in the first link you posted, which is barely 1 week old, they say they believe build 19043.928 will be final. Do you know if it was actually designated as the final/RTM build in the last few days, and if yes - can you send a link to the official statement by Microsoft? Because we need the official RTM build before we can start working on the official support.

[gfox]

KB5000736 is installing version 19043.928 via enablement package. Looking forward to the fix soon!

[ccsjnw]

I have paid support for Veeam and have opened a case (04788639) for this problem.

I'm trying to test my line of business applications for compatibility with a Windows 10 Enterprise with the 21H1 Enablement Package installed, and the inability to backup the affected computer with the Veeam Agent for Windows is a concern.

I was told by support that this needs to be handled via a 'feature enhancement request' which I didn't think was appropriate. The support case is still open without a resolution. A grubby workaround (registry hack etc.) would be perfectly acceptable whilst we wait for the next service update to the Veeam Agent for Windows It's only impacting one PC in the organisation, but it's an important PC.

Regards,
James.

[Dima P.]

Thanks for the feedback James! Placing a feature request is indeed not requited for new platform version support. We plan to add the official support for 21H1 in the immediate release vehicle, which is the next minor release (version 11a). The workaround will be provided as well with the immediate cumulative patch which we plan to ship in the next few days. Thanks!

[Dima P.]

Hi folks!

You can get the Veeam Backup & Replication 11 Cumulative Patch P20210507 now.

Various product functionality should no longer outright refuse to work with pre-release builds of Windows 10 21H1 and Windows Server 2022 builds and will instead attempt to process them using the existing logic created for previous OS versions. This change does not constitute the official support for these platforms, which is planned for version 11a.

[ccsjnw]

The Veeam v11 cumulative patch has resolved my issue, and I am now able to backup the affected computer running Windows 10 21H1.

[blaiseSA]

Thanks for your topic the problème is resolved !