Windows 10: Cart/Horse problem. Injecting drivers as boot critical.

Windows 10 Version 1909. Latest Public ADK a/o this post date.

In addition to the standard method of using dism to inject drivers to sysprep'd image, how does one 'promote' that driver to early boot or what MS used to call boot critical?

This for an iscsi project where I am attempting to patch and boot a sysprep'd image on unfamiliar hardware as an iscsi target. When I first boot a machine it loads generic ipxe driver stack to push winpe into ram (pixe/wimboot can inject drivers). Simultaneously the target iscsi image is available for dism edits by the winpe. I can in push network drivers to the iscsi mounted image but I don't understand how to promote them to early boot process.

Please feel free to correct terminology and dump lots of tech references with hyperlinks to MS training material. I am not asking for someone to do the work, I'm asking where to learn how to fix this.

--Below is just back story, it gets a bit rambly--

Before you say it's not possible, it is already possible in a round about ineffiecent way.

Presently I can boot a machine diskless to ipxe, load winpe, mount smb share, load windows 1909(if the winpe driver network driver patch worked). The problem here is the server is loading data from the server back to the server. So 16GB uniqe vhds per client machine. I get diskless clients but at an unoptimized storage cost.

If I can get this to work with sysprep'd vhd's as the base for my snapshots, I can save a ton of data. Each diskless client's vhd will only be the computer specific drivers etc existing as a differencing snapshot of the original.

Gotchas:
using ipxe with the wimboot module alllows me to dynamically alter the winpe on the fly. Scripts, drivers, it's awesome.
My dhcp server runs a script that per new client for this network it makes a new vhd, maps new vhd to iscsi iqn based on mac of client machine. The drive images are thin-provisioned so if they don't get used they take little space. However this system will run out of IQNs at 256 clients. Not that this server wouldn't implode from that kind of load, more like a reminder to clean out the fridge of old IQN targets and 1mb disk images never used. But this is assuming network isolation from production etc.

:)

 

Updated Shopping Cart and Wish List coming to the Microsoft Store

Source: Updated Shopping Cart and Wish List coming to the Microsoft Store - Xbox Wire

See also: Updated Shopping Cart and Wish List coming to the Microsoft Store - Windows Experience Blog


Tweet



— Twitter API (@user) View on Twiiter

 

Updated Shopping Cart and Wish List coming to the Microsoft Store

Source: Updated Shopping Cart and Wish List coming to the Microsoft Store - Xbox Wire

See also: Updated Shopping Cart and Wish List coming to the Microsoft Store - Windows Experience Blog

 

Critical Structure Corruption Windows 10

I keep getting this error "Critical Structure Corruption" and can't seem to fix it.

It happens while I am busy on my laptop. Here are some of the steps I have tried so far to resolve this with no success.

1. Ran Windows Memory Diagnostic = no problems so RAM looks good.
   
2. Check The CPU with Intel-Processor-Diagnostic-Tool = PASS all
   
3. Drivers update, I used driver booster and did need to update 18 drivers but was able to update with no issues.
   
4. Update software and drivers, well it was suggested that I update BlueStacks but the update failed, bluestacks mentioned that it might be an issue so as I do not use the tool I uninstalled the software altogether.
   
5. Updated Windows, this I do regularly and automatically so no big updates were missed.
   
6. Defragged the machine - system is optimized
   
7. Ran anti-virus check and all's good
   
8. Ran CCleaner
   

Now I might mention I'm not a super user, but I'm able to follow suggestions quite well.

Any help will be appreciated.

Screenshot: