Server 2016 Problems

P

PeterA215

New Member
Joined
Jul 22, 2025
Messages
25
Hi. Im a volunteer admin at an emergency serveice and have been having issues for the last few days.

Initially when I attempted to log in (last week) I was getting the circle of dots non stop. I did some research and found the Server 2016 can sometimes take ages to do an update. Although I hadnt seen this before, I decided to leave it to continue.

When I checked again, I was able to log in. Since restarting the server im getting bad username or password and no network connection.I restarted in safe mode with networking and have been able to log in.

I have been unable to access windows update to run troubleshooting so I deleted the software distribution folder as I thought it might be an update issue.. No change

Ive run DISM /online/cleanup-image /checkhealth and scanhealth and both resulted that the component store is repairable.

I attempted to do a restore health using DISM but it cant find the source. I then downloaded Server 2016 Essentials and tried to use that as a source but no success. After numerous attempts at trying to use DISM over the last few days im finally asking for help. Any assistance is appreciated.

I also had a thought that maybe Active Directory is corrupted but that doesnt explain no network in normal boot.
 
Solution
Based on your updates and the attached dcdiag output, here's a focused analysis and targeted action plan:

1. Analysis of Your dcdiag Report​

Major Points:​

  • AD Database Not Corrupt: The diagnostic completes initial setup and finds a single DC, so your database itself isn’t destroyed.
  • Critical Services NOT Running: Key lines:
    Code: 
    NETLOGON Service is stopped on [MRSERVER]
kdc Service is stopped on [MRSERVER]
DNS Service is stopped on [MRSERVER]
    These are vital for domain controller operations and could explain the login/network failures in normal mode.
  • Connectivity & DNS Failures:
    Code: 
    The host 491a32e9-ab1b-4f13-a7b8-54ad639896d9._msdcs.MRCC19.local
could not be resolved to an IP...
An in-place upgrade to Windows Server 2019 can, in many cases, resolve operating system corruption issues—but there are important caveats and planning steps for domain controllers:

In-Place Upgrade to Server 2019: What You Need to Know​

Potential Benefits​

  • Replaces all operating system files and rewrites most registry/service configurations.
  • Can resolve corruption that Server 2016 repair installs might not, since you’re “refreshing” with a new OS image.

Risks and Considerations​

  • Must be supported: Upgrading a domain controller in-place from Server 2016 to 2019 is supported by Microsoft, but only if:
    • Your server passes all pre-upgrade health checks (AD, DNS, SYSVOL, replication).
    • No critical errors exist—especially in Active Directory or SYSVOL, which may be exposed or made worse by an upgrade if the base environment is already unstable.
  • If your DC is already in a corrupt state (key system services cannot start; SFC can’t fix corruption), the upgrade could
    • Get stuck/fail
    • Leave the server in an irrecoverable state (boot loops, failed upgrades, etc.)
    • In rare cases, worsen directory corruption

Backups are Essential​

  • Always take a full system and AD backup before attempting an in-place OS upgrade on a domain controller.
  • Given your current internet situation, ensure you can locally recover if the upgrade fails.

Best Practice Approach for Your Situation​

Given your DC currently:
  • Cannot start key services (LanmanServer, Netlogon, DNS)
  • Fails SFC/DISM repairs
  • Cannot log in to normal mode
The safer/cleaner approach is:
  1. Repair the current Server 2016 environment (repair install/in-place upgrade of 2016 itself), or
  2. Restore from backup, then—once healthy and all services run—upgrade to Server 2019.
If those aren’t possible, as a last resort:
  • Back up all possible data and attempt the in-place upgrade to Server 2019.
  • Be prepared for the upgrade to fail if system corruption is severe.

If You Do Attempt the In-Place Upgrade to 2019​

  • Follow Microsoft’s domain controller in-place upgrade checklist:
    • Take a system state backup of AD
    • Verify AD health: Run dcdiag and resolve all issues if possible
    • Ensure all roles are documented
    • Have a bootable Server 2016 install disk or working backup for emergency roll-back

In Summary​

  • An in-place upgrade to Server 2019 might fix Windows corruption if Server 2016 is too broken to repair—but it’s less reliable if core services cannot even start.
  • You should try restoring a healthy Server 2016 environment or a 2016 repair install first, for the best chance at a safe and successful Server 2019 upgrade.
  • Only attempt a 2019 in-place upgrade if you have nothing left to lose (i.e., after backing up everything and preferably after trying other repairs first).
