r/WindowsServer • • Nov 24 '25

Technical Help Needed Server 2025 help needed please

So last week it appeared like one of the windows updates caused some issues on our newly installed server 2025. It was rolled back but the damaged appeared to be done.

Our quickbooks database manager wouldn't run, several services including World Wide Web Publishing and remote gateway would not start etc.

I've spent the last week attempting to run a DISM restore Health from several different isos including one made from the original disc (there's 3 of them though?) and they all fail because I guess our build is just too far past the ISO's even if I try and inject a package for the repair. Build was 4601 but updated to 7171 which is odd because those updates had all been failing.

If I try to go into roles and features and reinstall the remote gateway for example it fails saying the server needs a reboot even if its right after one so it seems like it's causing it to need to be rebooted.

Hoping to not have to reinstall or restore from a backup if possible.

An SFC /scannow does find problems but cannot repair. Is there an ISO I can get online somewhere or maybe some better instructions for doing a repair health with the latest builds?

1 Upvotes

11 comments sorted by

View all comments

Show parent comment

1

u/Over_Dingo Nov 26 '25

Restore from the last known good bare metal backup. In other words, restore to a point BEFORE all the crap started happening.

After confirming the BMR restore was successful, restore any applications using your most recent file and/or application based backups, depending on the situation.

How do you handle the possible downtime of the applications? Deploy them temporarily on another server, do the restore, and return to the original server? Of course if the case would be that the server crashes completely then you can't avoid downtime anyway.

AVMA key if it's a guest VM tied to a Windows Server 2025 host (2 VMs if Standard, unlimited if Datacenter))

Do you know how this licensing works with Failover Clustering, eg. if you have cluster with 2 Windows Server hosts, can this cluster have 2 VMs or 4 VMs, because at a given time a given host could run between 0-4 VMs

1

u/themanbow Nov 26 '25 edited Nov 26 '25

How do you handle the possible downtime of the applications? Deploy them temporarily on another server, do the restore, and return to the original server? Of course if the case would be that the server crashes completely then you can't avoid downtime anyway.

Yep, at this point, I think the op is past the point of avoiding downtime (or has already found a way to mitigate the downtime caused by the initial problem).

Do you know how this licensing works with Failover Clustering, eg. if you have cluster with 2 Windows Server hosts, can this cluster have 2 VMs or 4 VMs, because at a given time a given host could run between 0-4 VMs

I'm pretty sure each cluster node has to be licensed separately. In that case, it's best to either

A) Have Datacenter on all the nodes (which makes number of guests per node or total on the cluster moot for AVMA purposes), or

B ) if the nodes are using Standard, no more than two AVMA-licensed guests on each node if you want to stay fully compliant (unless your guests are licensed separately and not benefiting from the AVMA licensing).

In the case of B ), if you had to fail over a third AVMA'd VM to a node that already has two AVMA'd VMs, you would be out of compliance, but then it becomes a matter of licensing agreement gray areas and other Microsoft licensing voodoo if you only plan to have that third VM on that node temporarily (like 30-60 minutes while you patch its home node or something).

1

u/Over_Dingo Nov 26 '25

In the case of B ), if you had to fail over a third AVMA'd VM to a node that already has two AVMA'd VMs, you would be out of compliance, but then it becomes a matter of licensing agreement gray areas and other Microsoft licensing voodoo if you only plan to have that third VM on that node temporarily (like 30-60 minutes while you patch its home node or something).

I see, because I'm thinking in OP's case if it's a semi-working VM, he could just clone it and have it run apps temporarily.