IRONFORCE

New Member
Joined
Aug 20, 2025
Messages
8
HELLO
I have MICROSOFT SURFACE BOOK 2 , i7 - 8 G Ram , WIN 11. I did fresh reset, all updates, download support pack 1.9 G and install it . for sign-in option with Hello FACE , it says : WE COULDN'T FIND COMPATIBLE CAMERA FOR WINDOWS HELLO . I checked device manager , there is an Uknown device , checked his proprieties , it says : ROOT/HELLOFACEFIRMWAREDRIVER. I did automatic driver update but windows says that he cant find the compatible driver . I contacted support with LIVE CHAT and QUICK ASSIST . The first agent CLYDE , reseted my device using a restore point ( that i made after the fresh windows install ) and the second agent JEANNIE destroyed my device ( installing / uninstalling / forced shut down / stuck with missing DLL file at startup / very complicate recovery / needed recovery key from website with sign-in and codes ... torture 😢). I searched everywhere for the compatible driver for the IR camera so i can activate the HELLO FACE without success . NB: the regular cam is working and filming normally. ANY HELP IS WELCOME .
THANK YOU
 

Hi — sorry you got stuck and had a rough support experience. I looked at your post and have a practical troubleshooting path you can follow to get the Windows Hello IR camera recognized (and what to post back here if you want me to keep helping). I’m citing a few community notes about Hello/camera issues as background. wnwing ROOT\HELLOFACEFIRMWAREDRIVER means Windows sees a device interface used by the Windows Hello/IR camera stack but no correct driver/firmware is installed. That’s why Settings > Sign‑in options reports “We couldn’t find a compatible camera”.
  • On newer Windows 11 builds there are extra security checks (Enrelated controls) that can block external/unsupported Hello devices — worth checking later if driver fixes don’t work.
Step‑by‑step troubleshooting (do these in order)
1) Get the hardware ID (post it heger, right‑click the Unknown device → Properties → Details → Property: Hardware Ids. Copy the full string(s) and paste them in your reply. That single bit of info often tells us the exact driver package needed.
2) Try the safe reinstall cycle
  • In Device Manager: right‑click the Unknown device → Uninstall device. If it asks, check “Delete the driver software for this device”.
  • From Device Manager menu choose Action → Scan for hardware changes (or restart).
  • If the device reappears as the same Unknown device, take the Hardware Ids (step 1) and post them here.
3) Run Windows repair + driver refresh
  • Open an elevated command prompt and run:
    • sfc /scannow
    • DISM /Online /Cleanup-Image /RestoreHealth
  • After those finish, check Windows Update → Optional updates → Driver updates. Install any camera/firmware updates and reboot. Community troubleshooting guidance often points to Windows Update / Optional drivers as the source of missing camera drivers.
4) Reinstall the Surface drivers & firmware package
  • The Surface Book 2 needs the official Surface driverrom Microsoft (the package is what contains the UEFI/IR camera firmware and device drivers). If you already installed a support pack, try re‑downloading the exact Surface Book 2 package for your model & Windows 11 build and reinstall it (run the included setup/driver installer). After installation, reboot and check Device Manager again.
  • If you’re not comfortable doing this, take a system image or full backup first. (If you tell me the exact Surface Book 2 SKU / model number I can point to the precise file name to look for.)
5) Check TPM / Security settings briefly
  • Windows Hello depends on TPM + certain platform security settings. Open tpm.msc to confirm TPM is present and enabled.
  • Also check Settings → Accounts → Sign‑in options → Additional settings for an option about “Sign in with an external camera or fingerprint reader” — on some recent Windows builds this must be toggled to allow external or non‑trusted Hello devices. If you see it, try toggling and rebooting.
6) Surface Diagnostic/Logs
  • If the drivers/firmware package doesn’t fix it, run the Surface Diagnostic Toolkit (Microsoft’s too problems) and collect the logs. If you post the log IDs or the Device Manager hardware IDs here I can look for the exact missing driver.
7) If camera works in apps but not Hello
  • You mentioned the regular camera is working for video — if regular camera apps work but Hello won’t enroll, that points to the IR/liveness portion specifically missing (firmware or Hello driver), not the ordinary camera driver. That again points to installing the Surface drivers/firmware package.
What I need from you to go further (post these)
  • The Hardware Id(s) from Device Manager → Details for the Unknown device (ROOT\HELLOFACEFIRMWAREDRIVElines).
  • The exact Surface Book 2 model number (e.g., “Surface Book 2 15-inch, Model XXXXX” — it’s on the bottom of the tablet or in Settings → System → About).
  • A quick screenshot of Device Manager showing the Unknown device (if you can attach).
A couple of warnings / tips
  • Before doing UEFI/firmware or driver package installs make a full backup or a system image. One of the things you described with support (broken recovery flow) is exactly why a backup/image is important.
  • If you allow remote support again, insist they create a restore point and/or full image and explain step changes before each major change.
If you paste the Hardware Ids and model here I’ll look up the exact driver/firmware name to download and give step‑by‑step install instructions. If you prefer, I can also give PowerShell commands to list Hello‑related devices (example: Get‑PnpDevice | Where‑Object InstanceId -Match 'HELLO|FACE') and tell you what to paste back.
 

HELLO
I have MICROSOFT SURFACE BOOK 2 , i7 - 8 G Ram , WIN 11. I did fresh reset, all updates, download support pack 1.9 G and install it . for sign-in option with Hello FACE , it says : WE COULDN'T FIND COMPATIBLE CAMERA FOR WINDOWS HELLO . I checked device manager , there is an Uknown device , checked his proprieties , it says : ROOT/HELLOFACEFIRMWAREDRIVER. I did automatic driver update but windows says that he cant find the compatible driver . I contacted support with LIVE CHAT and QUICK ASSIST . The first agent CLYDE , reseted my device using a restore point ( that i made after the fresh windows install ) and the second agent JEANNIE destroyed my device ( installing / uninstalling / forced shut down / stuck with missing DLL file at startup / very complicate recovery / needed recovery key from website with sign-in and codes ... torture 😢). I searched everywhere for the compatible driver for the IR camera so i can activate the HELLO FACE without success . NB: the regular cam is working and filming normally. ANY HELP IS WELCOME .
THANK YOU
 

HI
Thank you so much for your time and effort. I really appreciate the help so much. I did all the steps above but unfortunately no luck and got UNKNOWN DEVICE back after win repair , sorry for that . Couldn't find a log from SURFACE DIAGNOSTIC TOOL but Here is the info of computer and DEVICE ( photos):

COMPUTER:
  • Device information:
  • Device name: ADMIRAL
  • Serial number: 010446692757
  • Surface model: Surface Book Model 1832 i7
  • SAM: 182.2304.139.0
  • UEFI: 394.779.768.0
  • App version: 75.7170.133.0
  • BIOS Version/Date: Microsoft Corporation 394.779.768 08/11/2015
  • Touch driver: 242.0.1.5
  • Wi-Fi driver: 15.68.17022.122
  • Edition: Windows 11 Pro
  • OS build: 26100.4946
  • Processor: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
  • Installed RAM: 8 GB
  • Storage size: 159 GB free of 237 GB
  • GPU: Intel(R) UHD Graphics 620NVIDIA GeForce GTX 1050
  • Screen resolution: 3000 x 2000
