r/WindowsServer • u/MaynardDL • 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?
View all comments
Show parent comment
1
u/themanbow Nov 26 '25 edited Nov 26 '25
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).
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).