MZ@ !L!This program cannot be run in DOS mode. $<թRթRթRԩRPԩRRichթRPEL! J p@ G.rdatap@@.rsrcP H@@i[ T.rdataT.rdata$zzzdbg @.rsrc$01@!F.rsrc$0200H `x     8!!"pA$dMUIųb$XPa+= jt#J `X MUI en-US)Hypervisor/Virtual Machine Support Driver)Hypervisor/Virtual Machine Support Driver( d&(*h,06@PU `a&(+x7PP<0= =''D>!!>11?AAp@LHypervisor 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. tHypervisor SPT Resizing policy failed to initialize. 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. Hypervisor launch failed; at least one of the processors in the system does not appear to support the features required by the hypervisor. (leaf: %1, required features: %2, features available: %3) 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 accessed (status %2). Hyper-V launch failed; the image %1 could not be loaded (status %2). Hyper-V launch failed; the image %1 could not be read (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; Either No Execute feature (NX) not present or not enabled in BIOS. Hypervisor launch failed; at least one of the processors in the system is incompatible with the others. @Hypervisor launch failed; Processor does not support the minimum features required to run the hypervisor (MSR index %1, allowed bits %2, required bits %3). Hypervisor launch failed; Processor does not provide the features necessary to run the hypervisor (BalStatus %1, leaf1 EAX %2, VMCR MS EAX %3, SVM CPUID features %4, has working SMM %5). 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; Incompatible SVM features present. Hypervisor launch failed; Incompatible VMX features present. 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; 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 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. A device is operating with reduced performance because of a problem with the system BIOS.%n%nThe device is not reported under the scope of a unique I/O remapping unit.%n%nDevice ID: %1%nPartition ID: %2 A device will not work correctly because of a problem with the system BIOS.%n%nThe Requester IDs reported for the device overlap with those reported for another device.%n%nDevice ID: %1%nPartition ID: %2 A device will not work correctly because the hypervisor does not have enough resources.%n%nDevice ID: %1%nPartition ID: %2 A device will not work correctly because of a problem with the system BIOS.%n%nAn IOAPIC is not correctly reported.%n%nIOAPIC ID: %1 A device could not be used by a child partition because of a limitation of the system hardware and BIOS.%n%nThe I/O remapping unit that controls the device does not have sufficient capabilities.%n%nDevice ID: %1%nI/O remapping unit base address: %2%nPartition ID: %3 A device could not be used by a child partition because of a limitation of the system hardware and BIOS.%n%nThe device cannot be securely used by a child partition.%n%nDevice ID: %1%nPartition ID: %2 hThe image %1 could not be accessed (status %2). dThe image %1 could not be loaded (status %2). `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). 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 The hypervisor did not enable mitigations for CVE-2018-3646 for virtual machines because HyperThreading is enabled and the hypervisor core scheduler is not enabled. To enable mitigations for CVE-2018-3646 for virtual machines, enable the core scheduler by running "bcdedit /set hypervisorschedulertype core" from an elevated command prompt and reboot. Error Warning Information TMicrosoft-Windows-Hyper-V-Hypervisor System THypervisor Eventlog creation failed! THypervisor Eventlog deletion failed! LHypervisor System Start Options! 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). 4VS_VERSION_INFO ~ 98 ~ 98?(StringFileInfo040904B0LCompanyNameMicrosoft CorporationVFileDescriptionHypervisor Boot Driver7FileVersion10.0.14393.2430 (rs1_release_inmarket_aim.180806-1810)<InternalNameHvService.sys.LegalCopyright Microsoft Corporation. All rights reserved.LOriginalFilenameHvService.sys.muij%ProductNameMicrosoft Windows Operating SystemDProductVersion10.0.14393.2430DVarFileInfo$Translation PADDINGXXPADDINGPADD