DEVICE :
 

Attachments

  • IMG-20250827-WA0009.webp
    IMG-20250827-WA0009.webp
    203.4 KB · Views: 0
  • IMG-20250827-WA0007.webp
    IMG-20250827-WA0007.webp
    213.1 KB · Views: 0
  • IMG-20250827-WA0006.webp
    IMG-20250827-WA0006.webp
    310.9 KB · Views: 0
  • IMG-20250827-WA0005.webp
    IMG-20250827-WA0005.webp
    328.7 KB · Views: 0
  • IMG-20250827-WA0008.webp
    IMG-20250827-WA0008.webp
    955.8 KB · Views: 0
Thanks — this is very helpful. The screenshots and the Surface Book 2 model (1832) confirm we’re dealing with the Windows Hello face/IR firmware/driver interface being present but the kernel/driver package for the Hello IR/liveness stack isn’t installed (Device shows Root\WindowsHelloFaceSoftwareDriver / reported ID hash B332F155 and Problem code 0x1C / install error E0000228). That matches the common symptom where the regular camera works for video but the IR/liveness portion (Hello) is missing or blocked. a focused troubleshooting plan you can do now, ordered from least‑to‑most invasive. After each step, tell me the exact output (or paste screenshots) and I’ll tell you the next move.
What to try next (step‑by‑step)
1) Confirm the Hello-related PnP devices and collect IDs (quick, low risk)
  • Open an elevated PowerShell (right‑click Start → Windows Terminal (Admin)) and run:
    • Get-PnpDevice -PresentOnly | Where-Object InstanceId -Match 'HELLO|FACE'
    • Get-PnpDevice -InstanceId "Root\WindowsHelloFaceSoftwareDriver" (replace the InstanceId if your Device Manager shows a slightly different string)
  • Copy/paste the full text output here (or attach a screenshot). That confirms how Windows enumerates the device and gives the full InstanceId we need to find a matching driver package. If PowerShell returns nothing, run:
    • Get-PnpDevice -PresentOnly | Where-Object FriendlyName -Match 'camera|hello|face'
Why: we need the exact InstanceId/HWIDs to match an INF/driver. I can then search the Surface driver pack or INF files for that ID. If you prefer, paste the “Hardware Ids” text you already can see in Device Manager (Root\WindowsHelloFaceSoftwareDriver / B332F155).
2) Check whether Windows can enumerate the driver store (pnputil) and list installed driver packages
  • In elevated CMD run:
    • pnputil /enum-drivers
  • Also check driver store folder permissions:
    • icacls "C:\Windows\System32\DriverStore\FileRepository"
  • And count the driver repo folders:
    • dir /b "C:\Windows\System32\DriverStore\FileRepository" | find /v "" /c
Why: if pnputil can’t list drivers or the DriverStore ACLs are broken, Windows won’t match or install driver packages properly — that’s been the root cause in similar Surface/upgrade problems and we have safe fixes to try. If pnputil fails or returns errors, tell me the exact output (or paste it).
3) Re‑install the o drivers + firmware (the correct package)
  • Download & install the Surface Book 2 (Model 1832) driver+firmware pack from Microsoft’s Surface support site (the Surface driver pack contains UEFI/firmware + the IR/Hello drivers). After installing, reboot and check Device Manager again.
  • After installation, if Device Manager still shows the Unknown device, right‑click it → Update driver → Browse my computer for drivers → Let me pick from a list → Have Disk → point at the INF folder from the Surface package (usually inside the extracted package under Drivers or similar).
Why: the Hello/IR camera often requires firmware + a signed driver that's included in the Surface support pack; installing the complete package frequently restores the missing Hello device. If you already installed a support pack, repeat the install using the exact package for Model 1832 and your Windows 11 build (you mentioned OS build 26100.4946) — sometimes a package mismatch or failed install leaves Hello unbound.
4) Check the new Windows 11 “additional spresent)
  • Settings → Accounts → Sign‑in options → Additional settings → toggle “Sign in with an external camera or fingerprint reader” ON (if present), then reboot and retry Hello enrollment.
Why: on recent Windows builds an extra setting can prevent non‑trusted/external Hello devices from being used until explicitly allowed. It’s quick to check and has resolved similar cases.
5) If pnputil showed driver enumeration errors or DriverStore eset ACLs and recheck
  • Run (Admin CMD) to restore default ACLs for INF area:
    • secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose
  • Reboot and re-run the pnputil /enum-drivers command above.
Why: corrupted registry/file ACLs can stop Windows from enumerating or installing drivers. Restoring defaults frequently fixes driver‑store enumeration problems. If that step fixes pnputil, reinstall the Surface driver pack afterwards.
6) If nothing above works — capture diagnostic output (Surface Diagnostic Toolkit /ce Diagnostic Toolkit for Business (or the Surface Diagnostic) and save the logs. If you can’t find it, tell me and I’ll post exact filenames to look for. Those logs can show a failed INF installation or firmware flash error. If you have the toolkit output, paste the ID or log excerpts here and I’ll read them.
7) Hardware possibility and last resorts
  • If the driver package does not supply an INF that matches the rface Diagnostic logs show a firmware/board-level error, the IR sensor module (the Hello camera) may be failing or its internal firmware is corrupted. At that point the safe route is contacting Surface repair (provide your serial number — you included it) for hardware diagnosis or a firmware reflash from Microsoft. Back up your data first. If you want to try a hardware test before a service request I can give the exact commands to check kernel logs / event viewer entries to look for IR device firmware errors.
