Windows 10: NFC Not Ready Now

When I boot up, the logon screen shows "NFC Not Ready Now" along with my user account. In order to log on, I have to manually select my user account. The computer previously had an ASUS Z87-Deluxe Quad motherboard which supported NFC Express. The motherboard was replaced with an ASUS Z97-E without NFC support. The Z97 would not shut down or go to sleep; I had to physically turn of the PSU in order to turn the computer off but that problem was solved by replacing the motherboard. The logon screen did not change after I replaced the motherboard. I have searched the registry and cannot find an NFC logon key or value. The NFC message does not appear if I chose the option to log on without a password. My hardware includes an Intel i7-4770K processor, Samsung 840 EVO 1TB SSD and 16 GB memory. Any help would be greatly appreciated. I am running Window 10 Pro which was upgraded from Win 8.1.

:)

 

Windwos 10 - nfc is not ready now

Edjesu, not sure if you will be notified, but I found and just posted the solution that worked for me, check it out and let me know if you have any problems. Dan

 

Windwos 10 - nfc is not ready now

Thanks


KA

KarimRombi That worked just fine for me. At least for now.

I found the ENABLED key at ASUS NFC LOGON and changed "On" to "Off." I no longer see the NFC option on boot up. I will let you know if it blows up later.

Curtiss

 

From the start icon, search for programs and features control panel. Look for Asus publisher and NFC software and uninstall it if you find it there.

I was close.... see here:
http://answers.microsoft.com/en-us/w...e-327135606641

 

Thanks for the reply. I have been trying to fix the problem for several months. It started after a Win10 update. I have seen the above page and several others from searching the web. I suspect that a part of the NFC Express software remained some where in the registry or some other area of Windows 10 after I uninstalled the ASUS NFC software. I have spent hours searching the registry and device drivers without success. I have decided to bite the bullet and do a clean reinstall of Win10. Thanks again for your help.