Solved Verifying Backup and Restore


Macrium Reflect includes viBoot (even the Free version). This allows you to boot a Macrium image as a Hyper-V or VirtualBox VM. This is an alternative way to test that an image is viable, and takes just a few minutes to set up and boot to Windows.
That's the way I do it. One note though; On my laptop with a Samsung NVME drive, using the Samsung driver the backup would not start in VIboot or Hyper-V. The Image never failed verification though. I removed the Samsung driver and installed the Microsoft driver and all is well.
 

My Computer

System One

  • OS
    Windows 10
As I said earlier, the roots of verification date back to days when writing media were less reliable. If you think about it, now we do terabytes of writing to modern hard drives, and data loss is rare.

Far be it for me to advise that verification is not needed, but I would like to challenge users here when was the last time verification failed on modern hard drives. Even when I did do i6r, I cannot recollect a single instance on modern hard drives. For sure I used to get failures on bsckimg up to dvd drive (so last but one decade).

To me verification is more of a physcological activity, these days, predicated on historical use/experience.

Naturally, there is always a SODs law that will kick in i.e. because you failed to verify it, naturally, this is the one time the backup will be knackered LOL.
Reliability of backup media is of course an issue.

Reliability of backup tools/softwares is another issue, this thread focused mainly on this issue.

There are hordes of other backup issues:

Do you have a hourly/daily/weekly/monthly/yearly backup routine?

Is your backup routine flexible enough to allow for orderly manual overrides on an as needed basis?

Do you strictly follow a 1-2-3 rule of backup (1 master, 2 backups, 3 different media) or strictly follow some other backup rule?

Do you make sure that at least 1 backup is air gapped from your live system at all times?

Do you use two or more backup tools/softwares to make the respective backups on your backup media?

How do you best integrate your backup effort in your overall computing and (home) office/house keeping?

Do you have dated and ticked off checklists for backup chores, password maintenance, and the like, and do you keep a log of irregularities?
.
.
.
Then of course, in all of the above, how do you get the overall biggest bang for your limited buck?

Each one of the '?' in the above is worth its own thread, IMHO.
 

My Computer

System One

  • OS
    Windows 10 Pro
That's the way I do it. One note though; On my laptop with a Samsung NVME drive, using the Samsung driver the backup would not start in VIboot or Hyper-V. The Image never failed verification though. I removed the Samsung driver and installed the Microsoft driver and all is well.

Reliability of backup media is of course an issue.

Reliability of backup tools/softwares is another issue, this thread focused mainly on this issue.
My point is these two are really integrally linked. As I said, back in days of optical drives, you needed for sure to verify as the media was unreliable to some degree. I have no concerns about the modern apps such as AOMEI Backupper or Macrium Reflect being 99.9999999+ % reliable in creating the temporary image data - the unreliability factor is the ACTUAL writing to the media.

So I reiterate my challenge to all users of mainstream imaging software - when was the last time you ever had a verification failure (and what media was it)?

In my opinion, verification now only serves as peace of mind, which is fine, but lets not kid ourselves, it is a truly essential activity. I fully accept that if you verify every backup, it will pick up the (say) one case in a thousand you would miss by not verifying. I say one in a thousand as I have literally done hundred of backups with Reflect
 

My Computer

