Samsung Magician 8.0 does not work

[Ukrnet]

New Samsung Magician 8.0 not installed (after install process samsung services start to load my comp processor and nothing happens futher).

After kind of installation, Magician interface not loading at all.

it's not working properly on my Win 11 and I reverted to 7.3.0

No previous versions of the program had such problems before!

Please fix it.

!!! SOLUTION

To make Samsung Magician 8.* work properly, just DO NOT disable the Windows service - "Server" (LanmanServer)

[Trespas]

I'm sorry but this is not a solution. I've never disabled that service. LanmanServer is up and running, but Magician isn't.

[Hans-Chris]

No, this is not the solution. I guess my problem with Magician is because it does not work with some Windows PCs. I just tried the newest build but it won't work either. I want to install Magician on a fanless PC with an Intel N100 CPU. Obviously Magician does not support the N100 or its Chipset. This is a CPU launched in Q1'23. So, it is not new but far from being old either. I am running Windows 11 Pro on it. EVERY single app does work EXCEPT this stupid Magician. It installs flawlessly but when I want to start it, it throws me this error message:

I looked into the Installation-Guide. Check the "General Limitation" section. They mention 32 (!) limitations. That's a whole lot of limitations... but it does not mention incompatibility with some CPU/Chipset configurations.

"it is not magic it is software" - it is definitely NOT magic - it is a piece of junk.

[Hunor98]

This is the only solution that has helped me so far, even though I have tried everything that was suggested.

The solution I found is related to this. To be able to restart LanmanServer or to reset it to default, run cmd as an administrator and copy these:

sc config LanmanServer start= auto
sc start LanmanServer

After that, samsung magician started automatically for me and it has been working flawlessly ever since.

[Hans-Chris]

No way. Why should this do anything when LanmanServer is already set to auto and is already running? Tried it anyway - no joy ☹️

[Hunor98]

I am very sorry that this did not help you either. I cannot answer what the connection is between the two. As I said, I've already tried all the other options suggested on the forums, but this was the only one that helped. Here is the link where I found the cmd commands and where you can find more information about LanmanServer, in case it helps.

https://revertservice.com/10/lanmanserver/

As you said and it can also be read on the page (which I linked), LanmanServer is automatically started by Windows. I use the Samsung Magician software on an 8-year-old Asus gamer notebook and the LanmanServer may have stopped after an update over the years. I hope you find a solution that works.

[Trespas]

Yeah, for many if not most people, it's not a lanman issue. Glad it helps someone use this garbage app.

Was bored again, so as Magician is an electron app you can enable certain flags. With --enable-logging you can see what the actual issue is. It literally can't find itself, or rather the preload file. And no, adding the magician folder to env path doesn't solve it. This is essentially faulty programming. It should be a simple fix, but the people responsible for developing Magician seem to be talentless hacks. This is a fresh install too.

[BaPef]

So I found a solution that actually worked for me

I modified the samsung magician shortcut on the desktop to be exactly "C:\Program Files (x86)\Samsung\Samsung Magician\SamsungMagician.exe" -no-sandbox 

and I also went to advanced and checked the box to run as administrator.

I had to do those two things together in 2024 to get it to run again.

[Petzi60]

There must be 2 "-" before "no-sandbox", then it works for me.

"C:\Program Files (x86)\Samsung\Samsung Magician\SamsungMagician.exe" --no-sandbox

[Trespas]

Thanks for trying to help. Those didn't work, get the exact same message. I've tried pretty much everything, with -disable-sandbox, --disable-sandox, --disable-gpu-sandbox --no-sandbox (which is the official electron cli flag) and many others and combination of these. Even set the temp path for user files in case it was a permission issue with the flag "--user-data-dir=c:\path\Magician", where of course tried to put it on another drive too.

As far as I can tell, there are several issues with Magician, which is why different solutions work for some people. Be it network service related, gpu-sandboxing, running as admin or whatever. Based on the errors I get and some googling, this seems like a classic case of lazy devs not wanting to actually fix deprecated or changed parts and instead "fixed" the app with temporary stupidity which keep causing different issues. 

On the other hand, would be interesting to see what errors people get before a working fix with the --enable logging -flag. One can save the logs to a text file  --enable-logging --log-file=c:\temp\logs

Don't know why I'm even bothering with this anymore, as without the source code there's a limit to what one can do. It just annoys me that Samsung doesn't even bother to comment on this or do anything about the issues.

Edit: Darn diddley doo, I'm losing my mind. Sent a ticket about this just to get some form of email contact, attached the error logs, and they ignored the whole part where I told them that "Magician can't even start"  and the logs, and went on about how rapid mode supports only sata drives blah blah blah. I mean, I have 8 Samsung SSD:s, 4 of which are traditional SATA and 4 are M.2 NVME, ranging from 860 to 990 series.

[kobonczek]

I also have such problems with this program. It used to work, and now it supposedly starts but remains on the taskbar all the time and does not want to restore itself in any way.