What I need from you now (paste these back here)
  • The exact output of pnputil /enum-drivers (copy/paste from Admin CMD) or a screenshot.
  • The Get‑PnpDevice output for Hello/Face devices (PowerShell copy/paste).
  • Confirm whether you reinstalled the Surface Bver+firmware pack since your last reset and, if yes, whether the installer rep you want, paste the outputs directly into your next reply and I’ll parse them and give the exact INF/driver file to install (and the exact Device Manager “Have Disk” pI can also give the exact PowerShell/CMD commands as a single copy/paste block you can run and then paste the whole result.
Short summary / tl;dr
  • Device Manager shows the Windows Hello face interface present but no compatible Hello driver/firmware is bound (Root\WindowsHelloFaceSoftwareDriver / B332F155 / E0000228). This means the IR/liveness driver/firmware is missing, mismatched, or blocked.
  • First actions: collect exact PnP IDs and pnputil output, install the official Surface Book 2 (Model 1832) driver+firmware package, check the extra sign‑in setting in Windows 11. If pnputilappear, restore DriverStore ACLs then repeat.
You’re not alone here — this is a common Surface Hello symptom after resets/driver mismatches. Paste the pnputil/Get‑PnpDevice outputs and I’ll locate the exact INF or tell you whether this looks like a hardware failure that needs service.
 

1-
Status Class FriendlyName
------ ----- ------------
OK Firmware Surface Base 2 Firmware Update
OK System Surface Keyboard Backlight
OK Computer Microsoft Corporation Surface Book 2
OK System Surface Dial Detection
Error
OK System Surface Pen Pairing
OK System Surface USB Hub Firmware Update
OK System Surface Power Meter
-
Get-PnpDevice : No Win32_PnPEntity objects found with property 'DeviceId' equal to
'Root\WindowsHelloFaceSoftwareDriver'. Verify the value of the property and retry.
At line:1 char:1
+ Get-PnpDevice -InstanceId "Root\WindowsHelloFaceSoftwareDriver"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Root\WindowsHelloFaceSoftwareDriver:String) [Get
-PnpDevice], CimJobException
+ FullyQualifiedErrorId : CmdletizationQuery_NotFound_DeviceId,Get-PnpDevice
-
Status Class FriendlyName
------ ----- ------------
OK Firmware Surface Touch
OK System Surface Display Color
OK System Surface Integration Service
OK Firmware Surface Base 2 Firmware Update
OK System Surface Touch Servicing ML
OK HIDClass Surface1832DigitizerIntegration Device
OK System Surface Keyboard Backlight
OK Monitor Surface Display
OK System Microsoft Camera Rear
OK Computer Microsoft Corporation Surface Book 2
OK System Microsoft IR Camera Front
OK System Surface Dial Detection
OK Firmware Surface ME
OK HIDClass Surface Pen Settings
OK System Surface Storage Firmware Update
OK Firmware Surface UEFI
OK System Surface Radio Monitor
OK System Surface Pen Pairing
OK USB Surface Ucsi Device
OK System Surface Serial Hub Driver
OK System Surface System Telemetry
OK System Surface Button
OK Firmware Surface System Aggregator
OK Camera Intel(R) AVStream Camera 2500
OK System Surface USB Hub Firmware Update
OK System Surface ACPI Notify Driver
OK HIDClass Surface Base 2 Integration
OK System Surface Integration
OK System Surface Power Meter
OK System Surface Hot Plug
OK Firmware Surface Integrated Sensor Hub
OK SoftwareDevice IntelIRCameraSensorGroup
OK System Intel(R) Management Engine Interface #1
OK System Microsoft Camera Front
OK System Surface DTX
OK Bluetooth Surface Pen
 

Thanks — the output is very useful. Good news: Device Manager / your PowerShell run shows the camera pieces are present (Intel(R) AVStream Camera 2500, Microsoft IR Camera Front and an IntelIRCameraSensorGroup software device), which says the hardware and the AVStream camera driver are visible — but the Windows Hello liveness/HelloFace driver still isn’t bound, which is why Settings shows “We couldn’t find a compatible camera.” That exact symptom and the safe checklist I recommended earlier are described in the thread I pulled from your case. (short)
  • The normal camera stack is present (so video apps work).
  • The Windows Hello IR/liveness driver (the WindowsHelloFace driver) is not installed or not binding to the Hello interface, so Hello enrollment fails. That matches the Root\WindowsHelloFaceSoftwareDriver / B332F155 / install error symptoms we saw earlier.
Next steps — pleasethem from lowest‑risk → next diagnostic steps). After each command, copy/paste the exact output (or attach a screenshot) and I’ll tell you the next move.
A — Quick checks (very low risk)
1) Confirm the exact camera PnP list (paste the full output)
  • Open Windows Terminal (Admin) and run (copy/paste everything it returns):
    • PowerShell:
      Get-PnpDevice | Where-Object { $_.FriendlyName -match 'Camera|IR|Intel|Hello|Face' } | Format-Table Status,Class,FriendlyName,InstanceId -AutoSize
  • Paste the full output here. That shows every camera/Hello related device and its InstanceId.
2) Inspect the IR camera driver details (a quick GUI check)
  • Device Manager → find Microsoft IR Camera Front → Right‑click → Properties → Driver tab → click Driver Details and copy the Provider and Driver File names (or screenshot). This helps us see which INF/driver is in use for the IR camera.
B — Check driver store & installed packages (needed if driver binding is failing)
1) Run pnputil to list driver packages (this tells us whether the Hello driver package exists in the driver store)
  • Open Command Prompt (Admin) and run:
    • pnputil /enum-drivers
  • Save or paste the output here (if it’s long, just paste any oem*.inf lines that look camera/hello/ir related). If pnputil errors or prints nothing, tell me the exact text — that points to a DriverStore/ACL problem we can fix. (If you prefer, redirect to a file and upload it: pnputil /enum-drivers > C:\Users\Public\pnputil.txt)
Why we run pnputil: if Windows has the Hello/IR INF in the store it should list it; if it’s missing the INF or the driver store can’t be enumerated, Windows cannot bind the Hello device. This issue and the pnputil check are in the same checklist I referenced earlier.
C — Quick security check that often blocore Isolation / Memory Integrity
  • Settings → Privacy & security → Device security → Core isolation details → turn Memory integrity OFF (if currently ON). Reboot after changing.
  • Why: Memory integrity (HVCI) can block old/unsigned kernel drivers from loading; temporarily disabling it is a common troubleshooting step. If you change this, tell me whether it was on or off and then re-check Device Manager / Sign‑in options. (We can re-enable it later once the correct signed drivers are installed.)
D — Reinstall the official Surface Book 2 driver + firmware package (model 1832)
  • Download the correct Surface Book 2 (Model 1832) Drivers + Firmware package from Microsoft’s Surface support page and install the package (run the .msi as Administrator), then reboot. If you already did this once, reinstall it again — sometimes the firmware/driver flash fails silently and a second run fixes the Hello binding. I recommended this earlier as a required step for the Hello/IR portion.
  • IMPORTANT: backup / create a system image before applying fierruptible power and AC connected). If you want step‑by‑step imaging instructions first (Macrium/AOMEI), tell me — I gave a short backup checklist previously.
E — If driver still won’t bind: collect logs
1) Event Viewer check (copy errors)
-Windows Logs → System. Filter on Critical / Error for the last boot and look for entries mentioning Camera, Hello, HelloFace, or firmware. Copy the messages/timestamps here.
2) Surface Diagnostic Toolkit
  • Run the Surface Diagnostic Toolkit (Surface Diagnostic for Business) and collect the generated log ID or zip. If you can’t find logs, tell me and I’ll post the exact filenames to look for. The toolkit output often includes a failed driver/firmware install entry we can act on. (If you need the direct step list to run it, say so.)
F — If pnputil fails to list drivers / DriverStore ACLs look broken
  • I’ll walk you through a safe ACL/DriverStore repair (secedit restore of default INF ACLs and attempt to re‑enumerate pnputil). That’s a bit more advanced but I’ll give exact commands to run if we see an access error from pnputil. This is one of the targeted fixes I mentioned earlier if driver enumeration is the blocker.
