Marietto

Hello to everyone. I would like to install Windows 7 x64 bit on my mobo Aorus pro based on the Z390 platform. I want to explain what I did,because at the end it failed giving a BSOD that I want to fix. I've followed the tutorial on this page : and I've reached the stage where I see the disks where to install Windows 7. Unfortunately I have one only disk that I can use and it is an USB disk,model : WD 3200BMV External but Windows refuses to install on a USB disk. At this point I've used But there is another problem on the stage 2 : it won't be installed on a USB disk. And unfortunately I have only one spare USB disk to use. Anyway I found a method to achieve the goal. The method explained here : https://github.com/vavrecan/usb-boot-watcher ok. This is what I did : C:\Users\virtu\Downloads\GetWaikTools\Waik_3\amd64>imagex /apply I:\Backup\Windows\en_windows_7_professional_x64_dvd_24.4.10\sources\install.wim 1 g: ImageX Tool for Windows Copyright (C) Microsoft Corp. All rights reserved. Version: 6.1.7600.16385 [ 100% ] Applying progress Successfully applied image. C:\Users\virtu\Downloads\GetWaikTools\Waik_3>bcdboot f:\Windows /s f: /v BFSVC: ServiceBootFiles MuiOnly:n Res:y Fonts:y BootMgrOvw:n BootStatOvw:n DbgTrn:y SuspendBDE:n BFSVC: Unable to open file f:\Windows\boot\Resources\BOOTRES.DLL for read because the file or path does not exist BFSVC Warning: Failed to determine source OS version. BFSVC: Copying boot files CopyBootManager(Yes) f:\Windows\boot\EFI -> \\?\GLOBALROOT\Device\HarddiskVolume42\EFI\Microsoft\Boot BFSVC: Updating \\?\GLOBALROOT\Device\HarddiskVolume42\EFI\Boot\bootx64.efi BFSVC: Creating Recovery directory. BFSVC: Logging boot file servicing to bootstat log \\?\GLOBALROOT\Device\HarddiskVolume42\EFI\Microsoft\Boot\BOOTSTAT.DAT. BFSVC Warning: Failed to log servicing event to bootstat \\?\GLOBALROOT\Device\HarddiskVolume42\EFI\Microsoft\Boot\BOOTSTAT.DAT. Status: 0x80000005 BFSVC: Copying font files from f:\Windows\boot\Fonts to \\?\GLOBALROOT\Device\HarddiskVolume42\EFI\Microsoft\Boot\Fonts... BFSVC: Copying resource files from f:\Windows\boot\Resources to \\?\GLOBALROOT\Device\HarddiskVolume42\EFI\Microsoft\Boot\Resources... BFSVC: SetNamedSecurityInfo failed! Error code = 0x2 BFSVC Warning: Resource files missing from f:\Windows\boot\Resources. These files are required for some editions of Windows. If you are servicing older versions of Windows, you can ignore this message. BFSVC: Servicing debugger files BFSVC Warning: ServiceDebuggerFiles: f:\Windows\boot\BootDebuggerFiles.ini does not exist BFSVC: System partition is not in a space BFSVC: BfsInitializeBcdStore flags(0x0000001c) RetainElementData:n DelExistinObject:n BFSVC: VolumePathName for f:\Windows is f:\ BFSVC: SystemRoot is \Windows BFSVC: Opening template from \Device\HarddiskVolume42\Windows\System32\config\BCD-Template. BFSVC: Opening store from \Device\HarddiskVolume42\EFI\Microsoft\Boot\BCD BFSVC: System BCD store does not exist, creating. BFSVC: Creating General objects. BFSVC: Creating Resume object. BFSVC: Creating MemTest object. BFSVC: Creating OsLoader object. BFSVC: OsLoader identifier: {f1a07f02-0ddc-11ef-af3b-e0d55ee21f22} BFSVC: Removing duplicate entries. BFSVC: Create BOOTMGR object RetainBootDefault:n BFSVC: Setting {default} to {f1a07f02-0ddc-11ef-af3b-e0d55ee21f22} BFSVC: Cleaning up debugger settings. BFSVC: Cleaning up hypervisor settings. BFSVC: Opening recovery store from \Device\HarddiskVolume42\EFI\Microsoft\Recovery\BCD BFSVC: Creating new recovery store \Device\HarddiskVolume42\EFI\Microsoft\Recovery\BCD BFSVC: Creating General objects. BFSVC: Create BOOTMGR object RetainBootDefault:y Boot files successfully created. The final stage : C:\Users\virtu\Downloads\usb-boot-watcher-master\bin\amd64>UsbBootWatcher /prepare f:\Windows\System32 Copy from C:\Users\virtu\Downloads\usb-boot-watcher-master\bin\amd64\UsbBootWatcher.exe To f:\Windows\System32\UsbBootWatcher.exe Copy from UsbBootWatcher.conf To f:\Windows\System32\UsbBootWatcher.conf Copy from f:\Windows\System32\config\system To f:\Windows\System32\config\system.backup20240509083357 Registry hive loaded HKLM\USBBOOT Target control set ControlSet001 Updating USBBOOT\ControlSet001\Services\usbstor Updating USBBOOT\ControlSet001\Services\usbehci Updating USBBOOT\ControlSet001\Services\usbohci Updating USBBOOT\ControlSet001\Services\usbuhci Updating USBBOOT\ControlSet001\Services\usbhub Creating service USBBOOT\ControlSet001\Services\Usb Boot Watcher Service Registry hive unloaded HKLM\USBBOOT It didn't work. You want to see well whats happened ? https://ibb.co/v4Bg4jC https://ibb.co/Qcpkysg How to fix this error ?

