I did not try to reinstall all programs or wsee because my server is fine, everything works so far. No issues with security essentials.
Use the original driver from Microsoft, then write the following registry entry: Make sure that the Magican software from Samsung has been completely removed beforehand. Use a little program called Revo Uninstaller Pro. A better app is Uninstalr Freeware (GitHUB), but it takes longer. For Windows 11 USE: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides] "735209102"=dword:00000001 "1853569164"=dword:00000001 "156965516"=dword:00000001 Server 2025: Code: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 1176759950 /t REG_DWORD /d 1 /f
To enable safemode again merge both keys: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\{75416E63-5912-4DFA-AE8F-3EFACCAFFB14}] @="Storage disks" Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\{75416E63-5912-4DFA-AE8F-3EFACCAFFB14}] @="Storage disks"
I did not use samsung magician software. Always used windows standard driver. But with tjis new nvme registry key, all devices are gone in wsee dashboard. Deleting the key brings back all devices.
For all who want to use client restore service (including creation of client restore usb key) on Windows Server 2025 with WSEE : Just take ADK für Windows 10, Version 1607 (re-released May 2025) and install WinPE component and everything works fine.
Hi - I know this is an old thread, but I hope someone can help me. I am running a WSE 2016 box and I would like to upgrade to 2022 (or 2025). I downloaded the evaluation versions of 2022 and 2025 to test things out, and I have a spare machine to run the test. Reading through the thread, I found the set-up script on the archived GitHub post but the Essentials.wim file was only 20.4MB when I downloaded it which seemed small. I clean-installed 2022, put the set-up script and Essentials.wim on the desktop and ran the script in Powershell - nothing happened. I am thinking that I don't have a good Essentials.wim file. Can someone provide me a copy of the file or tell me how to create one? I have my WSE 2016 installation disk if needed. Thanks!
@Oldsports : You can use the WSEE-Capture.ps1 Script from mentioned git hub for extracting and creating the wim file.
@Dieter31 - Thanks so much for the reply. Can you provide a little more detail on how to create the file? As I said, I have my WSE 2016 installation disk and I have downloaded both the Capture and Set-up files from the GitHub post. I also extracted the install.wim file from the installation disk as I first thought that this was the same as the Essentials.wim file: What does the Capture file need to extract and create the Essentials.wim file? Does it need access to the entire installation disk contents? Does it just need the install.wim file from the installation disk? I assume the files need to be in the same location (meaning the same folder). Can it be any folder on the computer or do they need to be in a certain place? Anything else I need to know or do? Thanks!
@pm67310 - Success! After clean-installing Server 2022 again and following the process (start Powershell in admin mode, enable scripts, run Setup file), the Essentials configuration window appeared. I entered my server information (server name, domain name, etc.) and the configuration completed after a few reboots. i never had to use EssentialsRoleConfigWizard.exe to re-start the configuration process after the reboots. I can now open the Dashboard and see my familiar Essentials layout! I will install all of the Windows updates and see if it breaks anything. One odd thing occurred that I cannot explain. When I enabled the scripts during the first attempt, I used the command "Set-ExecutionPolicy RemoteSigned" and that allowed me to run the Setup file. This time, that command did not work. I had to use "Set-ExecutionPolicy Unrestricted" in order for the script to run. After the server was fully configured, I used the command "Set-ExecutionPolicy Restricted" to disable scripts. Thanks!
I tested Windows Server 2025 approximately a year ago and found the platform insufficiently stable for my environment. I was unable to install VMware Server reliably, and several VM‑related functions that work consistently on Server 2022 — particularly automatic VM startup — were either non‑functional or inconsistent. In addition, certain applications could not be uninstalled through the standard mechanisms. With the recent improvements in NVMe utilisation and storage performance in newer builds, I’m considering evaluating Server 2025 again. Has anyone conducted recent testing or have technical insights, stability reports, or deployment recommendations to share?
I am having problems accessing my server folders using the WSEE Launchpad. I followed these steps to replace my Windows Server 2016 Essentials server with a Windows Server 2025 server with WSEE role: I clean-installed Windows Server 2025 and installed the WSEE role as per the Github instructions. I re-created all of the users from my Windows Server 2016 Essentials server on the Windows Server 2025 server. I restored all of the 2016 data files on the 2025 machine using Windows Server Backup. I downloaded the Windows Connector software from the 2025 server onto a laptop and connected the laptop to the server using one of the users I created. I signed into the Launchpad and I was able to access the server using the Dashboard option. I clicked on the Shared Folders option and received an error that said "Windows cannot access the \\******\Shared Folders. Check the spelling of the name. Otherwise, the might be a problem with your network". I can manually map "Shared Folders" as a network drive on the laptop and access the folders/files contained in it. I am not sure why the Launchpad cannot find it. Any ideas? Thanks! Update - I solved my own problem. The laptop's primary DNS was not pointed to the 2025 server; it was pointed to the router. On my main network, the router automatically assigns the server's IP address as the primary DNS to devices that are connected to it. On my test network (where I was testing the server), the router assigns itself as the primary DNS (which is the default). Once I fixed that, I was able to access Shared Folders via the Launchpad.