What I need from you now
  1. Paste the full output of:
    • Get-PnpDevice | Where-Object { $_.FriendlyNaIntel|Hello|Face' } | Format-Table Status,Class,FriendlyName,InstanceId -AutoSize
    • pnputil /enum-drivers (or tell me if pnputil returns an error)
  2. Tell me whether Core Isolation / Memory integrity was ON or OFF and, if ON, temporarily switch it OFF and reboot then re‑check Sign‑in options.
  3. Confirm whether you’ll reinstall the Surface Book 2 (1832) Drivers + Firmware package now (I’ll give the exact filename to download if you want) — and confirm you have a backup or are willing to make one before firmware steps.
If you paste the Get-PnpDevice + pnputil outputs I’ll parse them and either:
  • give the exact INF name to install with “Have Disk” (if the INF exists in the Surface package), or
  • walk you through the DriverStore ACL fix and reinstall sequence, or
  • if logs show a firmware/module failure, we’ll prepare a Surface service request (you already included the serial so that will speed it up).
You’re very close — the OS can see the IR camera components, we just need to get the correct Hello driver/firmware bound (or remove whatever is blocking binding). Paste the outputs and I’ll take it from there.
 

Status Class FriendlyName
------ ----- ------------
OK Firmware Surface Touch
OK System Surface Display Color
OK System Surface Integration Service
OK System Intel(R) Serial IO I2C Host Controller - 9D61
OK Firmware Surface Base 2 Firmware Update
Unknown HIDClass Surface Pen Integration Device
OK MEDIA Intel(R) Display Audio
OK System Intel(R) Dynamic Platform and Thermal Framework Manager
OK System Surface Touch Servicing ML
OK System Intel(R) Control Logic
OK System Intel(R) Control Logic
OK System Intel(R) Control Logic
OK HIDClass Surface1832DigitizerIntegration Device
Unknown HIDClass Surface Dock Integration
OK System Surface Keyboard Backlight
OK Monitor Surface Display
OK System Microsoft Camera Rear
OK Computer Microsoft Corporation Surface Book 2
OK System Intel(R) Serial IO UART Host Controller - 9D27
OK System Microsoft IR Camera Front
OK HIDClass Virtual HID Framework (VHF) HID device
OK System Microsoft Hyper-V Virtualization Infrastructure Driver
OK System Surface Dial Detection
OK Firmware Surface ME
OK HIDClass Surface Pen Settings
OK System Microsoft Virtual Drive Enumerator
OK System Surface Storage Firmware Update
OK System Intel(R) Serial IO I2C Host Controller - 9D63
OK Firmware Surface UEFI
OK System Intel(R) Integrated Sensor Solution
OK System Surface Radio Monitor
OK System Mobile 6th/7th Generation Intel(R) Processor Family I/O PMC - 9D21
OK System Intel(R) Serial IO I2C Host Controller - 9D60
OK System Intel(R) Dynamic Platform and Thermal Framework Generic Participant
OK SoftwareComponent Intel(R) iCLS Client
OK System Mobile 6th/7th Generation Intel(R) Processor Family I/O PCI Express...
OK System Intel(R) Smart Sound Technology (Intel(R) SST) Audio Controller
OK System Intel(R) CSI2 Host Controller
OK System Surface Pen Pairing
OK USB Surface Ucsi Device
OK System Intel(R) Serial IO GPIO Host Controller - INT344B
OK System Intel(R) Xeon(R) E3 - 1200 v6/7th Gen Intel(R) Core(TM) Host Bridge...
Unknown System Surface Dock Firmware Update
OK USB Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
OK HIDClass Virtual HID Framework (VHF) HID device
Unknown Net Surface Ethernet Adapter
OK System Surface Serial Hub Driver
OK System Mobile 6th/7th Generation Intel(R) Processor Family I/O SMBUS - 9D23
OK System Surface System Telemetry
OK System Surface Button
OK Firmware Surface System Aggregator
OK System Intel(R) Serial IO I2C Host Controller - 9D62
OK Camera Intel(R) AVStream Camera 2500
OK System Intel(R) Power Engine Plug-in
OK System Intel(R) Dynamic Platform and Thermal Framework Power Participant
OK System Surface USB Hub Firmware Update
OK System Surface ACPI Notify Driver
OK Display Intel(R) UHD Graphics 620
OK HIDClass Surface Base 2 Integration
OK System Intel(R) Dynamic Platform and Thermal Framework Processor Participant
OK HIDClass Intel(R) Precise Touch Device
OK System Intel(R) Imaging Signal Processor 2500
OK System Surface Integration
OK System NDIS Virtual Network Adapter Enumerator
Unknown System Surface Pen Firmware Update
OK System Mobile 6th/7th Generation Intel(R) Processor Family I/O Thermal sub...
OK System Surface Power Meter
OK System Mobile 7th Generation Intel(R) Processor Family I/O LPC Controller ...
OK System Surface Hot Plug
OK Firmware Surface Integrated Sensor Hub
OK Net Microsoft Wi-Fi Direct Virtual Adapter
OK Net Microsoft Wi-Fi Direct Virtual Adapter #2
OK SoftwareDevice IntelIRCameraSensorGroup
OK System Intel(R) Management Engine Interface #1
OK Processor Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
OK Processor Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
OK Processor Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
OK Processor Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
OK Processor Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
OK Processor Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
OK Processor Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
OK Processor Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
OK System Microsoft Camera Front
OK System Surface DTX
OK System Mobile 6th/7th Generation Intel(R) Processor Family I/O PCI Express...
OK Net Marvell AVASTAR Wireless-AC Network Controller
OK System Remote Desktop Device Redirector Bus
OK System Intel(R) Smart Sound Technology (Intel(R) SST) OED
OK SoftwareComponent Intel(R) Management Engine WMI Provider
OK System Intel(R) Dynamic Platform and Thermal Framework Generic Participant
OK System Intel(R) Dynamic Platform and Thermal Framework Generic Participant
OK System Intel(R) Dynamic Platform and Thermal Framework Generic Participant
OK System Intel(R) Dynamic Platform and Thermal Framework Generic Participant
OK System Intel(R) Dynamic Platform and Thermal Framework Generic Participant
OK System Intel(R) Dynamic Platform and Thermal Framework Generic Participant
OK Bluetooth Surface Pen
OK System Mobile 6th/7th Generation Intel(R) Processor Family I/O PCI Express...
 

Good — thanks, that output confirms the normal camera stack (Intel(R) AVStream Camera 2500, Microsoft IR Camera Front and the IntelIRCameraSensorGroup software device) is present, which tells us the hardware + AVStream driver are visible. The problem is that the Windows Hello “liveness/HelloFace” driver still isn’t binding — so Settings correctly reports “We couldn’t find a compatible camera.” hands to run (lowest risk → diagnostic). Please copy/paste the full text output from each command back here (don’t paraphrase) and I’ll parse it and tell you the precise next step.
1) Tell me the installed camera/Hello PnP entries (already helpful — run this)
  • Open Windows Terminal as Administrator and run:
    Get-PnpDevice | Where-Object { $_.FriendlyName -match 'Camera|IR|Intel|Hello|Face' } | Format-Table Status,Class,FriendlyName,InstanceId -AutoSize
  • Paste the full output here.
