asked on 4/21/2021

rds server reboots itself

Have an upgraded 2012 to 2016 to 2019 RDS server. It's running on top of a Hyper-V 2019 machine. It has been running fine for 4-months since the upgrade but is now rebooting itself.

Remote Access * RDP server * RDS 2019

Last Comment

Lee W, MVP

4/23/2021

Andrew Porter

4/21/2021

Is it set to reboot when audit logs are full?
Could it be Windows Updates?
What does the event log say relative to the reboot reason?

Lee W, MVP

4/21/2021

How is it rebooting itself? Constantly? Once in a while? Daily? Randomly 1x per day? 2x? What do you mean it's rebooting itself. Please be specific.

Keep in mind, UPGRADES can never be as stable as clean installs.

ehrsw

4/22/2021

ASKER

I can be on Hyper-V watching my 7-8 virtual machines. The RDS server, which is one of the 7-8 servers will reboot, and the uptime counter will reset to 0. Sometimes it will reboot after about 20 minutes, sometimes it will go for around an hour, hour and a half before rebooting.

serialband

4/22/2021

Have you tried running the following scans to see if there's any system file data corruption?
dism /online /cleanup-image /checkhealth
sfc /verifyonly

If they report errors, you can run the corresponding repairs.
dism /online /cleanup-image /restorehealth
sfc /scannow

ehrsw

4/22/2021

ASKER

FYI: Since everyone has gone home for the evening, the RDS server has been up without rebooting itself. 6+ hours

The vhd's are running on an HP SSD.

dism reports: No component store corruption detected.
sfc reports: Windows Resource Protection found integrity violations.
CBS.log states: Primitive installers committed for repair (repeats hundreds of times)

I have run the sfc /scannow and rebooted as instructed by the application. We'll see if this fixes the issue, once the users log back in tomorrow.

Thank you serialband for your suggestions.

ehrsw

4/22/2021

ASKER

The sfc didn't fix it but it was good to know as it did fix some issues.
After some research, I believe it's from the March Windows update which is incompatible with some printers, including the Kyocera printer driver that is on this RDS server. See: https://www.reddit.com/r/sysadmin/comments/m1jkuz/kyocera_drivers_patch_tuesday_bsod/gqj91b3/

We've uninstalled the Windows update in question and also applied the direct printing to the printer from spooled. We'll see if this fixes the issue.

ASKER CERTIFIED SOLUTION

ehrsw

4/23/2021

THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.

View this solution by signing up for a free trial.

Members can start a 7-Day free trial and enjoy unlimited access to the platform.

See Pricing Options

Start Free Trial

Lee W, MVP

4/23/2021

If you're not subscribed to the patchmanagement.org mailing list, I would recommend it. There can be a lot of chatter on it, but it tends to provide FAST information on patching issues and the Kyocera issue was noted weeks ago. Knowing you had a Kyocera print device and seeing those reports might have gotten you a faster solution.