Page 1 of 2

Install conflict with Samsung Magician

Posted: Fri Dec 21, 2018 4:42 pm
by Tobiwan
Hello,

after update my Windows from 1803 to 1809 (now at 17763.195) my Primo Cache does not work anymore. What I tried:

Version 3.0.2
Version 3.0.8
Whitelist rxfcv.sys and rxbsknl.sys on my Bitdefender Antivir Plus
Complete disable Bitdefender Antivir Plus
Checking Windows Eventlogs

The solution was to uninstall Samsung Magician version 5.3.0.1910 and than reinstall Primo Cache 3.0.8, now it work again on my system.

I'm not sure what the problem is, I think it must be the Windows Update 1809, because before the update I use Primo Cache 3.0.8 and Samsung Magician 5.3.0.1910 both on my system without any problem. Every time I installed Primo Cache I found a entry about Samsung Magician\magdrvamd64.sys in the Eventlog, so it seems a conflict at the installation, it was gone after uninstalling the Magician.

Can't report more, maybe it helps you. If I can give you more information let me know.

Tobi

Re: Install conflict with Samsung Magician

Posted: Sat Dec 22, 2018 5:47 am
by Jaga
Disable Samsung's RAPID Mode, if you have it enabled. It will conflict with Primocache.

Re: Install conflict with Samsung Magician

Posted: Sat Dec 22, 2018 11:56 am
by Tobiwan
Yes Jaga, I know. The Samsung RAPID Mode was always disabled since I use Primo Cache and it was disabled. I test my SSDs and HDDs every step with AS SSD Benchmark to see if anything changed, and if the RAPID Mode get's enabled by anything I would have noticed it, but the Drives shows normal values and there was no Samsung RAPID Service installed and running at my Windows.

What I don't get is, Primo Cache 3.0.8 + Samsung Magician (RAPID Mode disabled) works perfectly fine before I did the Windows Update to 1809. I did not change Primo or Magician, only Windows on my System.

Re: Install conflict with Samsung Magician

Posted: Sun Dec 23, 2018 7:46 am
by Jaga
Well hmm. I always defer updates on Windows based systems, since I've had issues with their day-1 roll-outs in the past (one client had ~40 PCs with black screens at boot a number of years ago). I'm still on 1803 myself, so can't verify if 1809 causes Primocache problems. It may very well cause Magician problems though. And it sounds like leaving Magician uninstalled helps Primocache to run fine, which corroborates that theory.

Re: Install conflict with Samsung Magician

Posted: Mon Dec 24, 2018 3:16 am
by Support
@Tobiwan, thank you very much for the feedback!
We are checking issues on Windows 10 1809 version.

Re: Install conflict with Samsung Magician

Posted: Fri Dec 28, 2018 12:34 pm
by Gogol
I already had Windows 1809 and Primocache 3.0.8 running on my system. After reading this article I updated Samsung Magician yesterday to the latest version 5.3.0.1903 and today after I turned my computer on I noticed that Primocache was running but Cached Read/Deferred/Trimmed blocks stayed at 0.
I did a reinstall of Primocache 3.0.8 and everything is working again.

Re: Install conflict with Samsung Magician

Posted: Fri Dec 28, 2018 3:51 pm
by rutra80
So you have both Samsung Magician and PrimoCache working on 1809? Can you test if Rapid mode is usable?

Re: Install conflict with Samsung Magician

Posted: Fri Dec 28, 2018 8:31 pm
by Tobiwan
You can install both, but not enable the Rapid Mode at the same time with running a cache on Primo Cache. I used Samsung Magician for benchmarks and firmware updates before I had the problem and uninstall it.

Re: Install conflict with Samsung Magician

Posted: Sat Dec 29, 2018 10:22 am
by Gogol
It seemed that after a reboot I had the same problem. Primocache running but counters stayed at zero. As a test I did remove Samsung Magician from startup and enabled it again. In Task Scheduler I can see that Magician started now after Primocache and both are working together now.
But I don't know for sure what the starting order was before.

Re: Install conflict with Samsung Magician

Posted: Sat Dec 29, 2018 9:05 pm
by Jaga
I never have Samsung Magician start with Windows, and always force an exit on it when done using it. There's no practical reason to have it running, especially since you can't use Rapid mode with Primocache.