System One

  • OS
    Windows 10 Pro + others in VHDs
    Computer type
    Laptop
    Manufacturer/Model
    ASUS Vivobook 14
    CPU
    I7
    Motherboard
    Yep, Laptop has one.
    Memory
    16 GB
    Graphics Card(s)
    Integrated Intel Iris XE
    Sound Card
    Realtek built in
    Monitor(s) Displays
    N/A
    Screen Resolution
    1920x1080
    Hard Drives
    1 TB Optane NVME SSD, 1 TB NVME SSD
    PSU
    Yep, got one
    Case
    Yep, got one
    Cooling
    Stella Artois
    Keyboard
    Built in
    Mouse
    Bluetooth , wired
    Internet Speed
    72 Mb/s :-(
    Browser
    Edge mostly
    Antivirus
    Defender
    Other Info
    TPM 2.0
My point is these two are really integrally linked.
I don't think that's the case. Failure of the backup medium is primarily hardware-related. Fialure of the backup tool is primarily software-related. That's 2 different failure mechanisms.

For example, I once dropped a USB HDD and I could not access my backup. Even if I could repair the USB HDD and access the backup, I would no longer trust it as a backup medium. That's one failure mecchanism.

I never had a problem with Backup and Restore (Windows 7) until I read in this forum that it has been deprecated years ago. Even if the tool would still work (it actually did) I would still toss it as a backup tool (I actuallly did) and that's a failure which is a totally different one from dropping the USB HDD.

I say one in a thousand as I have literally done hundred of backups with Reflect
And then there is the case of File History missing the hourly backups. I would say that it is more often than one in a thousand (from checking the 'Events' log, although not counting)

There is an easy workaround > manually running File History whenever you feel the need for it. But if you are raising the bar, then 'workaround' is not the word that you want to hear.
 

My Computer

System One

  • OS
    Windows 10 Pro
I don't think that's the case. Failure of the backup medium is primarily hardware-related. Fialure of the backup tool is primarily software-related. That's 2 different failure mechanisms.

For example, I once dropped a USB HDD and I could not access my backup. Even if I could repair the USB HDD and access the backup, I would no longer trust it as a backup medium. That's one failure mecchanism.

I never had a problem with Backup and Restore (Windows 7) until I read in this forum that it has been deprecated years ago. Even if the tool would still work (it actually did) I would still toss it as a backup tool (I actuallly did) and that's a failure which is a totally different one from dropping the USB HDD.


And then there is the case of File History missing the hourly backups. I would say that it is more often than one in a thousand (from checking the 'Events' log, although not counting)

There is an easy workaround > manually running File History whenever you feel the need for it. But if you are raising the bar, then 'workaround' is not the word that you want to hear.
Sigh - why not answer me and tell me the last time you had a verification failure?
 

My Computer

System One

  • OS
    Windows 10 Pro + others in VHDs
    Computer type
    Laptop
    Manufacturer/Model
    ASUS Vivobook 14
    CPU
    I7
    Motherboard
    Yep, Laptop has one.
    Memory
    16 GB
    Graphics Card(s)
    Integrated Intel Iris XE
    Sound Card
    Realtek built in
    Monitor(s) Displays
    N/A
    Screen Resolution
    1920x1080
    Hard Drives
    1 TB Optane NVME SSD, 1 TB NVME SSD
    PSU
    Yep, got one
    Case
    Yep, got one
    Cooling
    Stella Artois
    Keyboard
    Built in
    Mouse
    Bluetooth , wired
    Internet Speed
    72 Mb/s :-(
    Browser
    Edge mostly
    Antivirus
    Defender
    Other Info
    TPM 2.0
Sigh - why not answer me and tell me the last time you had a verification failure?
Well, I told you about my 'Backup and Restore' mishaps, there is a 'Backup and Restore' forum on this site with more mishaps, then there is the MR Support Forum/Disk Imaging subforum with topics like:
'index verification failed on external USB drive'
'image failed to reproduce windows start menu and applications'
'Creepy image errors not getting logged'
etc.

Note that a failed restore is a failed verification.
 

My Computer

System One

  • OS
    Windows 10 Pro
Well, I told you about my 'Backup and Restore' mishaps, there is a 'Backup and Restore' forum on this site with more mishaps, then there is the MR Support Forum/Disk Imaging subforum with topics like:
'index verification failed on external USB drive'
'image failed to reproduce windows start menu and applications'
'Creepy image errors not getting logged'
etc.

Note that a failed restore is a failed verification.
Nearly all mishaps are either user error or the media is damaged in some way. Verification is a specific process run after the backup has (allegedly) been done without any error messages. It is essentially like verifying the sha of an iso download.

All the other failures have nothing to do with verification.

So for the final time, when was the last time you had a verification failure, and what media were you using.

a) within last month

b) within last year

