{"id":11297,"date":"2025-11-25T01:02:16","date_gmt":"2025-11-25T00:02:16","guid":{"rendered":"https:\/\/archivista.ch\/cms\/?page_id=11297"},"modified":"2026-02-28T10:45:38","modified_gmt":"2026-02-28T09:45:38","slug":"archivistavm-2025-xi","status":"publish","type":"page","link":"https:\/\/archivista.ch\/cms\/en\/news\/year-2025\/archivistavm-2025-xi\/","title":{"rendered":"ArchivistaVM 2025\/XI"},"content":{"rendered":"

Windows 11 made simple and easy<\/h1>\n

Egg, November 24, 2025:<\/strong> Many of our customers have migrated from Windows 10 to Windows 11 in recent months. Nothing will change for customers of ArchivistaDMS and\/or ArchivistaERP. The use of the web browser remains the same under Windows 11 as under Windows 10. Only customers who use ArchivistaVM, our virtualization platform, will find an upgrade with ArchivistaVM 2025\/XI to set up and maintain Windows 11 instances more easily.<\/em><\/p>\n

\"\"<\/a><\/p>\n

Virtualization is and remains virtualization<\/h2>\n

First things first: Windows 11 can also be installed on an older version of the ArchivistaBox without any problems. In this sense, the update is not absolutely necessary. However, some things are handled a little differently in Windows 11, which is why the update and the assistance provided in this article make sense.<\/p>\n

First of all, there is the \u201csystem requirement\u201d that Windows 11 itself requires Trusted Platform Manager 2.0 and also requires SecureBoot without \u201cassistance.\u201d Both points are more pointless than helpful in virtual environments.<\/p>\n

The advantage of virtualization lies precisely in the fact that virtual instances can be easily migrated from hardware A) to B). However, the purpose (to put it optimistically) of SecureBoot and TPM 2.0 is for Windows to meticulously check that no changes are made to the hardware.<\/p>\n

In principle, both TPM 2.0 and SecureBoot (including encryption with BitLocker) can be used with KVM (or ArchivistaVM), but this is not recommended. Instances created in this way can either not be \u201cmoved\u201d to new hardware or software during virtualization at all, or only with increased effort.<\/p>\n

Installing Windows 11 with bypass.iso<\/p>\n

However, it is possible to install Windows 11 without these \u201cfeatures\u201d by changing a few entries in the registry (system settings) during installation. These commands are somewhat cryptic. The easiest way to execute these commands is to use a good old batch file. This can be downloaded (zipped here).<\/a><\/strong> Unzip the \u2018bypass.zip\u2019 file and upload it to the ISO files via ArchivistaVM. The Windows installation ISO should be in first place, followed by bypass.iso.<\/p>\n

After starting Windows 11, press Shift+F10<\/strong> to open the console. Then enter \u2018d:\u2019<\/strong> and then \u2018setup.bat\u2019.<\/strong> This activates the necessary registry entries. The installation can then proceed without any problems. For those who want to know what setup.bat does, here is a copy:<\/p>\n