If you want to proceed with a 2019 upgrade, I can give you exact steps, checks, and warnings to follow. Let me know if you want these, or want more help with repair or restore processes!
 
I can't find the exact build and version of my server. Can I do and in place repair from an different version?
 
Last edited by a moderator:
This is a crucial detail: For an in-place repair install (“upgrade-in-place” or “OS repair”) on Windows Server, your installation media must match both the edition (e.g., Standard, Datacenter, Essentials) and the build/version (especially for Server 2016, which has several “semiannual channel” and LTSC builds).

1. WHY THIS MATTERS​

  • If your install media does not match your currently installed version and edition, the in-place upgrade/repair will be blocked or may result in further corruption.
  • For example, you cannot perform an in-place repair with Server 2016 “1607” media on a Server 2016 “1809” or “2019” install, and definitely not if editions don’t match.

2. HOW TO FIND SERVER BUILD/VERSION​

Even from Safe Mode, you can use these commands:
From Command Prompt or PowerShell:
winver
or
systeminfo | findstr /B /C:"OS Name" /C:"OS Version"
or, for even more detail:
Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsBuildNumber
If you cannot run PowerShell, navigate to:
  • C:\Windows\System32\License.rtf — the text of this file often includes the version and edition.
  • C:\Windows\System32\winver.exe — double-click from Safe Mode GUI.

3. IF YOU CAN’T DETERMINE VERSION​

  • Do NOT attempt an in-place repair from a different version/build—this is likely to fail or cause further corruption.
  • However, if you only have one option and nothing else (and you’re prepared to wipe/reinstall if it fails), you may try—but this is not recommended, especially for domain controllers!

4. ALTERNATIVE OPTION​

  • If you have backup images or system state backups, a restore to a known-working state is far safer.
  • If you can extract useful system info from your uploads, let me know—I can search your files for evidence of the OS build/version and guide you from there.

BOTTOM LINE​

  • Matching edition and build/version is required for a supported in-place repair on Windows Server.
  • If you upload a systeminfo output or other logs, I can quickly identify your build/version and tell you exactly what install media you need.
  • Never use mismatched install/repair media unless you accept full server rebuild/possible data loss as a risk.
Reply here if you want me to search for your server’s build/version in your uploaded files—just confirm the file name or ask to search all logs. I’ll find it and advise!
 
Absolutely, seeking human support is a great idea—especially given the critical role of your server and the complexity of the situation.
Here’s what I recommend:

How to Get Human Support for Your Windows Server/DC Issue​

1. Microsoft Support​

  • As a production Windows Server/domain controller, you are eligible for paid Microsoft support, and as a non-profit/emergency service, you may qualify for discounts.
  • Visit: Microsoft Support for Business
  • They can guide you through advanced recovery, in-place upgrades, or restoration steps, and can even perform remote troubleshooting if necessary.

2. Local IT Professional or MSP​

  • If time is critical, contacting a local IT provider with Windows Server/Active Directory expertise may yield the fastest recovery, especially if you need on-site restoration, backup handling, or OS reinstalls.

3. iDrive Support​

  • For backup restoration, contacting iDrive’s support can assist you in retrieving your backups on another system, even if your server lacks internet access. They can help with “restore to external disk” or direct download solutions.

4. Community Resources​

What to Prepare​

  • Server edition and build (as discussed above)
  • Full error descriptions and steps tried so far (your posts here are a good summary!)
  • Recent backups/cloud backup access details
  • Server hardware information
You’ve done thorough technical groundwork here, which will help any human expert get up to speed quickly.
If you want, let me know your region or country (privately—if you wish), and I can suggest specific providers or partners for emergency Windows Server/AD recovery and support.
If you still want help with finding build/version from your logs for repair attempts, just let me know—you can use me and live human support in parallel. Your caution is wise for DC recovery!
 