c) within last five years

d) over five years (or never).
 

My Computer

System One

  • OS
    Windows 10 Pro + others in VHDs
    Computer type
    Laptop
    Manufacturer/Model
    ASUS Vivobook 14
    CPU
    I7
    Motherboard
    Yep, Laptop has one.
    Memory
    16 GB
    Graphics Card(s)
    Integrated Intel Iris XE
    Sound Card
    Realtek built in
    Monitor(s) Displays
    N/A
    Screen Resolution
    1920x1080
    Hard Drives
    1 TB Optane NVME SSD, 1 TB NVME SSD
    PSU
    Yep, got one
    Case
    Yep, got one
    Cooling
    Stella Artois
    Keyboard
    Built in
    Mouse
    Bluetooth , wired
    Internet Speed
    72 Mb/s :-(
    Browser
    Edge mostly
    Antivirus
    Defender
    Other Info
    TPM 2.0
Nearly all mishaps are either user error or the media is damaged in some way. Verification is a specific process run after the backup has (allegedly) been done without any error messages. It is essentially like verifying the sha of an iso download.

All the other failures have nothing to do with verification.

So for the final time, when was the last time you had a verification failure, and what media were you using.

a) within last month

b) within last year

c) within last five years

d) over five years (or never).
That's a very narrow definition of verification, no wonder that you want just about everything to pass verification according to that very narrow definition.

In the real world, a restored image passes verification or not, nothing else matters, and according to this real world definition of verification, there are daily problems on the forums.
 

My Computer

System One

  • OS
    Windows 10 Pro
That's a very narrow definition of verification, no wonder that you want just about everything to pass verification according to that very narrow definition.

In the real world, a restored image passes verification or not, nothing else matters, and according to this real world definition of verification, there are daily problems on the forums.
Whatever. Not prepared to discuss anymore if you cannot/will not answer a simple question.
 

My Computer

