"Left the house for a few hours and when I came back I was able to navigate through my sample drive."
 
Are you saying that it did actually work properly, once? After you left it long enough? If not, I don't understand this line, or the one after it.


At what point exactly does Sonar stop responding? (a) When you navigate to the drive with the samples on, (b) when you open a directory, (c) when you click on a file, or (d) when you attempt to pull a sample into your project?

X2 starts acting up when I navigate to the drive with my samples on it through the browser.  The buffer icon (spinning circle) comes up and usually after a few seconds "not responding" will show up at the top of the screen. What I decided to do one day while heading out was not touch it at all after seeing the not responding come up because usually after about 5 minutes of it not responding I will go ahead and shut the program down. A few hours later I returned home and I was able to navigate through my sample drive without problem or hesitation until I closed down the project then opened it again. Just to be clear I didn't close X2, just the song I opened to get to the browser.
 
This morning I decided to see exactly how long it took to load up my sample drive in the browser and it took about 30 minutes.  When I closed the project and reopened it it stalled out again and "not responding" appeared on the top of the screen.  

Show us the file path of where it plays up. What happens if you move say 80% of the samples in another folder? I'm thinking that a weird file path, unusual characters in a file/folder name other than say A-Z or 0-9, or the file path is too long, or a corrupted file hence my chkdsk suggestion. Or maybe too many files in one folder.
 
Sorry the screenshot is impossible to see.

CakeAlexS
Show us the file path of where it plays up. What happens if you move say 80% of the samples in another folder? I'm thinking that a weird file path, unusual characters in a file/folder name other than say A-Z or 0-9, or the file path is too long, or a corrupted file hence my chkdsk suggestion. Or maybe too many files in one folder.
 
Sorry the screenshot is impossible to see.

I tried uploading a pic earlier and you saw the results of that.. haha.. If you can explain to me the proper way to upload the pic for better viewing then I will.. 
 
I have already taken my main sample folders that I use and copied them to my main hard drive 
 
I have a total of 330gb of sounds including Komplete sounds and IK Multimedia's too. I am hoping that its not the case.. 
 
Funny thing though is that my sample drive is displayed as 'Samples/Refills" because I used to have Reason.. I will take the '/ Refills' out of it and see what happens.. Geez I would feel like a complete idiot if that were the problem.. haha...

CakeAlexS.... 
I cannot thank you enough... I would not have ever thought that something as simple as a symbol being in the file path would have caused such an issue.... 
 
Its strange that the other programs that I no longer use like Cubase's Mediabay or FL Studio's Browser or my other current DAW Studio One 2 didn't pick that up..
 
Again thanks a million.... 
 
 

chawilcomm
 
Its strange that the other programs that I no longer use like Cubase's Mediabay or FL Studio's Browser or my other current DAW Studio One 2 didn't pick that up..
 

Those are all cross-plaform apps. It is possible they do not rely on Microsoft file name handling routines.

chawilcomm
CakeAlexS.... 
I cannot thank you enough... I would not have ever thought that something as simple as a symbol being in the file path would have caused such an issue.... 

Not the first time Alex has solved some off-the-wall problem.  
 
I was wondering how this was going to play out, because I was stumped. Good job on the detective work...scook's explanation makes sense, too.

I can recall that I had this problem a long long time ago when I named a sample with an accent.  Sorry to remember this a little later...

chawilcomm...I would not have ever thought that something as simple as a symbol being in the file path would have caused such an issue...

Congrats on the resolution!  It's always great to see someone's problem being fixed.  I'm curious now what illegal characters were involved - and how they got there in the first place.
RB

It was a forward slash "/" on the name of the drive and that has been there since I put this computer together 4 years ago. 
 
What else was weird was that I had to remove a couple of .rar files. Apparently that was stopping the process to. But why would the .rar file stop the process and the Komplete files and IK Multimeida files on my drive?
 
Maybe because Sonar is equipped to read those types of files and not .rar files