Windows 11 24H2 officially supported?

[GLM]

Hi all,

When using Backup and Replication 12 (12.2.0.334) to backup a VM Microsoft Windows 11 Pro 24H2 (10.0.26100.1742) the following message is logged:

"Warning Microsoft Windows version installed on this machine is not officially supported by Veeam yet."

The backup completed succesfully.

Can someone confirm that 24H2 is not officially supported? .

Thank you.
Regards.

[Gostev]

Hi, confirming as it has just been released, literally a few days ago. Thanks

[travuse]

SAME with this
https://helpcenter.veeam.com/docs/agent ... tml?ver=60
Standalone Veeam Agent
Version: 6.2.0.121
Size: 166 MB
Microsoft Windows 11 (from version 21H2 to version 23H2)

When Will Veeam be supported for Windows 11 24H2?

[Gostev]

We'll know once we perform full regression testing cycle and understand breaking changes etc.
As always, our target for new OS/platform/application version support is 90 days.

[zaim]

I'm running VBR 12.1 on a Windows 11 host and did an update today to 24H2. Now I tried to upgrade to 12.2 but I get an error while upgrading in step 1 of 7: "VmaStopDrivers" from a MSI installer. What I could read from the logs that it has something to do with the SQL Instance and it fails with error 1603. Any ideas? I'm planing to move to postgre anyway but wanted to inform about this issue

[doktornotor]

24H2 is supported with 12.3, but for some reason VBR does not recognize IoT Enterterprise LTSC 2024. @Gostev

Code: Select all

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
    SystemRoot    REG_SZ    C:\WINDOWS
    BaseBuildRevisionNumber    REG_DWORD    0x1
    BuildBranch    REG_SZ    ge_release
    BuildGUID    REG_SZ    ffffffff-ffff-ffff-ffff-ffffffffffff
    BuildLab    REG_SZ    26100.ge_release.240331-1435
    BuildLabEx    REG_SZ    26100.1.amd64fre.ge_release.240331-1435
    CompositionEditionID    REG_SZ    EnterpriseS
    CurrentBuild    REG_SZ    26100
    CurrentBuildNumber    REG_SZ    26100
    CurrentMajorVersionNumber    REG_DWORD    0xa
    CurrentMinorVersionNumber    REG_DWORD    0x0
    CurrentType    REG_SZ    Multiprocessor Free
    CurrentVersion    REG_SZ    6.3
    DisplayVersion    REG_SZ    24H2
    EditionID    REG_SZ    IoTEnterpriseS
    EditionSubManufacturer    REG_SZ
    EditionSubstring    REG_SZ
    EditionSubVersion    REG_SZ
    InstallationType    REG_SZ    Client
    InstallDate    REG_DWORD    0x6795708e
    LCUVer    REG_SZ    10.0.26100.2894
    ProductName    REG_SZ    Windows 10 IoT Enterprise LTSC 2024
    ReleaseId    REG_SZ    2009
    SoftwareType    REG_SZ    System
    UBR    REG_DWORD    0xb4e
    PathName    REG_SZ    C:\Windows
    PendingInstall    REG_DWORD    0x0
    ProductId    REG_SZ    00484-40000-00001-AA446

Enterprise 24H2 / LTSC 2024 is recognized just fine. Perhaps noone really uses these weird editions?

[Gostev]

It's a fair assumption, perhaps we just don't have one in our QA labs currently.

[doktornotor]

For a quick test, you can switch between LTSC and IoT LTSC with just slmgr /ipk using the GVLK keys published by MS, not even a reboot required. They are really the same, just different licensing (plus the setup does not annoy people with requirements like TPM 2.0).