2) Show which signed driver package(s) exist in the driver store
  • Open Command Prompt as Administrator and run:
    pnputil /enum-drivers > C:\Users\Public\pnputil.txt && notepad C:\Users\Public\pnputil.txt
  • This will open the full pnputil output in Notepad. Copy & paste the parts that mention camera, ir, hello, or any oem*.inf entries that look related (paste the whole file if you can). If pnputil errors, paste the exact error text — that's useful (it indicates a DriverStore/ACL issue). (I asked for pnputil earlier because if the Hello INF exists in the store we can install it; if the driver store can’t be enumerated we will repair ACLs first).
3) Find any INF in the DriverStore/INF f Hello/WindowsHello/face
  • In Admin CMD run:
    findstr /S /M /I "hello windowshello face" "%windir%\inf*.inf"
    findstr /S /M /I "hello windowshello face" "%windir%\System32\DriverStore\FileRepository*.inf"
  • If anything is returned, paste the full filenames here (that tells us whether the Hello/HelloFace INF is present).
4) Get PnP signed-driver details for camera devices (INF name / provider / version)
  • In an elevated PowerShell run (one command):
    Get-CimInstance Win32PnPSignedDriver | Where-Object { $.DeviceName -match 'IR Camera|AVStream Camera|IntelIR' } | Select-Object DeviceName,Manufacturer,DriverVersion,InfName | Format-Table -AutoSize
  • Paste the full output.
5) Quick security check that often blocks drivers
  • Open Settings → Privacy & security → Device security → Core isolation details → note whether “Memory integrity” is ON or OFF.
    • If ON: temporarily switch Memory integrity to OFF, reboot, then re-check Settings → Accounts → Sign‑in options (try to Set up Face recognition again) and paste what changed.
  • Also go to Settings → Accounts → Sign‑in options → Additional settings and look for “Sign in with an external camera or fingerprint reader” — if it exists, toggle it ON and reboot, then try Hello again. Report whether the option exists and its state.
6) Reinstall official Surface drivers & firmware (if you haven’t yet, or even if you have — do it again)
  • From Microsoft’s “Download drivers and firmware for Surface” page, get the Surface Book 2 (model 1832) driver+firmware pack and run the included installer (Right‑click → Run as administrator) and reboot when asked. If you want I can give the exact filename to look for — tell me whether you want me to post the link and I’ll point to the official Microsoft package.
  • Important: do this on AC power and with a backup (create a system image or at least a restore point if you haven’t already). Re‑running the official Surface package often completes a firmware/driver bind that failed silently the first time.
If after these steps the Hello driver still doesn’t bind, we’ things depending on results:
  • If pnputil failed / DriverStore can’t be enumerated: I’ll give the exact, safe commands to restore default INF ACLs (secedit) and then re-run pnputil and reinstall the Surface package. That fixes driver-store enumeration issues in many cases.
  • If the Surface package shows a firmware/flash failure in the toolkit logs or Even to either a firmware corruption or a failing IR module — at that point we’ll prepare a targeted Surface service request (your serial number is handy) or walk through extraction of diagnostic logs so you can open a support case with Microsoft for a firmware reflash / hardware repair.
One useful temporary workaround while we fix this: enroll a PIN (if you don’t already) and keep using the front camera for video — that avoids any work stoppage until we resolve Hello.
What I need now
  • Paste the outputs of commands in steps 1, 2 (pnputil file), 3 (findstr), and 4 (Get-CimInstance).
  • Tell me whether Memory integrity was ON or OFF and whether the “Sign in with an external camera…” setting exists.
  • Tell me whether you want the exact Surface package download filename/link and whether you have an external backup drive (to make an image before firmware flashes).
Once you paste the command outputs I’ll analyze them and either point to the exact INF to install or give the DriverStore ACL repair + reinstall sequence. You’re very close — the camera hardware shows up, we just need to bind the Hello liveness driver or repair the driver store that’s preventing it.
 

Log Name: System
Source: Microsoft-Windows-WindowsUpdateClient
Date: 8/27/2025 1:08:18 AM
Event ID: 44
Task Category: Windows Update Agent
Level: Information
Keywords: Started,Download
User: SYSTEM
Computer: ADMIRAL
Description:
Windows Update started downloading an update.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WindowsUpdateClient" Guid="{945a8954-c147-4acd-923f-40c45405a658}" />
<EventID>44</EventID>
<Version>1</Version>
<Level>4</Level>
<Task>1</Task>
<Opcode>12</Opcode>
<Keywords>0x8000000000002004</Keywords>
<TimeCreated SystemTime="2025-08-27T00:08:18.8288465Z" />
<EventRecordID>5599</EventRecordID>
<Correlation />
<Execution ProcessID="3248" ThreadID="3260" />
<Channel>System</Channel>
<Computer>ADMIRAL</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="updateTitle">Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.435.410.0) - Current Channel (Broad)</Data>
<Data Name="updateGuid">{1d7756ca-df42-484a-9685-1488c9468540}</Data>
<Data Name="updateRevisionNumber">200</Data>
</EventData>
</Event>
 

Thanks — that Windows Update event is just a Defender definition download (not related to Hello). Good news from your device list: the AVStream camera, Microsoft IR Camera Front and IntelIRCameraSensorGroup are present — that shows the hardware and camera driver exist. The remaining problem is that the Windows Hello “HelloFace” liveness driver/INF isn’t binding to the Hello interface (so Settings says “We couldn’t find a compatible camera”). That matches the DriverStore/driver‑binding symptoms we’ve been tracking. two short notes:
  • If Memory integrity (Core isolation) is enabled it sometimes blocks kernel drivers from loading — we’ll check that below.
  • The safest/most reliable fix is to reinstall the official Surface Book 2 drivers+firmware package (Model 1832). If we need to, we’ll also repair DriverStore ACLs so Windows can enumerate and bind drivers.
What I need you to mmand output here). Do them in order.
1) Turn OFF Memory integrity temporarily (GUI)
  • Settings → Privacy & security → Device security → Core isolation details → toggle Memory integrity to Off (if it’s On). Reboot if you change it.
  • Tell me whether it was On or Off and whether you toggled it.
2) Dump the driver store listing (Admin CMD)
  • Run (as Administrator):
    pnputil /enum-drivers > C:\Users\Public\pnputil.txt && notepad C:\Users\Public\pnputil.txt
  • Paste here any oem*.inf entries that mention camera, ir, hello, intel, avstream, or anything that looks like Surface/IR.
Why: this shows whether the Hello/IR INF exists in the store or whether DriverStore enumeration is failing. If pnputil gives an error, paste the exact error text.
3) Search for any Hello/Face INF text (Admin CMD)
  • Run:
    findstr /S /I /M "hello windowshello face helloFace" "%windir%\inf*.inf"
    findstr /S /I /M "hello windowshello face helloFace" "%windir%\System32\DriverStore\FileRepository*.inf"
  • Paste any file paths returned. If nothing returns, say so.
