Windows 10: Peeling the layers of Collision for Containers, virtual, ROM Persistant, intel hypervisor...

I'm trying to help my mother return her pc back to having a functional and cohesive SYSTEM like it had been prior to windows 10 but she's created such a mess after ignoring some failed problems in the past that have totally made windows 10 incapable of reliable processing info to the people using the PC.


So, essentially cant determine what's by design, and what's result of overlays, virtualization or previous failures and yeah.

I mean total UEFI lack of usable system i/o for temperature, voltages, Overclocking is unpredictable, kernel and cpu we used to use for overclocking are greyed out and refuse to report anything to the OS without 3rd party work arounds for fan controls, temp reading, all system critical information. We want that stuff back.


Everything else in the house is mobile device but with the new security features and cross platform features am unable to keep my familes android **** off the computer long enough to build back a trusted system, secure signing keys, and service everything. People think they can just throw a new part at it and solve problems in virtual world and cant differentitate between that space and the ones around it. Yall need to encorporate a Shopping mall YOU ARE HERE, Map so ppl can map our their destination graphically.. sorry in advance for so much at once



UEFI lets you adjust overclock but not where it necessarily reflects in the OS as it should/did. whatever Kernel that was virtualized initially that intel or whoever used to initially setup the computer seems dead to me, unresponsive, or just really good at hiding.... It's like we have 20 different profiles fighting in a race to take control over settings and system performance and effects cached memory settings for the last people using the computer.... am i going nuts here or is this by design?



Workstation homegroup desktop
Device name MARCYSS-PC


Processor IntelR CoreTM i7-3930K CPU @ 3.20GHz 3.20 GHz

Installed RAM 16.0 GB

Device ID 08481185-DCAA-4FDD-8114-02027898B5EA

Product ID 00330-80000-00000-AA571

System type 64-bit operating system, x64-based processor

Pen and touch No pen or touch input is available for this display




Hardware:


Asus P9X79 Deluxe mark1 using AMI UEFI from 2014, latest.. Aptio maybe at somepoint?

CPU: i7-3930k , true speed is "turbo" to 3.8 but unsure if this is optimized by OS or kernel or the hypervisor?

Mushkin 997008 - 4x4 - PC3-14900 9/10/9/27/1 but slowed it half speed to control heat.

As if there's a constant push pull of control over system critical settings by the browser, user profiles, hypervisor, machine, kernel and software... in the end nobody wins though and system might lock up, send error, fail updates, stop updates, do random stuff or try to finish activities from previous events....

EVGA 1060 6gb occupying pci16 slot

varying processor micro ids between whats reported by windows and the motherboard UEFI neither i can confirm are supposed to be for my chipset

2 250gb ssds on sata6g - no third party software this round

but used to have AiDA64. Steam, GPU OC software, i think the computer was initially tuned with XTU OC profiles in addition to intel/asus default ones.




She tried reinstalling windows 10 times by now, keeeps using the same hard drives, refuses to try another. Differences in definition of cleaning vs restoring, vs NUCLEUR THERMOBARIC irradication of everything to restore peace and order on our computer. Help plz. I really suspect this to be related to Linux Subsystem **** she uses for flashing her android devices. She nor i fully understand all of that, and the networking implications of all that so now we have devices with with root access, administrator, super admin, enterprise and system control via OTA updates or USB, HOW to you keep this all seperated? Cross platform features suck so far. I know they're "in development" but damn, everything nowadays feels underdeveloped and buggy, erratic and later deemed unsafe, riddled with security vulnerabs.,,



1/23/2021 5:49 AM Windows Error Reporting Fault bucket , type 0
Event Name: MpTelemetry
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft Defender Antivirus 77BDAF73-B396-481F-9042-AD358843EC24
P2: 4.18.1909.6
P3: TimeOut
P4: 1.1.17700.4
P5: fixed
P6: 12 / 2049+
P7: 5 / not boot
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_Microsoft Defend_18d7544f9d3754b394bf88206eacba8b4312145e_00000000_76767c76-df87-4546-9b3f-0d7b51129cc1

Analysis symbol: 
Rechecking for solution: 0
Report Id: 76767c76-df87-4546-9b3f-0d7b51129cc1
Report Status: 4
Hashed bucket: 
Cab Guid: 0