System One

  • OS
    Windows 10 Pro + others in VHDs
    Computer type
    Laptop
    Manufacturer/Model
    ASUS Vivobook 14
    CPU
    I7
    Motherboard
    Yep, Laptop has one.
    Memory
    16 GB
    Graphics Card(s)
    Integrated Intel Iris XE
    Sound Card
    Realtek built in
    Monitor(s) Displays
    N/A
    Screen Resolution
    1920x1080
    Hard Drives
    1 TB Optane NVME SSD, 1 TB NVME SSD
    PSU
    Yep, got one
    Case
    Yep, got one
    Cooling
    Stella Artois
    Keyboard
    Built in
    Mouse
    Bluetooth , wired
    Internet Speed
    72 Mb/s :-(
    Browser
    Edge mostly
    Antivirus
    Defender
    Other Info
    TPM 2.0
Whatever. Not prepared to discuss anymore if you cannot/will not answer a simple question.
? In the real world definition of the word 'verification' of backups, there are daily problems on the forums.

That's the simple answer to the simple question, posted in the above.
 

My Computer

System One

  • OS
    Windows 10 Pro
? In the real world definition of the word 'verification' of backups, there are daily problems on the forums.

That's the simple answer to the simple question, posted in the above.
Zzzzzzzzzzzzzz.
 

My Computer

System One

  • OS
    Windows 10 Pro + others in VHDs
    Computer type
    Laptop
    Manufacturer/Model
    ASUS Vivobook 14
    CPU
    I7
    Motherboard
    Yep, Laptop has one.
    Memory
    16 GB
    Graphics Card(s)
    Integrated Intel Iris XE
    Sound Card
    Realtek built in
    Monitor(s) Displays
    N/A
    Screen Resolution
    1920x1080
    Hard Drives
    1 TB Optane NVME SSD, 1 TB NVME SSD
    PSU
    Yep, got one
    Case
    Yep, got one
    Cooling
    Stella Artois
    Keyboard
    Built in
    Mouse
    Bluetooth , wired
    Internet Speed
    72 Mb/s :-(
    Browser
    Edge mostly
    Antivirus
    Defender
    Other Info
    TPM 2.0
Well, the very first step is to enable Hyper-V in Windows Features if you have Pro, or install VirtualBox if you have Home. Reflect v8 supports both, if you have v7 then it only supports Hyper-V.

Then it's simply a matter of running viBoot and selecting the .mrimg file you wish to boot as a VM. There's a Ten Forums tutorial for that:

Good morning, Bree.

I went to the tutorial above and found that it was last updated in November 2019. I didn't see anything indicating VirtualBox. (I think Kari generally only uses what's included in Windows, so no surprise there.)

I'm pretty sure that most of my students will have Windows Home, so they'll need instructions for Virtual Box. I couldn't find anything in Windows 11 Tutorials.
 

My Computers

System One System Two

  • OS
    Windows 11 23H2 22631.2861
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP Envy TE01-1xxx
    CPU
    Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz 2.90 GHz
    Motherboard
    16.0GB Dual-Channel Unknown @ 1463MHz (21-21-21-47)
    Memory
    16384 MBytes
    Graphics Card(s)
    Intel UHD Graphics 630
    Sound Card
    Realtek High Definition Audio
    Monitor(s) Displays
    Monitor 1 - Acer 27" Monitor 2 - Acer 27"
    Screen Resolution
    1920 x 1080
    Hard Drives
    WDC PC SN530 SDBPNPZ-512G-1006 (SSD)
    Seagate ST1000DM003-1SB102
    Seagate BUP Slim SCSI Disk Device (SSD)
    PSU
    HP
    Case
    HP
    Cooling
    Standard
    Keyboard
    Logitech Wave K350
    Mouse
    Logitech M705
    Internet Speed
    500 mbps
    Browser
    Firefox
    Antivirus
    Windows Defender
    Other Info
    That's all Folks!
  • Operating System
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP
    CPU
    Intel Core i7 (10th gen) 10700
    Motherboard
    Intel
    Memory
    16 GB
    Graphics card(s)
    Intel UHD Graphics 630
    Sound Card
    Built-in
    Monitor(s) Displays
    Acer 27" & Samsung 24"
    Screen Resolution
    1920 x
    Hard Drives
    SSD (512 GB)
    HDD (1 TB)
    Seagate
    PSU
    Intel i7 10th Generation
    Case
    HP
    Cooling
    HP/Intel?
    Mouse
    Logitech M705
    Keyboard
    Logitech Wave K350
    Internet Speed
    50 mbps
    Browser
    Firefox 90.2
    Antivirus
    Windows Defender
    Other Info
    Headphone/Microphone Combo
    SuperSpeed USB Type-A (4 on front)
    HP 3-in-One Card Readr
    SuperSpeed USB Type-C
    DVD Writer
Nearly all mishaps are either user error or the media is damaged in some way. Verification is a specific process run after the backup has (allegedly) been done without any error messages. It is essentially like verifying the sha of an iso download.

All the other failures have nothing to do with verification.

So for the final time, when was the last time you had a verification failure, and what media were you using.

a) within last month

b) within last year

c) within last five years

d) over five years (or never).
I've had several verification errors using Macrium to backup to my NAS wirelessly. Not every time but maybe three times. I now always use an ethernet cable anytime I back up any of my three computers to the NAS. Never had a failure doing that.
I also have never had a verification error when backing up to an external SSD hard drive.
 

My Computer

System One

  • OS
    Windows 10
I've had several verification errors using Macrium to backup to my NAS wirelessly. Not every time but maybe three times. I now always use an ethernet cable anytime I back up any of my three computers to the NAS. Never had a failure doing that.
I also have never had a verification error when backing up to an external SSD hard drive.
Yeah wifi backup is probably the one mode where verification is important as signal strength can have a big impact.
 

My Computer