4) List installed signed drivers for camera devices (Admin PowerShell)
  • Run:
    Get-CimInstance Win32PnPSignedDriver | Where-Object { $.DeviceName -match 'IR Camera|AVStream Camera|IntelIR|Windows Hello|Hello|Face' } | Select-Object DeviceName,Manufacturer,DriverVersion,InfName | Format-Table -AutoSize
  • Paste the full output.
5) Re-run the camera/Hello PnP device list (Admin PowerShell)
  • Run:
    Get-PnpDevice -PresentOnly | Where-Object { $_.FriendlyName -match 'Camera|IR|Intel|Hello|Face' } | Format-Table Status,Class,FriendlyName,InstanceId -AutoSize
  • Paste the full output.
6) Collect recent PnP / driver install errors from System (Admin PowerShell — saves files you can open)
  • Run these two commands (they will save the last 48 hours of relevant events to text files):
    Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Microsoft-Windows-Kernel-PnP'; StartTime=(Get-Date).AddDays(-2)} | Select-Object TimeCreated,Id,LevelDisplayName,@{n='Message';e={$.Message}} | Out-File C:\Users\Public\PnpEvents.txt -Width 4096
    Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Microsoft-Windows-DriverFrameworks-UserMode'; StartTime=(Get-Date).AddDays(-2)} | Select-Object TimeCreated,Id,LevelDisplayName,@{n='Message';e={$
    .Message}} | Out-File C:\Users\Public\DFEvents.txt -Width 4096
  • Open those two files (C:\Users\Public\PnpEvents.txt and C:\Users\Public\DFEvents.txt) and paste any errors or anything that references Hello, HelloFace, IR, firmware, or oem*.inf.
7) Reinstall official Surface Book 2 drivers + firmware
  • If you haven’t yet (or even if you have), please download and run the official Surface Book 2 (Model 1832) Drivers & Firmware package from Microsoft’s Surface support page and run the included installer as Administrator. Do this on AC power and reboot after the installer finishes.
  • After reboot, re-run steps 2 and 5 above and paste outputs (pnputil and Get-PnpDevice). If the installer shows firmware flash failures, note the message.
8) If you find a matching INF (oemXX.inf) or an INF filename in step 4 or 3
  • I’ll give you an exact command to install it (pnputil /add-driver "fullpath\oemXX.inf" /install) and we’ll force Windows to bind the Hello driver.
What I’ll do after you paste the outputs
  • If pnputil shows the Hello INF in the store: I’ll give the exact pnputil /add-driver or pnputil /install command to bind it.
  • If pnputil fails or shows enumeration/access errors: I’ll give safe commands to restore default INF ACLs (secedit /configure ...) and re-run pnputil so Windows can enumerate/install drivers again.
  • If the Surface package fails a firmwarfirmware/board errors: we’ll prepare the Surface Diagnostic Toolkit logs and escalate to Microsoft service (your serial is handy) — I’ll show exactly what to include.
If you prefer I can also (A) paste the exact Surface package filename to download from Microsoft, or (B) produce a single copy/paste script (PowerShell & CMD) that runs steps 2–6 and writes the outputs to text files you can paste here. Which do you prefer?
Finally — quick reassurance: you’ve got the right pieces visible (Intel AVStream camera, IR camera, IntelIRCameraSensorGroup). Most cases are fixed either by installing the correct Surface INF/firmware package or repairing driver‑store enumeration; we’ll proceed carefully and I’ll walk you through each step.
 

Log Name: System
Source: Microsoft-Windows-DriverFrameworks-UserMode
Date: 8/26/2025 12:12:11 AM
Event ID: 10116
Task Category: User-mode Driver problems.
Level: Critical
Keywords:
User: SYSTEM
Computer: ADMIRAL
Description:
The device Surface Base 2 Firmware Update (location 1) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DriverFrameworks-UserMode" Guid="{2e35aaeb-857f-4beb-a418-2e6c0e54d988}" />
<EventID>10116</EventID>
<Version>1</Version>
<Level>1</Level>
<Task>64</Task>
<Opcode>0</Opcode>
<Keywords>0x2000000000000000</Keywords>
<TimeCreated SystemTime="2025-08-25T23:12:11.5965267Z" />
<EventRecordID>4199</EventRecordID>
<Correlation />
<Execution ProcessID="1248" ThreadID="1400" />
<Channel>System</Channel>
<Computer>ADMIRAL</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<UmdfDeviceOffline xmlns="http://www.microsoft.com/DriverFrameworks/UserMode/Event">
<LifetimeId>{0d96eb4a-dcce-43d2-867e-635590b20c6e}</LifetimeId>
<FriendlyName>Surface Base 2 Firmware Update</FriendlyName>
<Location>1</Location>
<InstanceId>{5E9A8CDC-14AB-4609-A017-68BCE594AB68}\SURFACEBASE2FWUPDATE\8&amp;E8C1F96&amp;0&amp;1</InstanceId>
<RestartCount>1</RestartCount>
</UmdfDeviceOffline>
</UserData>
</Event>
 

Thanks — that DriverFrameworks User‑Mode critical event (Event ID 10116) is an important clue: it shows the Surface Base 2 firmware update process crashed while running in user mode, which can leave the firmware/driver partially applied and the Hello/IR driver unbound. In plain terms: Windows can see the AVStream camera and the IR camera software device, but the Hello “liveness” driver/firmware binding is not finishing because the Surface firmware update/driver process crashed. That’s why Settings says “We couldn’t find a compatible camera.” ordered, safe checklist you can run (low → higher risk). Do them exactly in order, paste the indicated outputs back here, and I’ll interpret them and give the precise follow‑ups (including the exact pnputil or pnputil /add‑driver line if the INF exists). Important: back up your data first (image or at least copy critical files), run firmware installs on AC power, and don’t interrupt a firmware flash.
Quick summary of what to do next
  • Check & temporarily disable Memory Integrity (Core isolation). This can block drivers from loading.
  • Confirm DriverSttil) and search for Hello/IR INFs. If DriverStore can’t enumerate, restore INF ACLs (secedit) then re-run pnputil.
  • Reinstall the official Surface Book 2 & Firmware package (run the MSI as Administrator). Reboot and re-check. Re‑running often completes a flash that failed silently.
  • Collect the relevant System logs (Kernel‑PnP and DriverFrad the pnputil output so we can pinpoint the failure code and take the precise action (bind INF, repair ACLs, or escalate to service).
Step‑by‑step (copy/paste the exact commands)
A — Very quick checks and backup
1) (Macrium, AOMEI, or copy critical files). Don’t skip this if you’ll reinstall firmware.
2) Check Memory Integrity (Core isolation)
  • Settings → Privacy & security → Device security → Core isolation details
  • If “Memory integrity” is ON, toggle it OFF, then reboot. (This is temporary for troubleshooting; you can re‑enable if driver installs succeed.) Memory integrity can prevent older kernel drivers from loading and is a common blocker for Hello drivers.
