Still, moving it to C is not a solution to this problem. A year ago this happened, (see my earlier posts), and only a fixed PMS update a few versions later corrected the Plex Media Scanner.exe crash.
When I upgraded to Win 10 Pro, I put it all on C: because I was worried about the problem you are having.
The problem is not only PLEX. it seems to happen with Win 10 from the latest Patch Tuesday.
All I know is they are looking into the problem and I have not seen an answer.
I can tell you one thing I don’t like is the use of the users area in WIN 10.for everything. That area is encrypted by default. If your system crashes, it is next to impossible to get anything from all users areas.
Things changed greatly when I upgraded to an SSD for my boot drive but PMS is a HOG. If your system is a large one like mine, then you need to do like me and peel back a bit.
I loved to have everything in one place but that is impossible now. PLEX has moved off of the original course and has moved to a (%%^^#@) place online. I would love to be able to toggle all of the online stuff off and remain offline.
Don’t know if you want to try this but you can and it works better for me.
Drive C: 120GB SSD Drive . Windows 10 Pro installed. ONLY
Drive D: 500GB SSD Drive User area and User based programs
Stablebit Service: Movies and TV Series on External Drives. (Since PLEX no longer allows Mapped network drives to work properly)
You can find a tutorial that shows how to Change the Enviromentals for the users. Usually just change the C: to a D:
I have 32GB of memory installed so I have a Virtual Ram Drive of 16GB as Z: This is for the Temp File area for small compilations.
My Movie and Series collection is stored in a Stablebit Drive of T: and M: using Sonarr.
I can use Sonarr to move any series I want to start watching to Drive D: and back again.
This keeps PLEX database very small and easy to maintain. One added note. Don"t try to optimize a drive with a HUG PLEX database on it. You will be sorry.
I have learned the KISS method the hard way.
Thanks - I backed out 1.20.3.3401 and went back to 1.20.1.3252, event log was just filling with errors… Not sure how wide spread this is because I’ve not heard/seen anything more about it except for this thread… I guess we’ll wait for the next stable release.