SDI update driver causing NTLite activation to fail

Mr. Yu

Member
Messages
314
Reaction score
24
Hello
Due to the low driver version on the official website, I had to use Snappy Driver Installer to update the driver. After updating all drivers, ntlite pops up requesting reactivation. And re importing the license.dat and entering the key is also of no use. I have returned to the previously backed up system, and ntlite can be used normally.
Which driver changed the hardware code? thank you.
 
NTLite licensing is keyed to your PC's unique HW ID's. For example: motherboard, CPU, boot device, primary NIC.

Since you know what you did wrong, it's just a process of elimination. But it's probably not any of the peripheral devices.
 
I am currently investigating and have installed small drivers such as graphics cards, network cards, and Bluetooth, but none of them have malfunctioned. The only possibility is the motherboard driver. seven
Please wait for my message.
 
I'm not waiting. You already solved your own problem, but haven't isolated the offending driver.

50/50 it's SMBus or System Control Interface.
 
Found the reason, it is due to nvme drive, which I have been ignoring. After I uninstalled it ntlite can recognize the hardware normally. What does hard disk have to do with ntlite? Do I need to reactivate ntlite to replace my hard drive?
 
"Please wait for my message." is just a written expression of respect. It's just another way of thanking you for answering. Your "I'm not waiting." is embarrassing to me.
 
You have to reactivate whenever the system drive is changed. I'm guessing NTLite sees the NVME being reported as the "primary boot device", by whatever hardware detection it uses. "Primary" is chosen by the disk controller ranking, which is based on the chip's PCI bus number.
 
I do make me sad. I'll be replacing the hard drive often, as it has a limited life span. Other hardware can last until I die.
Updating drivers can also cause this problem, It boggles the mind.
 
Latest news
To verify this, I took the risk of testing it on two other Sata solid-state drive computers, and strangely, there were no activation issues. Since I only have one computer with NVME hard drive, I cannot rigorously verify it.
But I'm sure there won't be any issues updating drivers on Sata solid-state drives. However, activation issues may occur on NVME hard drives.
Driver package: The latest driver package for DriverOff at 03.07.24 Driver detection: Snappy Driver Installer
 
Back
Top