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)

[JoeHardy]

Their TVs don't support Dolby Vision either.

[KG829]

I am also having this issue, tried all the suggestions in this thread none worked. Will be reverting to 7.3.

[rmoreas]

I don't get this to work, not with 8.1 and not with 7.3 on latest Win10 build. The icon of the app appears in the taskbar, but nothing happens.

Why does the Samsung Magician software not just work? This is not expectable. 

[rmoreas]

When starting 8.1 from command line, I get the following errors:

INFO:process Argv: [
'C:\\Program Files (x86)\\Samsung\\Samsung Magician\\SamsungMagician.exe',
'--disable-gpu-sandbox'
]
INFO:OS INFO:: {"OSName":"Microsoft Windows 10 Enterprise","OSBuild":"10.0.19045","OSArch":"64-Bit"}
Error sending from webFrameMain: Error: Render frame was disposed before WebFrameMain could be accessed
at WebFrameMain.send (node:electron/js2c/browser_init:2:94617)
at WebContents.send (node:electron/js2c/browser_init:2:79767)
at _r (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:346590)
at e.handleOnOprStageProgressCBEvent (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:359545)
at e.value (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:236032)
at C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:244483
Error sending from webFrameMain: Error: Render frame was disposed before WebFrameMain could be accessed
at WebFrameMain.send (node:electron/js2c/browser_init:2:94617)
at WebContents.send (node:electron/js2c/browser_init:2:79767)
at _r (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:346590)
at e.handleOnOprStageProgressCBEvent (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:359545)
at e.value (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:236032)
at C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:244483
Error sending from webFrameMain: Error: Render frame was disposed before WebFrameMain could be accessed
at WebFrameMain.send (node:electron/js2c/browser_init:2:94617)
at WebContents.send (node:electron/js2c/browser_init:2:79767)
at _r (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:346590)
at e.handleOnOprStageProgressCBEvent (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:359545)
at e.value (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:236032)
at C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:244483
Error sending from webFrameMain: Error: Render frame was disposed before WebFrameMain could be accessed
at WebFrameMain.send (node:electron/js2c/browser_init:2:94617)
at WebContents.send (node:electron/js2c/browser_init:2:79767)
at _r (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:346590)
at e.handleOnOprStageProgressCBEvent (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:359545)
at e.value (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:236032)
at C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:244483
Error sending from webFrameMain: Error: Render frame was disposed before WebFrameMain could be accessed
at WebFrameMain.send (node:electron/js2c/browser_init:2:94617)
at WebContents.send (node:electron/js2c/browser_init:2:79767)
at _r (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:346590)
at e.handleOnOprStageProgressCBEvent (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:359545)
at e.value (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:236032)
at C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:244483
Error sending from webFrameMain: Error: Render frame was disposed before WebFrameMain could be accessed
at WebFrameMain.send (node:electron/js2c/browser_init:2:94617)
at WebContents.send (node:electron/js2c/browser_init:2:79767)
at Sr (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:347961)
at e.handleUIBlockingCBEvent (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:348936)
at e.value (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:243125)
at C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:244483
Error sending from webFrameMain: Error: Render frame was disposed before WebFrameMain could be accessed
at WebFrameMain.send (node:electron/js2c/browser_init:2:94617)
at WebContents.send (node:electron/js2c/browser_init:2:79767)
at er (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:342651)
at BrowserWindow.<anonymous> (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:362137)
at BrowserWindow.emit (node:events:525:35)
at C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:348353
at Sr (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:348477)
at e.handleUIBlockingCBEvent (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:348936)
at e.value (C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:243125)
at C:\Program Files (x86)\Samsung\Samsung Magician\resources\app\dist\main\app\app.js:2:244483

[Trespas]

After few days of trying, even with a fresh install and a new ssd and all the suggestions I finally got it working.

The solution? Just smash it. Every time it would crash, I just kept starting it again and again. Sometimes might have tried to start it twice (all from the powershell, so it is fast to do). Each time it said it failed, I pressed cancel and did it again. Might even have force quit a few times before before it gave the option to cancel (by just closing power shell). Then it just suddenly moved on from the point it usually gets stuck, started normally and now seems to work started normally from the shortcut. The number of tries wasn't anything absurd either, might have been around 5-15.

On the other hand, it should just work.

Edit: After several reboots, installing other software, adding windows features etc. decided to see if it still works. Not surprising at all, it crashed on startup again. And as before, just starting it several times made it work. I do have the "--disable-gpu-sandbox" in my shortcut, but anyway. Didn't need to use powershell, just kept launching it, I think it took 7 tries this time. Now I can quit and start it normally again. Coincidence or not, I have 7 samsung SSD:s installed: 4 NVME drives and 3 traditional SSD:s. I have never seen a program this badly made.

Edit2: So I've been testing a bit more. For me, it doesn't seem matter if the --disable-gpu-sandbox is there or not. I just keep hitting "OK" for it to reinitialize. Longest time it took was a bit over 12 minutes, shortest was 1 minute 31 seconds. No logic there either. The only difference is that after that 12+ minute one is that I changed the "Auto refresh option" to 1 minute, which refreshes the drives status and performance. But don't know why that would matter.

[Hans-Chris]

Does not work either for me. I am not willing to hit  a key during 12+ Min. - thus, not tested this but I tried all other suggestions.

This is an insult to Samsung SSD customers! I really think about not buying Samsung SSD's again!

Look at the "Western Digital Dashboard": much smaller, faster and works perfectly. It may not have as much features as Magician but for me the really important feature is the firmware-update. Well, ok you can update the firmware even without Magician but it is a tedious process.

Also a very annoying "feature" in Magician: If the mass-storage-controller is configured as RAID it does not work, even if the SSD is not part of a RAID array. I thought that this may be technically impossible but the "Western Digital Dashboard" showed me that it can be done without problems! Btw. this applies to ALL Magician versions - it never worked with RAID controllers.

Even the cumbersome "corsair ssd toolbox" is way better because it acutally DOES WORK!

[Trespas]

Yes, this situation is absolutely ridiculous. I only wasted my time on the "keep hitting the button" method out of pure curiosity and frustration while watching tv. Fixing this shouldn't even take long, as they have more than enough data about the issue.

I've actually mailed my local samsung help and a few others about this, and will keep mailing them until they fix the thing. Suggest others do the same, as this forum is quite useless at getting the message to them.

[aurum79]

The Samsung 8.1 update works for me (with repeated attempts to start finally succeeding).   However, the 8.2 update does not work at all.   Very frustrating that Samsung keeps going backwards.   We're not, as one presidential candidate said, going back!

[Trespas]

Yeah, at this point this is purely absurd. They update the program, but don't bother at fixing the issues that prevent people from using it. I don't have the time to see if clicking the button for an hour or so would start it, so F samsung. Going to start buying SSD:s from other brands.

[Ukrnet · Accepted solution]

I want to help you all.
To make Samsung Magician 8.* work properly, just DO NOT disable the Windows service - "Server" (LanmanServer)