Proximity Device Error

[jgch]

The Device Manager on my ZBook reports an Error Code 10 for the Proximity Device (NxpNfcClientDriver).
I have rebooted my system already - without success.

jgch_0-1787149811704.png

I have not found suitable option in the HP Diagnostics tool to test this device. Is my notebook broken?

[Deep_World]

Hi  @jgch 
 
Welcome to the HP Support Community!

Thank you for reaching out, and I understand your concern about the Code 10 error reported for the NxpNfcClientDriver (Proximity Device) in Device Manager on your ZBook. I’m glad you’ve already restarted the system and checked HP Diagnostics.

To better understand the situation, could you kindly share:

• Are you experiencing any issues with NFC-related features, smart card authentication, Windows Hello, or device pairing?
• Have you noticed any unknown devices or additional warnings in Device Manager besides the Proximity Device entry?

In the meantime, kindly try the below steps and confirm : 

1. Open Device Manager.
2. Expand Proximity Devices.
3. Right-click NxpNfcClientDriver and select Uninstall device.
4. Restart the notebook and allow Windows to reinstall the driver automatically.

If the issue persist :

1. Open HP Support Assistant and check for available driver updates.
2. Install any available Chipset, NFC, and BIOS updates specific to your ZBook model.
3. Open Settings -Windows Update -Advanced Options -Optional Updates and install any available hardware driver updates.
4. In Device Manager, right-click the device, select Properties -Driver, and note the driver version and date. Kindly share those details with us.

I hope this helps. 

[ZemJ]

Problem Description:

The internal NFC reader (ACPI ID: NXP8013) stopped functioning (likely triggered by a recent BIOS update to version 01.05.07, a modern AMD chipset driver update, or a recent Windows 11 system update). In Windows Device Manager, it fails to start with Code 10 (status 0x80070005 – Access Denied within the WUDFHost.exe process during I2C bus access).

Troubleshooting Steps Already Taken (Without Success)

• 1. Low-Level WDF Log Diagnostics (WUDFHost.exe / Event Viewer):

  • Analyzed WDF operational logs (Microsoft-Windows-DriverFrameworks-UserMode/Operational) and kernel events.

  • Verified that the underlying ACPI/bus layer (AMDI0010) detects the device on the I2C bus properly, with operation (27, 0) returning status 0x0 (STATUS_SUCCESS).

  • The failure occurs inside the user-mode host process WUDFHost.exe when attempting to open the I/O communication channel for NxpNfcClientDriver.dll, where the kernel rejects the request with 0x80070005 (Access Denied / STATUS_ACCESS_DENIED), resulting in Code 10.

• 2. Driver Clean Reinstallation:

  • Fully removed the driver package from the Driver Store (pnputil /delete-driver) and performed a clean installation of the official NxpNfcClientDriver.dll package.

  • Result: Unresolved; the WDF host still logs 0x80070005.

• 3. Attempted Generic Windows NFC Driver Binding:

  • Attempted manual assignment of generic INF drivers (netnfc.inf / proximity.inf located in C:\Windows\INF).

  • Result: Windows does not provide a standalone generic INF for I2C-based NXP controllers without a vendor client; only the class installer c_proximity.inf is present.

• 4. Integrity Enforcement and Secure Boot Modification:

  • Tested running with disabled driver signature/integrity enforcement (bcdedit /set testsigning on and nointegritychecks on) with Secure Boot disabled in BIOS Setup (F10).

  • Result: I2C bus access permissions remained blocked within the Windows kernel/WDF boundary.

• 5. BIOS Rollback Attempt:

  • Attempted rolling back the BIOS to a previous version (01.04.05 / 01.03.00).

  • Result: The rollback did not resolve the problem; the exact same error and Code 10 persisted.

• 6. Hardware Power Reset (G3 Reset):

  • Performed a complete G3 hardware reset (disconnected AC power and held the Power button continuously for 25 seconds to drain motherboard capacitors and reset the Embedded Controller).

  • Result: No change; the status code in Windows persists.

• 7. Low-Level Hardware Diagnostics via Live Linux (Ubuntu):

  • ACPI Check: /sys/bus/acpi/devices/NXP8013:00/status returns 15 (0x0F = Present, Enabled, UI, Functioning).

  • I2C Bus Response: Using i2c-tools at address 0x28 (on bus i2c-3), the controller responds with a hardware ACK and returns the initial status byte 0xD5 (NCI preamble).

  • Diagnostic Conclusion: The hardware, power rails, and NXP silicon are 100% functional and responsive on the physical layer.

• 8. HP Support Chat Interaction:

  • Contacted HP Support Chat. The agent recommended reinstalling the NFC driver, AMD Chipset drivers, and Wi-Fi card drivers—all of which were performed without success.

  • The agent subsequently advised performing a full factory reset (OS reinstallation), which was declined as an unfeasible and disproportionate measure given the low-level security/bus nature of the issue.

• 9. Local Phone Support Contact:

  • Contacted local HP phone support. I was informed that HP currently has no internal records or known advisories regarding this specific error, and that an authorized service partner will contact me on the next business day to determine the next steps(I am waiting for that call).

Summary

The hardware is fully functional and electrically intact. The issue is strictly isolated to a security/permission conflict between WUDFHost.exe in Windows and updated platform security components (such as the recent BIOS 01.05.07 microcode/certificates, updated AMD I2C/GPIO bus drivers, or recent Windows 11 kernel security patches).

[Deep_World]

Hi @jgch 
 

Thanks for your response and Thank you for providing such a detailed analysis and for outlining all the advanced troubleshooting you've already completed. I can see that you have thoroughly validated the NFC hardware, performed clean driver installations, tested BIOS rollback, completed hardware resets, and even confirmed functionality at the hardware level under Linux.

Based on the information shared, this does not appear to be a hardware failure. Since the NFC controller is detected correctly on the I2C bus and responds normally in Linux, the issue is isolated to the Windows driver stack and its interaction with platform security components.

As per the above information the issue is occurring within the Windows User-Mode Driver Framework (WUDFHost.exe), which is returning 0x80070005 (Access Denied).

Because the NFC controller is communicating correctly at the hardware level and continues to fail only within Windows, replacing hardware components is unlikely to resolve the issue.

At this point,  Kindly wait for the authorized service center or To ensure your device receives the appropriate care, we recommend visiting an authorized HP service center. Our certified technicians can provide a thorough diagnosis and offer the best solutions to address the issue.​

You can locate the nearest HP service center using our Service Center Locator:​

🔗 HP Service Center Locator

If you need further assistance or have any questions, please don't hesitate to contact us.​

Regards,

Deep_World