On WindowsForum.com, you are absolutely welcome to seek direct human support—this forum is made up of IT professionals, experienced system admins, and fellow volunteers. Many active members will read your thread and can provide advice, troubleshooting steps, and sometimes even step-by-step hand-holding.
What to expect:
  • Replies are typically from community volunteers, experienced sysadmins, and sometimes industry experts.
  • You may get responses over the course of several hours or days, depending on who’s available and who has the right expertise for advanced domain controller recovery.
  • If you want urgent or real-time help (screen-sharing, remote access, on-call support), that level of service generally requires a paid consultant or Microsoft Premier Support, as forums can’t guarantee immediate or emergency live response.
How to maximize your support here:
  • Keep your thread updated with all actions taken and recent output (as you’ve already done—your thread is excellent).
  • Attach logs or screenshots if you feel comfortable—this often speeds up diagnosis.
  • If the situation becomes truly urgent (e.g., mission-critical system offline and you can’t proceed with community-suggested fixes), you’ll want to escalate to direct/premium human support, as described in my prior message.
In summary:
You’re already getting human attention by posting here, and you’ve documented your troubleshooting process in a way that will attract help from advanced WindowsForum members. Keep engaging and updating—if someone with direct experience in your exact scenario is watching, they’ll jump in.
If you want even more visibility:
  • Use a descriptive, clear thread title (yours is already good!)
  • Summarize your main symptoms and the steps you’ve tried in your next reply (maybe even edit your opening post with the latest findings for new helpers).
And if you ever want a real-time connection, phone support, or remote undivided attention, I recommend Microsoft or a qualified local IT service as your next escalation.
Let me know if you want tips for raising visibility here or help succinctly summarizing your current state for fellow human helpers!
 
Great question! Here’s how to get the most effective human support right here on WindowsForum:

How to Get Human Support on WindowsForum.com​

1. Keep Posting Updates in Your Thread​

You’re already on the right track:
  • Describe your problem in as much detail as possible (what happened, what you’ve tried, errors you’re seeing).
  • Continue to post updates and new findings (as you have been doing).

2. Engage With the Community​

  • Ask for specific suggestions or for a review of your troubleshooting steps.
    • Example: “Could another admin or AD expert review my steps above and suggest next actions?”
  • If someone replies, respond directly to their suggestions and clarify any questions they have.

3. Use Thread Tools​

  • Make sure your thread is in the most relevant subforum (Windows Server, Networking, or Active Directory).
  • You can “bump” your thread politely (post a brief update or question) if it hasn’t received a response after a reasonable time.

4. Tag/PM Active Members or Staff (if available)​

  • If you see users or moderators who commonly help with advanced topics, you can mention their usernames (using @, if supported) in your thread.
  • Some forums allow private messaging (“conversation”)—feel free to reach out and request a look at your thread.

5. Be Patient But Persistent​

  • Remember, this is a global volunteer community; sometimes replies are quick, other times a matter of hours or a day.
  • Keep your thread active with clear, detailed posts—more information means more likely a knowledgeable member will engage.

6. Consider Summarizing​

  • If your thread is getting long, summarize the current state of your issue and what’s been tried at the top or in a new reply to help new helpers quickly get up to speed.

Extra Tip:​

If you urgently need real-time or live support (phone, remote session, screen sharing), forums may not be sufficiently fast—consider supplementing with professional paid support for emergencies.
In summary:
— Keep replying to your thread with fresh info and questions
— Engage with anyone who responds
— Tag/PM knowledgeable helpers if possible
— Summarize if the thread is long
— Be patient, but keep your problem visible!
If you’d like, I can help you draft a brief “summary post” to re-engage helpers—just let me know!
 
You must log in or register to reply here.

Similar threads

S
  • Solved
Windows Server Essentials 2016 problem adding second drive for client backups
Replies
9
Views
594
ChatGPT
  • Solved
How to fix "Remote Desktop Services is not configured correctly" on Windows Server 2016 Essentials
Replies
1
Views
716
ChatGPT
  • Featured
  • Article Article
Windows Server 2016 EOL: Risks, Upgrades, and a Migration Playbook
Replies
0
Views
300
ChatGPT
  • Featured
  • Article Article
SQL Server 2016 End of Support 2026: Migration, Modernization, and Security Strategies
Replies
0
Views
586
ChatGPT
  • Featured
  • Article Article
Secure Federated Identity with Duo MFA and Microsoft AD FS on Windows Server 2016+
Replies
0
Views
178
ChatGPT