Hello to everyone. What I would like to understand if why,when I try to passthru my RTX 2080 ti from FreeBSD to Windows 11,it won't do it,causing the error 12. It says that it generates a resource conflict and requires additional installation). I'm trying to debug the error. Below you see the IOMMU group of my Nvidia Geforce RTX 2080 ti passed in a Windows 11 / bhyve VM and of Windows 11 installed physically. I'm not able to understand if there are inconsistencies. VM : Group: 30.0.15.1123 - Device: NVIDIA GeForce RTX 2080 Ti (Device ID: PCI\VEN_10DE&DEV_1E04&SUBSYS_250319DA&REV_A1\3&61AAA01&0&48) Group: 4.39.0.0 - Device: NVIDIA Virtual Audio Device (Wave Extensible) (WDM) (Device ID: ROOT\UNNAMED_DEVICE\0000) Group: 1.46.831.832 - Device: NVIDIA USB Type-C Port Policy Controller (Device ID: PCI\VEN_10DE&DEV_1AD7&SUBSYS_250319DA&REV_A1\3&61AAA01&0&4B) Group: 10.0.22000.2360 - Device: Controller host NVIDIA USB 3.10 eXtensible - 1.10 (Microsoft) (Device ID: PCI\VEN_10DE&DEV_1AD6&SUBSYS_250319DA&REV_A1\3&61AAA01&0&4A) Physical installation : Group: 31.0.15.5222 - Device: NVIDIA GeForce RTX 2080 Ti (Device ID: PCI\VEN_10DE&DEV_1E04&SUBSYS_250319DA&REV_A1\4&94764DC&0&0009) Group: 4.49.0.0 - Device: NVIDIA Virtual Audio Device (Wave Extensible) (WDM) (Device ID: ROOT\UNNAMED_DEVICE\0000) Group: 1.50.831.832 - Device: NVIDIA USB Type-C Port Policy Controller (Device ID: PCI\VEN_10DE&DEV_1AD7&SUBSYS_250319DA&REV_A1\4&9476 4DC&0&0309) Group: 10.0.22000.2360 - Device: NVIDIA USB 3.10 eXtensible Host Controller - 1.10 (Microsoft) (Device ID: PCI\VEN_10DE&DEV_1AD6&SUBSY S_250319DA&REV_A1\4&94764DC&0&0209) As an experiment I've passed only this device from FreeBSD to WIndows 11 : pptdevs="2/0/0" I have excluded "2/0/1 ; 2/0/2 ; 2/0/3". I want to show you what means these addresses : 02:00.0 VGA compatible controller: NVIDIA Corporation TU102 [GeForce RTX 2080 Ti] (rev a1) 02:00.1 Audio device: NVIDIA Corporation TU102 High Definition Audio Controller (rev a1) 02:00.2 USB controller: NVIDIA Corporation TU102 USB 3.1 Host Controller (rev a1) 02:00.3 Serial bus controller: NVIDIA Corporation TU102 USB Type-C UCSI Controller (rev a1) What happened when I launched the vm using these parameters ? bhyve -S -c sockets=2,cores=2,threads=2 -m 4G -w -H -A \ -s 0,hostbridge \ -s 1,ahci-hd,/mnt/$vmdisk0'p2'/bhyve/img/Windows/Windows11.img,bootindex=1 \ -s 9:0,passthru,2/0/0 \ -s 11,hda,play=/dev/dsp,rec=/dev/dsp \ -s 13,virtio-net,tap18 \ -s 29,fbuf,tcp=0.0.0.0:5918,w=1600,h=950,wait \ -s 30,xhci,tablet \ -s 31,lpc \ -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI_CODE.fd \ vm0:18 < /dev/null & sleep 2 && vncviewer 0:18 this error : Assertion failed: (!err), function hda_init, file /usr/corvin-src-releng-140/usr.sbin/bhyve/pci_hda.c, line 353. The error is caused by this parameter : -s 11,hda,play=/dev/dsp,rec=/dev/dsp \ I have excluded it and Windows 11 booted. Now,inside it I still see the error 12 : The device PCI\VEN_10DE&DEV_1E04&SUBSYS_250319DA&REV_A1\3&61aaa01&0&48 generates a resource conflict and requires additional installation. If I pass to the vm only -s 9:0,passthru,2/0/0 \ ; it does not work anyway,because AFAIK,MAYBE there is one and only IOMMU group,so I should pass everything ? But if I pass everything,the error 12 is there anyway. I would like to understand if there is a problem with the IOMMU thing,if there is maybe there is the needing to develop a patch like this one : GitHub - benbaker76/linux-acs-override for FreeBSD. For an experienced developer should not be so hard to understand which devices conflict. I want to ask some help to understand how to debug the error. If we will be able to understand which devices conflict,maybe I can explain this to the bhyve developer with which I'm in contact and he can develop a patch. So,we will be able to use every modern nvidia gpus inside a Windows VM with bhyve under FreeBSD ! That's a nice goal,isn't it ? So,please ask me more informations that you need to understand the origin of the error. Windows Build/Version : 10.0.22000.2538

Hello to everyone. I've installed Windows XP 32 and 64 bit as virtual machine with VMware 17 on my Ubuntu 23.10. The goal is to be able to boot them in UEFI mode. At a certain point of the video,he changes the boot mode from BIOS to UEFI (I can't attach urls). I did the same,but In my case it won't change. The button is greyed out. I've also converted those xp virtual machines from vmdk to img and I tried to boot them with bhyve (the hypervisor used on FreeBSD),but they didn't boot. So,I can't check if the vmdk images are able to boot with VMware because I'm not able to enable the UEFI option and I can't check if they don't boot with bhyve because they don't boot with UEFI in VMware.