B — Collect PnP / driver store info (critical diagnostics)
Open an elevated Command Prompt (Run as Admiese:
1) Dump driver store list into a file (this shows whether the Hello/IR INF exists)
pnputil /enum-drivers > C:\Users\Public\pnputil.txt && notepad C:\Users\Public\pnputil.txt
  • After Notepad opens, search inside for strings: camera, ir, intel, avstream, hello, windowshello, helloFace, Surface. Paste any oem*.inf lines you find that look related.
2) Check driver‑store folder ACLs / count entries (in the same elevated CMD)
icacls "C:\Windows\System32\DriverStore\FileRepository"
dir /b "C:\Windows\System32\DriverStore\FileRepository" | find /v "" /c
  • If icacls shows ACCESS DENIED or odd ACLs, tell me the output — we’ll run the safe secedit ACL restore next. Issues here explain why Windows can’t bind drivers.
3) Search installed INF files for Hello/Face strings (optional; useful)
findstr /S /M /I "hello windowshello helloface face"
findstr /S /M /I "hello windowshello helloface face" "%windir%\System32\DriverStore\FileRepository*.inf"
  • Paste any full filenames returned (or “none”).
4) List currently installed camera drivers (shows InfName/provider/version)
Open an elevated PowerShell and run:
Get-CimInstance Win32PnPSignedDriver | Where-Object { $.DeviceName -match 'IR Camera|AVStream Camera|IntelIR|Windows Hello|Hello|Face' } | Select-Object DeviceName,Manufacturer,DriverVersion,InfName | Format-Table -AutoSize
  • Paste the full output.
5) Enumerate Hello/camera PnP devices (confirm InstanceIds)
In elevated PowerShell:
Get-PnpDevice -PresentOnly | Where-Object { $_.FriendlyName -match 'Camera|IR|Intel|Hello|Face' } | Format-Table Status,Class,FriendlyName,InstanceId -AutoSize
  • Paste the full output.
C — Collect System event logs that matter (Kernel‑PnP & DriverFrameworks)
Run these (admin PowerShell) — they’ll save the last 48 hours of PnP and DriverFrameworks events into files you can open:
Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Microsoft-Windows-Kernel-PnP'; StartTime=(Get-Date).AddDays(-2)} | Select-Object TimeCreated,Id,LevelDisplayName,Message | Out-File C:\Users\Public\PnpEvents.txt -Width 4096
Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Microsoft-Windows-DriverFrameworks-UserMode'; StartTime=(Get-Date).AddDays(-2)} | Select-Object TimeCreated,Id,LevelDisplayName,Message | Out-File C:\Users\Public\DFEvents.txt -Width 4096
  • Open both files (C:\Users\Public\PnpEvents.txt and C:\Users\Public\DFEvents.txt) in Notepad and paste any ERROR/CRITICAL lines that reference Hello, HelloFace, IR, firmware, Surface, or oem*.inf. The DFEvents.txt will include the 10116 messages you pasted; those help tell us whether the firmware flash crashed or a user-mode driver crashed repeatedly. The message you supplied (Surface Base 2 Firmware Update offline due to user-mode driver crash) is exactly the sort of entry I expect to see in DFEvents.txt. That event often indicates the firmware/driver process failed and needs to be re‑run or escalated.
D — Repair driver store ACLs (only if pnputil failed/ACCESS DENIED)
If pnputil failed to enumerate drivers or icacls showed odd ACLs, run (Admin gure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose
(reboot)
then re-run pnputil /enum-drivers and paste the resulting C:\Users\Public\pnputil.txt output again.
  • This restore of default INF ACLs is a standard, safe repair that often fixes driver‑store enumeration issues so Windows can bind drivers.
E — Reinstall Surface Book 2 Drivers & Firmware package (Model 1832)
  • Download the official Surface Book 2 (Model 1832) Drivers & Firmware package from Microsoft’s Ssearch “Surface Book 2 drivers and firmware Model 1832” on Microsoft’s site). Unzip and run the included Surface_Drivers_xxx.msi as Administrator. Reboot when the installer asks. Do this on AC power and after a backup. Re‑running this package often finishes a firmware/driver bind that failed earlier and will add the HelloFace INF into the driver store if it’s missing.
After the installer finishes and you reboot:
  • Re-run pnputil /enum-drivers and Get-PnpDevice commands from above and paste the outputs here.
  • If the installer reports a firmware flash f Diagnostic Toolkit reports a failed step, copy that error text — it tells us whether this is a software/driver problem or a firmware/hardware problem.
F — If the Hello driver INF exists in the store but isn’t bound
If you find an oemXX.inf in pnputil that looks like the Hello/IR INF (I’ll help identify it), we will run:
pnputil /add-driver "C:\full\path\to\oemXX.inf" /install
That forces Windows to install and bind that driver to matching devices.
G — If firmware update repeatedly crashes (DF event 10116 still appears)
  • Run the Surface Diagnostic for Business tool (Surface Diagnostic Toolkit) and save/export the logs. If the toolkit shows a failed firmware step for the Surface Base 2 firmware update, this often requires Microsoft/Surface service to reflash the module or provide a corrected firmware — that’s when we escalate to repair/service. If we go that route I’ll tell you exactly which logs/screenshots and the brief description to include in a Microsoft support case (having your serial already listed helps).
What I need from you to proceed right now
1) Tell me whether Memory integrity was ON or OFF and, if ON, toggle it OFF and reboot. Then re‑check Settings → Sign‑in options.
2) Run the pnputil command and opputil.txt; paste any oem*.inf lines that reference camera, ir, hello, Surface, Intel, AVStream, or similar.
3) Paste the contents (ERROR/CRITICAL lines) from C:\Users\Publreference Surface Base 2 Firmware Update (Event ID 10116) or other firmware/driver crashes; also paste any Kernel‑PnP errors from C:\Users\Public\PnpEvents.txt.
4 will re‑run the Surface Book 2 driver+firmware MSI now (and confirm you have AC power and a backup).
If we find the INF in the driver store I’ll give the exact pnputil add‑driver command and, if necessary, a short manual “Have Disk” procedure toevice Manager. If DriverStore enumeration is broken we’ll run the secedit ACL repair and then reinstall the Surface package. Ifails repeatedly and logs show user‑mode driver crashes, we’ll prepare a Surface service escalation (logs + serial) because that step points at a firmware/board reflash or module replacement.
Short, plain next message you can paste back here
  • “Memory integrity was ON/OFF. I ran pnputil and pasted the following oem*.inf lines: … . DFEvents.txt shows these ERROR lines: … . I will (or will not) re‑run the Surface MSI now.”
I’ll parse your outputs and give the exact low‑risk commands to fix the Helloto escalate to Microsoft service, including the precise logs and steps they’ll want. You’re on the right path — the hardware is visible, we just need to finish the driver/firmware binding or repair the driver store that’s preventing it.
 

that's a lot ????ITS YOUR DEVICE ?!?!? HOW YOU DONT HAVE THE DRIVER ?!?!?!? ANY HUMAN AROUND ? THATS CRAZY
 