@echo off<\/strong>\r\ntitle \ufe0f Bypass Windows 11 Requirements - Safe Registry Tweaks<\/strong>\r\ncolor 0A<\/strong>\r\n\r\necho ====================================================<\/strong>\r\necho Windows 11 Bypass Script (TPM, RAM, Secure Boot)<\/strong>\r\necho ====================================================<\/strong>\r\necho.<\/strong>\r\n\r\necho \u27a4 Adding Registry keys to skip hardware checks...<\/strong>\r\n\r\nreg add \"HKLM\\SYSTEM\\Setup\\LabConfig\" \/v BypassTPMCheck \/t REG_DWORD \/d 1 \/f<\/strong>\r\nreg add \"HKLM\\SYSTEM\\Setup\\LabConfig\" \/v BypassSecureBootCheck \/t REG_DWORD \/d 1 \/f<\/strong>\r\nreg add \"HKLM\\SYSTEM\\Setup\\LabConfig\" \/v BypassRAMCheck \/t REG_DWORD \/d 1 \/f<\/strong>\r\nreg add \"HKLM\\SYSTEM\\Setup\\LabConfig\" \/v BypassCPUCheck \/t REG_DWORD \/d 1 \/f<\/strong>\r\nreg add \"HKLM\\SYSTEM\\Setup\\LabConfig\" \/v BypassStorageCheck \/t REG_DWORD \/d 1 \/f<\/strong>\r\n\r\necho.<\/strong>\r\necho \u2705 Success: Windows 11 setup bypasses applied.<\/strong>\r\npause<\/strong><\/pre>\n
Of course, the individual entries could also be entered on the command line, but this is cumbersome; \u2018setup.bat\u2019 is much easier. At the end of the installation, the usual points should be cleaned up (e.g., disable indexing on drives, etc.).<\/p>\n
CPU optimizations<\/h2>\n
Unfortunately, Windows 11 may sometimes fail to start during installation or migration (to another VM environment or from a physical machine). In this case, the CPU can be optimized by selecting the \u2018Options\u2019 tab for the relevant instance and then selecting the \u2018Options\u2019 field:<\/p>\n
-cpu host,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time<\/strong><\/pre>\n
‚-cpu host‘ ensures that the native CPU of the physical computer is used. The other parameters are not strictly necessary, but can help to synchronize the time between the native computer and the Windows 11 guest.<\/p>\n
\"\"<\/a><\/p>\n
Optimize hard disk drivers<\/h1>\n
ArchivistaVM runs on KVM. With conventional IDE drivers, the hard disks can only be accessed at a \u201cfairly\u201d slow speed (approx. 70 MB\/second). The Virtio drivers offer significantly more speed. These can be downloaded as an ISO file from this link.<\/a><\/strong><\/p>\n
Note:<\/strong> In principle, the Virtio drivers could also be activated during installation. However, since the corresponding entry is well hidden, it may be easier to perform the installation yourself with IDE hard disks and only activate the Virtio drivers afterwards.<\/em><\/p>\n
To \u201cmigrate\u201d from the classic IDE drivers to Virtio, the following steps are necessary.<\/p>\n
    \n
  1. Mount the Virtio driver ISO file via the CD drive (for hardware).<\/li>\n
  2. Add an empty Virtio hard disk for hardware. Important: Windows only activates the Virtio drivers if at least one Virtio disk is present.<\/strong><\/li>\n
  3. Start Windows 11.<\/li>\n
  4. Start the setup program for the Virtio drivers in Windows 11.<\/li>\n
  5. Shut down Windows 11.<\/li>\n
  6. Remove the empty Virtio hard disk from the instance. Important: The next step only works if there are no Virtio disks.<\/strong><\/li>\n
  7. Convert the original hard disk(s) from IDE to Virtio. To do this, click the button on the left and then on the entry \u2018IDE=>Virtio\u2019 for hardware and an IDE disk. The format is then changed from IDE to Virtio in the configuration file.<\/li>\n
  8. Start Windows 11; the Virtio drivers will be activated automatically.<\/li>\n<\/ol>\n
    ArchivistaVM 2025\/XI (or later) is required for step 7. In earlier versions, the entries in the conf file (\/etc\/qemu-server\/xxx.conf) would have to be changed manually from \u2018ide\u2019 to \u2018virtio\u2019.<\/p>\n
    Note: Virtio<\/strong> drivers are also available for network cards. To make the change here, the current Mac address can be copied to the clipboard in Hardware (with the instance switched off!). Then delete the network card (usually e1000) and recreate it as a \u2018virtio\u2019 card (pasting the old Mac address is highly recommended, but not mandatory).<\/em><\/p>\n
    Shutting down machines \u201chard\u201d<\/h2>\n
    Daily practice has shown that under certain circumstances, Windows 11 cannot currently be shut down using \u201cShut Down\u201d and sometimes not even using \u201cStop.\u201d Although such problems can usually be solved by making appropriate changes in the registry (keyword ACPI), the \u201cKill\u201d button is now available as of version 2025\/XI. This allows instances (with all consequences) to be terminated definitively via the job number.<\/p>\n
    Note: If not all content has been saved to the hard disk when \u2018Kill\u2019 is executed, this data will be lost. Terminating an instance with \u2018Kill\u2019 is therefore at your own risk.<\/p>\n
    UEFI directly in the setup<\/h2>\n
    Previously, UEFI had to be activated manually via the \u2018Options\u2019 tab and the \u2018Options\u2019 field. New in version 2025\/XI, the \u2018UEFI\u2019 option is now available for this purpose. UEFI can either be activated directly when creating an instance, or the option can be activated or deactivated in the \u2018Options\u2019 tab under \u2018UEFI\u2019.<\/p>\n
    \"\"<\/a><\/p>\n
    Setting optional parameters (e.g., keyboard)<\/h2>\n
    In ArchivistaVM, it has always been possible to set optional parameters via the \u201cOptions\u201d tab and the \u201cOptions\u201d field. The procedure for addressing a specific CPU has already been described above. However, all KVM\/Qemu commands can be stored in this field.<\/p>\n
    An example of this is setting a specific keyboard. For example, \u2018-k de\u2019 activates a German keyboard, while \u2018-k de-ch\u2019 activates a Swiss keyboard. If you want to use a French keyboard, you can do so with \u2018-k fr\u2019.<\/p>\n
    Command line with qm<\/h2>\n
    The entire KVM interface of ArchivistaVM can also be used via the terminal. \u2018qm list\u2019 can be used to request a list of all instances. \u2018qm start xxx\u2019 can be used to start the instance \u2018xxx\u2019, while \u2018qm stop xxx\u2019 immediately shuts down the machine. The complete list of all commands can be requested with \u2018qm help\u2019.<\/p>\n
    ArchivistaVM 2025\/XI: Simple and easy<\/h2>\n
    With the new version of ArchivistaVM, virtualization is even easier than it already was. ArchivistaVM is available on every ArchivistaBox.<\/p>\n\n\n\n\t
    \n\n\t\t<\/i><\/span> PDF Button<\/a>\n\n\t<\/div>\n\n\n\n\n\n","protected":false},"excerpt":{"rendered":"
    Windows 11 made simple and easy Egg, November 24, 2025: Many of our customers have migrated from Windows 10 to Windows 11 in recent months. Nothing will change for customers of ArchivistaDMS and\/or ArchivistaERP. The use of the web browser remains the same under Windows 11 as under Windows 10. Only customers who use ArchivistaVM, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":11366,"menu_order":21,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"class_list":["post-11297","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/archivista.ch\/cms\/wp-json\/wp\/v2\/pages\/11297","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archivista.ch\/cms\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/archivista.ch\/cms\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/archivista.ch\/cms\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/archivista.ch\/cms\/wp-json\/wp\/v2\/comments?post=11297"}],"version-history":[{"count":1,"href":"https:\/\/archivista.ch\/cms\/wp-json\/wp\/v2\/pages\/11297\/revisions"}],"predecessor-version":[{"id":11298,"href":"https:\/\/archivista.ch\/cms\/wp-json\/wp\/v2\/pages\/11297\/revisions\/11298"}],"up":[{"embeddable":true,"href":"https:\/\/archivista.ch\/cms\/wp-json\/wp\/v2\/pages\/11366"}],"wp:attachment":[{"href":"https:\/\/archivista.ch\/cms\/wp-json\/wp\/v2\/media?parent=11297"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}