how to put the EFI partition on the beginning of the disk to be able t

I've erased the MSR and the recovery partition. Now this is the new structure :



root@ziomario-Z390-AORUS-PRO:/home/ziomario/Scrivania# fdisk /dev/sda -l


Disk /dev/sda: 465,78 GiB, 500107862016 bytes, 976773168 sectors

Disk model: CT500MX500SSD4

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disklabel type: gpt

Dispositivo Start Fine Settori Size Tipo

/dev/sda1 2048 1488895 1486848 726M EFI System

/dev/sda2 1488896 975591423 974102528 464,5G Microsoft basic data

/dev/sda3 975591424 976773119 1181696 577M Windows recovery environment



I tried to boot windows 10 physically with this script,but it didn't boot :



qemu-system-x86_64 -boot menu=on \

-bios /usr/share/OVMF/OVMF_CODE.fd \

-drive file=/dev/sda,media=disk,format=raw \

-cpu host -enable-kvm -m 16G



you can see the error message here :



Schermata a 2020-05-18 17-28-11.png - Google Drive

Hi there @ziomario

Don't do ANYTHING with the HDD's -- as I said in my previous post -- simply when creating the VM allocate local storage e.g 60GB or however much you want to use and specify it as RAW VIRTIO.

(For creating storage -- choose custom and browse local -- then select RAW / VIRTIO).

That's ALL you need to do -- don't bother formatting anything or preparing the HDD in Windows.

Now just add hardware (e.g win virtio iso and the windows iso) plus any other pieces of hardware - e.g network card, and I'd use the spice video (default), and the EFI for the boot.

Now just select "Begin installation"

point to the win virtio iso file when Windows install asks for driver.

To make the VM totally viewable across your network install software to create a Bridge (only on wired connections and then select shared device for the network giving name of your bridge) -- otherwise use NAT - although in that case you won't have access to the HOST from the VM - you can access the rest of your LAN and the internet of course.

I use Arch linux with KDE desktop (Window manager / GUI -- select SDDM) .

Work through this-- other distros might be similar though.

Complete Installation of KVM, QEMU and Virt Manager on Arch Linux and Manjaro | ComputingForGeeks

There's one error in this -- you will after doing this need to install package dmidecode otherwise libvirt service won't start the first time.

Cheers
jimbo

Make sure that you have important data backed up to another drive or the cloud:

Macrium Software | Your Image is Everything
Backup and Restore with Macrium Reflect

Run each the V2 and DM log collectors so that files can be scanned.
If there are reported major problems they can be troubleshooted.
BSOD - Posting Instructions

Make sure the default language is English so that the logs can be scanned:


https://www.tenforums.com/tutorials/...dows-10-a.html
Change Display Language in Windows 10


This tutorial has steps to disable automatic repair:
Enable or Disable Automatic Repair in Windows 10

I sent you the log files privately.

The logs were scanned.

The computer has windows insider.

Version : 10.0.19628

The logs displayed: SL_LICENSING_STATUS_UNLICENSED

Please activate windows:
https://support.microsoft.com/en-us/...troubleshooter
https://support.microsoft.com/en-us/...ivation-errors
https://support.microsoft.com/en-us/...-phone-numbers

thats not true !



- - - Updated - - -

how it works ? it is also true that on the low & right corner of Windows 10,I see :

The logs displayed that as V2 was ran in safe mode.

See if you can run V2 with normal boot.

The computer has been having BSOD.
Please send feedback to Microsoft using the insiders feedback hub.

that-s exactly the point. I can go only in safe mode. this is the exact reason why I gave you the log files. But it does not happens when I use it without qemu & kvm.

1) Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /v C:
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot


2) Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10

Code:

Event[37310]:
  Log Name: System
  Source: Ntfs
  Date: 2020-05-18T23:33:57.2040000Z
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-N9UN2H3
  Description: 
A corruption was discovered in the file system structure on volume ??.

La Tabella file master (MFT) contiene un record file danneggiato.  Il numero di riferimento del file Φ 0x250000000a56da.  Il nome del file Φ "<Impossibile determinare il nome del file>".