.

KGRKJGETMRETU895U-589TY5MIGM5JGB5SDFESFREWTGR54TY

Server : Apache/2.4.58 (Win64) OpenSSL/3.1.3 PHP/8.2.12
System : Windows NT SERVER-PC 10.0 build 26200 (Windows 11) AMD64
User : ServerPC ( 0)
PHP Version : 8.2.12
Disable Function : NONE
Directory : C:/Windows/System32/en-US/

Upload File :

Current File : C:/Windows/System32/en-US/hvloader.dll.mui

MZ����@��� �!�L�!This program cannot be run in DOS mode.

$�X=��9S��9S��9S������9S���Q��9S�Rich�9S�PEL����!&L

p�@ dI8.rdata�@@.rsrcdI J@@���
lPP���$����8.rdata8.rdata$voltmdP�.rdata$zzzdbg �.rsrc$01� �H.rsrc$02 ��_,�x����
peE� l��<
�����(�@�X�p����� � � �� ���!4D��e��MUI���c{��ط�
"��w�SO�b�u�{Qxھ������MUIen-US#��

��� |""� $&D
(,�..�00�68,;A�PV|`a�"��(%���(���*���0��3�� 60087PPL7���7
��8���8'�'��8����<9�����<����(=!�!��=1�1�l>A�A��?�����@��$BLHypervisor successfully started.

LHypervisor scheduler type is %1.

�Hypervisor Eventlog for global system events could not be created!

�Hypervisor launch has been disabled through the hypervisorlaunchtype bcdedit setting.

hHypervisor fails to start ETW tracing session.

�Hypervisor launch failed; sleep and hibernate could not be disabled (status %1).

�Hypervisor launch failed; the hypervisor boot loader's internal logic failed (BalStatus %1, sub-status %2).

�Hypervisor launch failed; the hypervisor boot loader was unable to allocate sufficient resources to perform the launch.

Hypervisor launch failed; the hypervisor boot loader does not support the vendor of at least one of the processors in the system.

�Hyper-V launch failed; the system does not appear to have a sufficient level of ACPI support to launch the hypervisor.

<Hypervisor launch failed; at least one of the processors in the system does not appear to provide a virtualization platform supported by the hypervisor.

�Hyper-V launch failed; the image %1 could not be loaded (status %2).

�Hypervisor launch failed; the image %1 failed code integrity checks, and cannot be used.

�Hypervisor launch failed; the image %1 does not contain the image description datastructures, and cannot be used.

�Hyper-V launch failed; at least one of the processors in the system was unable to launch the hypervisor (status %1).

\Hypervisor launch failed; the hypervisor image is revision %1, but the currently installed virtualization software only supports launching revision %2 hypervisor images.

�Hypervisor launch failed; Either VMX not present or not enabled in BIOS.

�Hypervisor launch failed; Either SVM not present or not enabled in BIOS.

`Hypervisor launch failed; EL2 not present.

�Hypervisor launch failed; Either No Execute feature (NX) not present or not enabled in BIOS.

@Hypervisor launch failed; Processor does not support the minimum features required to run the hypervisor (MSR index %1, allowed bits %2, required bits %3).

THypervisor launch failed; Processor does not provide the features necessary to run the hypervisor (leaf %1, register %2: features needed %3, features supported %4).

�Hypervisor launch failed; Hypervisor image does not match the platform being run on.

�Hypervisor launch failed; Required firmware table not found.

�Hypervisor launch failed; Encountered invalid firmware information.

�Hypervisor launch failed; Second Level Address Translation is required to launch the hypervisor.

4Hypervisor launch failed; Secure Mode Extensions have been enabled by the BIOS. Please disable Secure Mode Extensions in the BIOS to launch Hyper-V.

�Hypervisor launch failed; Minimum CPUID leaves required by the hypervisor are not supported on the system.

�Hypervisor launch failed; The physical address limit supported has been exceeded.

0Hypervisor launch failed; The hypervisor was unable to initialize successfully (phase %1), and was not started. This initialization failure may be the result of a platform configuration or firmware issue. Contact your system vendor for more information or updated firmware.

�Hypervisor launch failed; Too many runtime services memory ranges described by firmware.

Hypervisor launch failed; Memory ranges validation failure (BalStatus: %1, BalInternalError: %2, Line: %3, MemoryRangesCount: %4).

�Hypervisor launch failed; The operating systems boot loader failed with error %1.

�Hypervisor launch failed; The operating system boot loader was unable to locate a required resource.

�Hypervisor launch failed; The operating system boot loader detected a persistent memory failure.

Hypervisor launch failed; The operating system boot loader was unable to allocate sufficient memory to complete the operation.

Hypervisor launch failed; The operating system boot loader was unable to allocate sufficient resources to complete the operation.

�Hypervisor launch failed; The operating system boot loader detected a memory map conflict.

�Hypervisor launch failed; the version of the microcode update dll does not match the current operating system.

�Hypervisor processor startup failed (APIC ID %1, status %2). Further processors in the system were not started.

�Hypervisor processor startup failed (APIC ID %1) due to CPUID feature validation error. Further processors in the system were not started. Leaf %2, register %3 feature mismatch: BSP has features %5; AP has features %4

|Hypervisor initialized I/O remapping.%n%nHardware present: %1%nHardware enabled: %2%nPolicy: %3%nEnabled features: %4%nInternal information: %5%nProblems: %6%nAdditional information: %7

�Hypervisor I/O remapping is forcibly enabled by policy (the hypervisoriommupolicy BCD option is set to enable). If the system exhibits instability or reduced performance, consider restoring the default policy.

�There is an I/O remapping problem with the sytem BIOS.%n%nProblems: %1

`The image %1 could not be read (status %2).

�The image %1 failed code integrity checks, and cannot be used.

�Hypervisor failed to properly synchronize TSC across logical processors (Max delta: %1, Min delta: %2).

�The hypervisor did not enable mitigations for side channel vulnerabilities for virtual machines because HyperThreading is enabled and the hypervisor core scheduler is not enabled. To enable mitigations for virtual machines, enable the core scheduler by running "bcdedit /set hypervisorschedulertype core" from an elevated command prompt and reboot.

�The queried interface version %1 is not supported (Min : %2, Max : %3).

TThe queried interface is incomplete.

pPartition persistence services will be unavailable.

�The configured Minroot settings are not compatible with the hypervisor core scheduler and have been overriden. This may expose a different number of logical processors to the root partition.

�Failed to unregister the remote hypercall interface (status %1).

(Hypervisor configured mitigations for CVE-2019-11091, CVE-2018-12126, CVE-2018-12127, CVE-2018-12130 for virtual machines.%n%nProcessor not affected: %1%nProcessor family not affected: %2%nProcessor supports microarchitectural buffer flush: %3%nBuffer flush needed: %4%n

�The hypervisor did not enable mitigations for side channel vulnerabilities for virtual machines because HyperThreading is enabled. To enable mitigations for virtual machines, disable HyperThreading.

�AMD PSP PCI device discovered. Segment: %1, bus: %2, device: %3, function: %4.

PSecure firmware update status: %1.

HSecure firmware image invalid.

DSecure firmware version: %1.

On the prior boot session, the root partition did not respond to the synthetic watchdog in time, triggering a hardware watchdog reboot.

Info

Error

Warning

Information

TMicrosoft-Windows-Hyper-V-Hypervisor

System

THypervisor Eventlog creation failed!

THypervisor Eventlog deletion failed!

LHypervisor Eventlog flush failed!

DHypervisor Load Options - %1.

�Host processor features mask: %1%n%nHost xsave features mask: %2%n%nHost cache line flush size: %3 bytes

�Hypervisor configured mitigations for CVE-2018-3646 for virtual machines.%n%nProcessor not affected: %1%nProcessor family not affected: %2%nProcessor supports cache flush: %3%nHyperThreading enabled: %4%nParent hypervisor applies mitigations: %5%nMitigations disabled by bcdedit: %6%nMitigations enabled: %7%nCache flush needed: %8%n

lHypervisor Load Options are conflicting - %1, %2.

�Features are enabled that require all processors be started. %1 of %2 processors currently running.

tHyper-V failed creating a new partition (status %1)!

lHyper-V detected access to a restricted MSR (Msr: %1, IsWrite: %2, MsrValue: %3, AccessStatus: %4, Pc: %5, ImageBase: %6, ImageChecksum: %7, ImageTimestamp: %8, ImageName: %9).

�Hyper-V successfully created a new partition (partition %1).

|Hyper-V successfully deleted a partition (partition %1).

�Host processor features mask: %2%n%nHost xsave features mask: %3%n%nHost cache line flush size: %4 bytes

pHypervisor initial page allocation NUMA policy: %1

lConnect IOCTL failed when registering interface.

hRegistering remote hypercall interface failed.

|Library initialization failed when registering interface.

@NUMA distribution disabled

8Even NUMA distribution

HProportional NUMA distribution

�4VS_VERSION_INFO��
�e
�e?�StringFileInfo�040904B0LCompanyNameMicrosoft CorporationLFileDescriptionHv Loader Libraryh$FileVersion10.0.26100.1 (WinBuild.160101.0800):
InternalNamehvloader.dll�.LegalCopyright� Microsoft Corporation. All rights reserved.JOriginalFilenamehvloader.dll.muij%ProductNameMicrosoft� Windows� Operating System>
ProductVersion10.0.26100.1DVarFileInfo$Translation �PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPAD

Anon7 - 2021