I hear you — that’s totally frustrating. You did nothing wrong; the problem isn’t you, it’s the device/driver tooling. The Event ID 10116 you pasted shows the Surface Base 2 firmware update process crashed while it was running, and when that happens the Hello/IR liveness driver often never finishes installing or binding. In short: Windows sees the camera hardware but the Hello driver/firmware didn’t complete, so Hello reports “no compatible camera.” t and give two fast options: a quick try you can do now, or I can help prepare the exact files/logs/message to escalate to Microsoft service (so they reflash/repair the module).
Option A — Try the quick fixes (10–20 minutes)
1) Plug the Surface into AC power (required for firmware steps).
2) Temporarily turn OFF Memory Integrity:
  • Settings → Privacy & security → Device security → Core isolation details → set “Memory integrity” to Off → Reboot.
    (This step avoids HVCI blocking driver loading.)
    3) Re‑run the Surface Book 2 (Model 1832) Drivers + Firmware installer:
  • Download the Surface Book 2 drivers/firmware package from Microsoft, unzip it, right‑click the MSI → Run as administrator → reboot when prompted.
  • If the installer reports a firmware flash error, note the exact message. Re‑running the package often completes a firmware/driver bind that failed earlier.
    4) After reboot, ches → Sign‑in options → Face Recognition. If still failing, get two quick outputs and paste them here:
  • Run Command Prompt (Admin) and run: pnputil /enum-drivers > C:\Users\Public\pnputil.txt then open that file and copy any oem*.inf lines that mention camera/IR/Surface.
  • Open Device Manager → Cameras / Imaging devices → capture the exact names shown (a screenshot is fine).
If that fixes it — great. If not, continue to Option B.
Option B — Escalate to a Surface firmware/service repair (recommended if re‑install crashes or the DF events keep appearing)
  • Your DF/Kernel logs already show the user‑mode driver crash for the Surface Base 2 firmware update (Event ID 10116). When the firmware update process is unstable like that, it often requires Microsoft/Surface service to reflash the module or replace the faulty firmware component. I can:
    • Prepare a short support message + the exact logs/methods Microsoft support will ask for (Event text, pnputil dump, and the Surface serial you already posted), or
    • Walk you step‑by‑step to collect the Surface Diagnostic Toolkit logs they’ll need and the exact wording to paste into a Microsoft support case.
      This is the most reliable path when user‑mode firmware update crashes are the root cause.
If you want to proceed now, tell me which you prefer:
  • “Try Quick Fix” — I’ll give direct download filename + the single copy/paste command block (pnputil + the power checks) to run and paste back.
  • “Prepare Support” — I’ll assemble the exact support text and list the logs to send to Microsoft so you can open a repair ticket (I’ll draft the message with your serial included).
Again — completely understandable to be angry. You’re right: the device should bring its own drivers. The crash in the Surface firmware update process is the real reason it doesn’t. Tell me which option and I’ll give the exact next commands or the ready‑to‑send support text.
 

Can I install win 10?
 

Short answer: Yes — you can install (or downgrade to) Windows 10 on your Surface Book 2 (Model 1832). Microsoft provides Surface recovery / Bare‑Metal Recovery (BMR) images and documents the downgrade process. However, there are a few important caveats you must understand before you do it. (learn.microsoft.com)
What you need to know before proceeding
  • End‑of‑support timing: Windows 10 reaches end of support on October 14, 2025. After that date Microsoft will stop regular security/feature updates unless you enroll in the consumer Extended Security Updates (ESU) program. That makes running Win10 a short‑term or transitional option for most users. (support.microsoft.com, learn.microsoft.com)
  • Downgrade rights / licensing: Microsoft/OEM downgrade rights generally let you run Windows 10 Pro on a Surface that shipped with a Windows 11 Pro license, but follow the Surface downgrade guidance and OEM EULA. (learn.microsoft.com)
  • Drivers & firmware: after installing Win10 you must install the correct Surface Book 2 (Model 1832) Drivers & Firmware package for Windows 10 — Microsoft publishes those in the Surface Recovery/Drivers download pages. Some newer Surface models are not compatible with Windows 10; the Book 2 is an older Surface and has Windows 10 support, but you must use Microsoft’s recovery image and drivers. (learn.microsoft.com)
  • This may not fix the Hello/IR issue: your problem looks like a firmware/driver binding failure (the Surface Base 2 firmware update process crashed). Reinstalling Windows 10 could succeed, but if the firmware component is corrupted or the module is failing, the Hello IR problem may persist and you may still need a Surface service/firmware reflash. (We saw driver/firmware crash events on your logs — that’s why I recommended logs and a Surface Diagnostic run earlier.)
Step‑by‑step (recommended, safe path)
1) Backup first (required)
  • Create a full image (Macrium Reflect, AOMEI or similar) or at minimum copy your Documents/Pictures and export any keys (BitLocker recovery key) before making changes.
2) Decide whether to try repairs first
  • Because the logs show the Surface Base 2 firmware update crashed, the quickest less‑destructive route is to re‑run the official Surface Book 2 drivers & firmware installer while on AC power — that often completes a failed firmware bind and restores Windows Hello without reinstalling the OS. If you want, I’ll give the exact filename to download and the single copy/paste installer steps. (This is usually faster than a full downgrade.)
3) If you still want to install Windows 10 (downgrade) — official Microsoft flow
  • Download the Surface recovery/BMR image for Surface Book 2 (Model 1832) from Microsoft’s Surface Recovery Image Download page (sign in to Microsoft and select your device). Use Microsoft’s instructions for creating a recovery USB and doing a bare‑metal restore. After the restore you must install the Surface Drivers & Firmware package for the model. (learn.microsoft.com)
  • Steps (high level):
    1. Back up everything.
    2. Download the Surface BMR image for Model 1832 (Microsoft site) and create a recovery USB (follow their tool instructions).
    3. Boot from the recovery USB and perform the recovery/installation.
    4. After install, run Windows Update and install the Surface drivers/firmware package and any optional driver updates. Reboot as required.
    5. Test Windows Hello and camera functions; if the Hello/IR issue persists, collect the Surface Diagnostic Toolkit output or Event logs for escalation.
4) Licensing & support choices after install
  • Because Windows 10 support ends Oct 14, 2025, consider enrolling in the Windows 10 consumer ESU (if you must stay on Win10 temporarily) or plan to move back to Windows 11 / a new PC. Microsoft documents ESU and the upgrade recommendation. (support.microsoft.com, techradar.com)
If you want my help right now
  • I can guide you step‑by‑step to either:
    A) Re‑run the Surface Book 2 drivers & firmware installer (fastest first attempt). — I’ll give the exact download filename and the commands to run as Admin.
    B) Or, prepare the complete recovery USB + downgrade instructions and walk you through the full reinstall. I can also assemble the exact support message and logs you’d need if this turns into a hardware/firmware service case with Microsoft.
Which do you prefer? Reply with “A: retry drivers” or “B: do Win10 recovery” and I’ll post the precise, copy‑paste steps (and the Microsoft download page to use).
 

Back
Top