I assume that you’re talking about Microsoft’s Essentials config wizard failing at some percentage, such as 89% etc., during the installation process here (and not the WSEE Installer itself failing). If so, then I’m not able to reproduce that issue over here I’m afraid (and no one else is currently reporting a similar issue). Are you starting out with a brand new/clean (i.e., straight out-of-the-box) Windows Server 2025 install? If not, then you may want to try doing that and see if it works better for you that way instead.

Typically, the Windows Server Essentials config wizard will stall out at 89% (or there abouts) when the “Windows Server Essentials Management Service” cannot be started. You can try running the config wizard again (via its desktop shortcut), and when it stalls out at 89%, etc., open the Services applet and see if you can manually start the management service from there. If you can’t, then that’s most likely what’s causing the issue.

From there, you could try opening the Event Viewer applet on the server and looking at the following log(s) to see if they happen to show any errors that will point you in the right direction:

Event Viewer (Local) -> Applications and Services Logs -> Microsoft -> Windows -> ServerEssentials (and ServerEssentials-Deploy)

Event Viewer (Local) -> Windows Logs -> Applications (or System) [to see if it shows any indication as to why the service won’t start]

Additionally, you can look in the server’s “Logs” folder to see if any of the log files within that folder happen to give you any indication as to what is causing the failure. The server’s Logs folder is located here:

C:\ProgramData\Microsoft\Windows Server\Logs

If you sort the folder by date modified, then the most recently written to log files will appear at the top. You can then open them up in Notepad and see if they show you anything of interest.

Other than that… Doing a quick Internet search brings up the following information (about it being a permissions issue on C:\ServerFolders, etc. – although I have no idea how accurate it is or not):

Ask Brave

Lastly, make sure that you’re not attempting to install Windows Server and WSEE onto a dynamic disk, drive pool/storage space, RAID array, etc. seeing as that could be what’s causing the issue as well (i.e. just use a traditional HDD or SSD with nothing fancy going on).

I’m sorry that I don’t have a better answer for you on this one, but I do hope that what I’ve said helps you out some.

Thank you thank you thank you

It was the Dynamic disk

I’m getting emails from admin at theofficemaven.com, that how I knew it was posted  🙂