System One

  • OS
    Windows 10 Pro + others in VHDs
    Computer type
    Laptop
    Manufacturer/Model
    ASUS Vivobook 14
    CPU
    I7
    Motherboard
    Yep, Laptop has one.
    Memory
    16 GB
    Graphics Card(s)
    Integrated Intel Iris XE
    Sound Card
    Realtek built in
    Monitor(s) Displays
    N/A
    Screen Resolution
    1920x1080
    Hard Drives
    1 TB Optane NVME SSD, 1 TB NVME SSD
    PSU
    Yep, got one
    Case
    Yep, got one
    Cooling
    Stella Artois
    Keyboard
    Built in
    Mouse
    Bluetooth , wired
    Internet Speed
    72 Mb/s :-(
    Browser
    Edge mostly
    Antivirus
    Defender
    Other Info
    TPM 2.0
I went to the tutorial above and found that it was last updated in November 2019. I didn't see anything indicating VirtualBox.
Kari intends to update Reflect tutorials now that v8 Free is available, but I understand health issues have delayed that.

Yes, support for VirtualBox is new for viBoot v8. Very little else has changed in viBoot since the tutorial was last updated, and using it with VirtualBox works the same way as using it with Hyper-V, so the tutorial is still relevant.

For more on this, see Macrium's video here:


And see the Knowledge Base:

 

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD
    Internet Speed
    50 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Beta as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 4GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, and Canary builds as a native boot .vhdx.
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Lattitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Beta as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 4GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, and Canary builds as a native boot .vhdx.
Kari intends to update Reflect tutorials now that v8 Free is available, but I understand health issues have delayed that.

Yes, support for VirtualBox is new for viBoot v8. Very little else has changed in viBoot since the tutorial was last updated, and using it with VirtualBox works the same way as using it with Hyper-V, so the tutorial is still relevant.

For more on this, see Macrium's video here:


And see the Knowledge Base:

Thank you, @Bree! I'm going to try this now. Looks like it may be what I'm looking for.
 

My Computers

System One System Two

  • OS
    Windows 11 23H2 22631.2861
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP Envy TE01-1xxx
    CPU
    Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz 2.90 GHz
    Motherboard
    16.0GB Dual-Channel Unknown @ 1463MHz (21-21-21-47)
    Memory
    16384 MBytes
    Graphics Card(s)
    Intel UHD Graphics 630
    Sound Card
    Realtek High Definition Audio
    Monitor(s) Displays
    Monitor 1 - Acer 27" Monitor 2 - Acer 27"
    Screen Resolution
    1920 x 1080
    Hard Drives
    WDC PC SN530 SDBPNPZ-512G-1006 (SSD)
    Seagate ST1000DM003-1SB102
    Seagate BUP Slim SCSI Disk Device (SSD)
    PSU
    HP
    Case
    HP
    Cooling
    Standard
    Keyboard
    Logitech Wave K350
    Mouse
    Logitech M705
    Internet Speed
    500 mbps
    Browser
    Firefox
    Antivirus
    Windows Defender
    Other Info
    That's all Folks!
  • Operating System
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP
    CPU
    Intel Core i7 (10th gen) 10700
    Motherboard
    Intel
    Memory
    16 GB
    Graphics card(s)
    Intel UHD Graphics 630
    Sound Card
    Built-in
    Monitor(s) Displays
    Acer 27" & Samsung 24"
    Screen Resolution
    1920 x
    Hard Drives
    SSD (512 GB)
    HDD (1 TB)
    Seagate
    PSU
    Intel i7 10th Generation
    Case
    HP
    Cooling
    HP/Intel?
    Mouse
    Logitech M705
    Keyboard
    Logitech Wave K350
    Internet Speed
    50 mbps
    Browser
    Firefox 90.2
    Antivirus
    Windows Defender
    Other Info
    Headphone/Microphone Combo
    SuperSpeed USB Type-A (4 on front)
    HP 3-in-One Card Readr
    SuperSpeed USB Type-C
    DVD Writer
Thank you, @Bree! I'm going to try this now. Looks like it may be what I'm looking for.
Kari intends to update Reflect tutorials now that v8 Free is available, but I understand health issues have delayed that.
Yes, I know. Wishing @Kari all the best and a speedy recovery. I've used his tutorials for several years and they always help.

Thanks for showing me how to use this one too!
For more on this, see Macrium's video here:


And see the Knowledge Base:

 

My Computers

System One System Two

  • OS
    Windows 11 23H2 22631.2861
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP Envy TE01-1xxx
    CPU
    Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz 2.90 GHz
    Motherboard
    16.0GB Dual-Channel Unknown @ 1463MHz (21-21-21-47)
    Memory
    16384 MBytes
    Graphics Card(s)
    Intel UHD Graphics 630
    Sound Card
    Realtek High Definition Audio
    Monitor(s) Displays
    Monitor 1 - Acer 27" Monitor 2 - Acer 27"
    Screen Resolution
    1920 x 1080
    Hard Drives
    WDC PC SN530 SDBPNPZ-512G-1006 (SSD)
    Seagate ST1000DM003-1SB102
    Seagate BUP Slim SCSI Disk Device (SSD)
    PSU
    HP
    Case
    HP
    Cooling
    Standard
    Keyboard
    Logitech Wave K350
    Mouse
    Logitech M705
    Internet Speed
    500 mbps
    Browser
    Firefox
    Antivirus
    Windows Defender
    Other Info
    That's all Folks!
  • Operating System
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP
    CPU
    Intel Core i7 (10th gen) 10700
    Motherboard
    Intel
    Memory
    16 GB
    Graphics card(s)
    Intel UHD Graphics 630
    Sound Card
    Built-in
    Monitor(s) Displays
    Acer 27" & Samsung 24"
    Screen Resolution
    1920 x
    Hard Drives
    SSD (512 GB)
    HDD (1 TB)
    Seagate
    PSU
    Intel i7 10th Generation
    Case
    HP
    Cooling
    HP/Intel?
    Mouse
    Logitech M705
    Keyboard
    Logitech Wave K350
    Internet Speed
    50 mbps
    Browser
    Firefox 90.2
    Antivirus
    Windows Defender
    Other Info
    Headphone/Microphone Combo
    SuperSpeed USB Type-A (4 on front)
    HP 3-in-One Card Readr
    SuperSpeed USB Type-C
    DVD Writer
Thank you, @Bree! I'm going to try this now. Looks like it may be what I'm looking for.
Bear in mind, if you have Pro on PC and using Hyper-V, virtualbox and Hyper-v do not coexist that well.

Virtualbox is very slow if Hyper-V is enabled.

When using Pro, viboot works better in Hyper-V than virtualbox (in my tests).

So, I recommend you use Hyper-V in Pro, Virtualbox in Home.

If you really want to use virtualbox in Home, better to disable Hyper-V.
 

My Computer

System One

  • OS
    Windows 10 Pro + others in VHDs
    Computer type
    Laptop
    Manufacturer/Model
    ASUS Vivobook 14
    CPU
    I7
    Motherboard
    Yep, Laptop has one.
    Memory
    16 GB
    Graphics Card(s)
    Integrated Intel Iris XE
    Sound Card
    Realtek built in
    Monitor(s) Displays
    N/A
    Screen Resolution
    1920x1080
    Hard Drives
    1 TB Optane NVME SSD, 1 TB NVME SSD
    PSU
    Yep, got one
    Case
    Yep, got one
    Cooling
    Stella Artois
    Keyboard
    Built in
    Mouse
    Bluetooth , wired
    Internet Speed
    72 Mb/s :-(
    Browser
    Edge mostly
    Antivirus
    Defender
    Other Info
    TPM 2.0
Bear in mind, if you have Pro on PC and using Hyper-V, virtualbox and Hyper-v do not coexist that well.

Virtualbox is very slow if Hyper-V is enabled.

When using Pro, viboot works better in Hyper-V than virtualbox (in my tests).

So, I recommend you use Hyper-V in Pro, Virtualbox in Home.

If you really want to use virtualbox in Home, better to disable Hyper-V.
Wow! This machine came with Windows 10 Pro. I dual boot, and for some reason, I seem to have installed Windows 11 Home! :ffs::oops:

So, it seems I won't have to deal with Hyper-V since it's not available in my Windows 11 partition. I know there are ways to install Hyper-V in Windows 11 Home, but I'm not going there.

I've done my research and understand that I will need VirtualBox to create a virtual HDD/Desktop in this Home version.

I guess you could call this serendipity, since I'm in "the same boat" with my students. :)
 

My Computers

System One System Two

  • OS
    Windows 11 23H2 22631.2861
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP Envy TE01-1xxx
    CPU
    Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz 2.90 GHz
    Motherboard
    16.0GB Dual-Channel Unknown @ 1463MHz (21-21-21-47)
    Memory
    16384 MBytes
    Graphics Card(s)
    Intel UHD Graphics 630
    Sound Card
    Realtek High Definition Audio
    Monitor(s) Displays
    Monitor 1 - Acer 27" Monitor 2 - Acer 27"
    Screen Resolution
    1920 x 1080
    Hard Drives
    WDC PC SN530 SDBPNPZ-512G-1006 (SSD)
    Seagate ST1000DM003-1SB102
    Seagate BUP Slim SCSI Disk Device (SSD)
    PSU
    HP
    Case
    HP
    Cooling
    Standard
    Keyboard
    Logitech Wave K350
    Mouse
    Logitech M705
    Internet Speed
    500 mbps
    Browser
    Firefox
    Antivirus
    Windows Defender
    Other Info
    That's all Folks!
  • Operating System
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP
    CPU
    Intel Core i7 (10th gen) 10700
    Motherboard
    Intel
    Memory
    16 GB
    Graphics card(s)
    Intel UHD Graphics 630
    Sound Card
    Built-in
    Monitor(s) Displays
    Acer 27" & Samsung 24"
    Screen Resolution
    1920 x
    Hard Drives
    SSD (512 GB)
    HDD (1 TB)
    Seagate
    PSU
    Intel i7 10th Generation
    Case
    HP
    Cooling
    HP/Intel?
    Mouse
    Logitech M705
    Keyboard
    Logitech Wave K350
    Internet Speed
    50 mbps
    Browser
    Firefox 90.2
    Antivirus
    Windows Defender
    Other Info
    Headphone/Microphone Combo
    SuperSpeed USB Type-A (4 on front)
    HP 3-in-One Card Readr
    SuperSpeed USB Type-C
    DVD Writer
Wow! This machine came with Windows 10 Pro. I dual boot, and for some reason, I seem to have installed Windows 11 Home! :ffs::oops:

So, it seems I won't have to deal with Hyper-V since it's not available in my Windows 11 partition. I know there are ways to install Hyper-V in Windows 11 Home, but I'm not going there.

I've done my research and understand that I will need VirtualBox to create a virtual HDD/Desktop in this Home version.

I guess you could call this serendipity, since I'm in "the same boat" with my students. :)
It is a little known quirk that a Pro digital licence will activate Home, so it is not surprising you did not spot it.

I think you are ok by your serendipitious situation but I am not 100% certain if bios virtualisation settings will interfere but I don't think so. Only one way to find out ...
 

My Computer

System One

  • OS
    Windows 10 Pro + others in VHDs
    Computer type
    Laptop
    Manufacturer/Model
    ASUS Vivobook 14
    CPU
    I7
    Motherboard
    Yep, Laptop has one.
    Memory
    16 GB
    Graphics Card(s)
    Integrated Intel Iris XE
    Sound Card
    Realtek built in
    Monitor(s) Displays
    N/A
    Screen Resolution
    1920x1080
    Hard Drives
    1 TB Optane NVME SSD, 1 TB NVME SSD
    PSU
    Yep, got one
    Case
    Yep, got one
    Cooling
    Stella Artois
    Keyboard
    Built in
    Mouse
    Bluetooth , wired
    Internet Speed
    72 Mb/s :-(
    Browser
    Edge mostly
    Antivirus
    Defender
    Other Info
    TPM 2.0

Latest Support Threads

Back
Top Bottom