Windows 11 24H2 / MicroWin 24.10.07 - After fresh install device manager shows "HelloFace" driver missing.

[cybrnook]

Describe the bug

After a vanilla MicroWin of 24H2 (no options modified other than default) using MicroWin 24.10.07, in device manager after the install it appears the drivers for Windows "HelloFace" are missing/broken.

To Reproduce

Build 24H2 with latest stable MicroWin and install.
Check device manager for missing/broken driver.

Expected behavior

Device Manager is clean, outside of drivers for your specific hardware being missing.

Screenshots

[CodingWonders]

@cybrnook, can you still register fingerprints or your face using Windows Hello?

[cybrnook]

Hello Face shows as unavailable/no camera found, which is incorrect. I have the Logitech BRIO 4K which does support Hello Face.

With that said, I am prepared to test the latest version of MicroWin the 11.11 version which I built last night. If you think that could be of benefit, I am prepared to do that before we go further if you want.

[CodingWonders]

@cybrnook, before trying newer versions, try following this guide

Especially, check if the Windows Biometric Service (WbioSrvc) is running and start it if it isn't

[cybrnook]

Still the same outcome unfortunately:

@CodingWonders let me know if there is anything else before we swing the sledge hammer and reinstall.

[CodingWonders]

Have you made sure the Windows Hello drivers for your hardware are installed? You may have to grab them from the computer manufacturer

If that doesn't work, try installing the latest version of your ISO.

Now, I can't test this, since my test machine is a VM, and that doesn't have Windows Hello-compatible hardware, obviously.

[cybrnook]

The motherboard is an Asus X670E ProArt, so there are no additional drivers needed.

With that said, two main items I want to call out:

1. Vanilla install of 24H2 works fine and I have no issues after the install as far as this feature is concerned.
2. I just reinstalled 24H2 using the latest 11.11 version of MicroWin, no options modified. Again the feature is broken in the final product.

I am quite certain it's MicroWin doing this when it's stripping features out during its rebuild.

[CodingWonders]

Can you show the screenshots of the biometric device on both installations? This is what I want:

Can you also verify if you have the system files listed in the 24H2 installation on the MicroWin one?

Note that I can't provide the true cause of the problem until more information is given because I don't have a Logitech BRIO and I use VMs for testing

[cybrnook]

So, I don't think it has anything to do with the camera as even doing a fresh install without the camera plugged into USB, the service HelloFace was still/already broken on first boot of 24H2.

However, with the said I went ahead and used the latest 11.11 dev build and used it to build with 23H2 (not 24H2), and the issue of the HelloFace feature being broken is no longer there. So it seems specific to MicroWin and 24H2 as I am not seeing the same issue with 23H2.

[Mark112887]

I would like to chime in with some information. I recently assembled a brand new system and was very eager to install Windows 11 Pro with your tool. I downloaded the latest ISO from Microsoft, and then I proceeded to let the latest public version of MicroWin do its thing and make the ISO for me, which I then copied to a USB flash drive with Rufus. Unfortunately for me, I didn't realize that Windows Hello was broken until I was well into the setup of my operating system. I have the same camera as OP These are the steps that I took to confirm that this issue was indeed with MicroWin. I imaged my system and then did a clean install with a fresh untouched version of Windows 11 Pro. Windows actually asked me at that point to set up Hello during the out-of-box experience. This made me curious, so I did another fresh install with MicroWin. This time with my camera plugged in during setup and it did not recognize my camera. The same issue was present. I didn't think to look in Device Manager, so I didn't see what the OP has posted, but it made me open a ticket with Logitech.  Ended up installing with World region to avoid as much as I could

[CodingWonders]

@Mark112887, did you use a Microsoft account for the regular 24H2 installation? Because I have a clue as to what may be wrong: the unattended answer file, which automatically creates a local account

[Mark112887]

@Mark112887, did you use a Microsoft account for the regular 24H2 installation? Because I have a clue as to what may be wrong: the unattended answer file, which automatically creates a local account

No sir, I used bypassnro to set up a local account on the official install. At no point did MicroWin allow me to set up my camera for Hello. I think I tried a fresh user account aswell, but I can't remember for sure

[CodingWonders]

@cybrnook, @Mark112887, one thing I noticed is that the functionality required for Windows Hello is disabled because of this Feature on Demand:

Try running the following command on the MicroWin install and see if it fixes it:

dism /online /add-capability /capabilityname=Hello.Face.20134~~~~0.0.1.0

Or, you can go to the "Optional features" page of Settings to add this one:

It will take a couple of minutes to install, and you will need to restart your computer

[Mark112887]

@cybrnook, @Mark112887, one thing I noticed is that the functionality required for Windows Hello is disabled because of this Feature on Demand:

Try running the following command on the MicroWin install and see if it fixes it:

dism /online /add-capability /capabilityname=Hello.Face.20134~~~~0.0.1.0

Or, you can go to the "Optional features" page of Settings to add this one:

It will take a couple of minutes to install, and you will need to restart your computer

After four separate clean installs of Windows, I have finally got my system up and running the way I like it with everything installed and organized and working perfectly. Unfortunately, I'm not going to be able to run this test, so hopefully when the OP sees this, he will be able to do what you are suggesting. It looks like you've pinpointed the problem. So hopefully that is in fact the solution.

[CodingWonders]

I provided a possible fix for this in #3066. Give it a whirl and see if the issue is fixed, @cybrnook

[cybrnook]

Adding the feature manually seemed to have not worked:

I will work on a reformat and report back.

@CodingWonders what's the easiest way for me to include your changes in your PR into an updated version of Winutil (MicroWin) so I can test it?

[CodingWonders]

You can do it in 2 ways. One is the easier way and the other one may be harder:

First way:

1. Clone my fork (here) by either using Git or downloading a ZIP version of that branch
2. Open PowerShell and run Compile.ps1

Second way:

1. Grab the latest pre-release of WinUtil by typing irm christitus.com/windev -OutFile winutil.ps1 on PowerShell. This is similar to what you would use, but without "iex"
2. Look at what has changed in the aforementioned PR and do a find/replace of what changed

[cybrnook]

Hmm, look okay?

[CodingWonders]

You can safely remove the .git folder. What matters is that the script is compiled

[cybrnook]

It did:

[CodingWonders]

Try doing the image now and come back with the results, then

[cybrnook]

Just some feedback as I am moving along, I assume it's known/not an issue that seems quite a few packages are not being removed during the build (24H2):

[CodingWonders]

@cybrnook, that is an older version of the script. Use the newest one

Try following the other method I talked about

[CodingWonders]

Just some feedback as I am moving along, I assume it's known/not an issue that seems quite a few packages are not being removed during the build (24H2):

Have you made sure you're in the correct branch? It's microwin-2025-preparation, not main

[cybrnook]

Rookie mistake, my apologies. Working on building the image now:

[CodingWonders]

No worries! Make your ISO with this branch and install it.

If the issue is fixed, do not close it. Wait for that PR to be merged. It will close this issue automatically once it's merged

[cybrnook]

I think we are okay. Device manager is clean post install after your recent changes.

Thanks for the quick follow up.

[CodingWonders]

@cybrnook, thanks for your feedback!