techsupport

Not entirely certain where the issue is coming from, but for most laptops the install should finish without all of the drivers just running in the included minimal set. If you can finish the install you should be able to do drivers after that and it should all be happy.

That said, an alternative is using a virtual machine. If you only use a few programs this may be a much more reliable and stable way to run Windows apps without messing with dual boot and drivers etc. The Virtualbox install is super easy and drivers are installed using the guest tools iso, so it is really simple to have fairly good graphics performance with limited overhead. You can also snapshot the image and have a known working state before updates, so if they gank something during the update you can just roll back and put off the update. Very handy for mission critical tools.

What i usually do nowadays when doing a fresh intall of windows is by using winNTsetup because it avoids too many steps if you have already decided to nuke the drive. You can download it from majorgeeks or have it preintalled on most portable windows like hirens, dlcboot or medicat.

Edit: oops my bad, sry, i got some bad reading comprehension, youre doing dual boot, ignore what i've said.

Dual boot is troublesome, even if you managed to make it work, it could mess your system, like for example, a windows update that could mess your grub partition thats why most people avoid it and use vm instead( qemu, vbox, etc.)

Jesus the comments are bad...

You need drivers. Specifically, you need the drivers for your internal disk (probably an NVMe), and/or the USB drivers. You also need to have them in a location where you can reach with Windows Setup. If it's the USB drivers you need, having them placed loose on the USB install drive won't help.

It's not a laptop thing, nor an Acer thing per se. But it is a hardware thing. Microsoft didn't include the drivers for your exact chips for whatever reason, probably because they were never submitted for approval.

In the end, you'll probably need to mount boot.wim (and likely install.wim) using DISM, add the drivers, then update the USB drive. I don't think you can do this without a functional Windows machine.

You might be about to get around some of this by trying different USB ports. Some might have different controllers, and thus need different drivers. This was very common when USB3 was new (e.g. USB2 were Intel and connected to the chipset, while USB3 was an add-on from Marvell and the like)

I recently had this exact issue when creating a bootable USB from the windows .iso under Linux mint.

The only fix was to use a windows PC and the windows media creation tool to create the USB drive.

Oh, I know this one! This occured when I made a bootable Windows USB on Linux. If you use Rufus to make the USB, it works. Rufus is Windows-only, sadly, so you'll need to vreate a Windows VM first.