^What kinda Error is this supposed to be? Thats not legible to a human being. come on.


1/23/2021 5:49 AM Windows Error Reporting Fault bucket 1565884248932642552, type 5
Event Name: MpTelemetry
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft Defender Antivirus 77BDAF73-B396-481F-9042-AD358843EC24
P2: 4.18.1909.6
P3: TimeOut
P4: 1.1.17700.4
P5: fixed
P6: 12 / 2049+
P7: 5 / not boot
P8: 
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C21.tmp.WERInternalMetadata.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_Microsoft Defend_18d7544f9d3754b394bf88206eacba8b4312145e_00000000_76767c76-df87-4546-9b3f-0d7b51129cc1

Analysis symbol: 
Rechecking for solution: 0
Report Id: 76767c76-df87-4546-9b3f-0d7b51129cc1
Report Status: 268435456
Hashed bucket: e618bb5506cf834d65bb236d91026ef8
Cab Guid: 0





1/22/2021 6:42 PM Windows Error Reporting Fault bucket , type 0
Event Name: AppxDeploymentFailureBlue
Response: Not available
Cab Id: 0

Problem signature:
P1: 80004004
P2: 13
P3: 0
P4: NONE
P5: 10.0.19041.630
P6: 401
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_80004004_ea754f1431511d2d9c473ffcee4d37cf6426b414_00000000_37e28731-6b22-45af-b8b1-4da66281b662

Analysis symbol: 
Rechecking for solution: 0
Report Id: 37e28731-6b22-45af-b8b1-4da66281b662
Report Status: 4
Hashed bucket: 
Cab Guid: 0


1/22/2021 6:38 PM Application Hang The program OptionalFeatures.exe version 10.0.19041.1 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 150c
 Start Time: 01d6f0ed632d5ff1
 Termination Time: 4294967295
 Application Path: C:\Windows\System32\OptionalFeatures.exe
 Report Id: 420f9516-09f9-46a1-b5c5-e55adb2fe84d
 Faulting package full name: 
 Faulting package-relative application ID: 
 Hang type: Top level window is idle




is this normal for networking adapter THERES SO MANY?

Name [00000000] Microsoft Kernel Debug Network Adapter




Adapter Type Not Available

Product Type Microsoft Kernel Debug Network Adapter

Installed Yes
PNP Device ID ROOT\KDNIC\0000
Last Reset 1/22/2021 10:52 AM
Service Name kdnic
DHCP Enabled Yes
DHCP Server Not Available
DHCP Lease Expires Not Available

DHCP Lease Obtained Not Available

Everythin else NA


Driver C:\WINDOWS\SYSTEM32\DRIVERS\KDNIC.SYS 6.1.0.0, 32.52 KB 33,296 bytes, 12/7/2019 1:07 AM


if network adapters are installed are they being used if something is enabled? i'd think not necessarily but idk


windows 10 ate my uefi kernel :

:)

 

Virtual Machine is not starting because Hypervisor is not running

Virtual Machine is not starting because Hypervisor is not running.

Any suggestion?

 

Window sandbox fail to start 0x800706d9 (Hypervisor/Virtual Machine Support Driver element not found)

When I run the sandbox, error 0x800706d9 displayed

From the event viewer

The Container Manager Service service depends on the HV Host Service service which failed to start because of the following error:

The dependency service or group failed to start.

The HV Host Service service depends on the Hypervisor/Virtual Machine Support Driver service which failed to start because of the following error:

Element not found.

The Hypervisor/Virtual Machine Support Driver service failed to start due to the following error:

Element not found.

 

Windows 10: Switched from BIOS to UEFI. Hyper-V reports that the hypervisor is not running

I partitioned my hard drive and installed Debian on second partition. In order to do this I had to switch from BIOS to UEFI after basically destorying the MBR. Everything works great. However when I choose to boot to Windows 10 my various images within Hyper-V are not starting. The error states that hypervisor is not running. Any ideas?

I tried this Hyper-V reports that the hypervisor is not running. How to start the hypervisor? but no joy. Any suggestions on why this would have stopped working?