Customer getting 0xD error code on a VM

Hi,

Usually LimeLM works without problems for my customrs using various VMs, VPS's etc. Today a customer encountered a problem though. Quoting them:

"I have a server with VPS proxmox VE5 installed on it. I then created a Windiws 10 Pro Virtual machine. I used virtIO drivers to install windows.I setup the network like this : (a screenshot showing NAT mode, Model VirtlO (paravirtualized), MAC address)"

Time/date/timezone are set correctly on it (I verified it).

Is there anything I can do about it? Is there any piece of information which could help diagnosing it? (The customer is tech savvy so it's possible to obtain). I don't nor plan to use trials, maybe it's possible to switch off the time/timezone/date check altogether from my side?

Resuming a VM from a snapshot will make the date/time look suspicious to TurboActivate. Tell them to reverify the timezone, date, and time, and then tell them to reboot the VM instance (i.e. what it says in the error message).

Rebooting is an important step. As is verifying the timezone.

Thanks, it was very helpful. It turned out there are small time differences after VM reboot which customer was able to fix after your message.

Reply
Discard post