Installing Dimension Pro

I got a new SSD hard drive
 
I installed Dimension pro using Command Center it just sits there installing in an infinite loop.
 
So I stopped it finally after two hours. It seems like Dimension was installed. It worked fine in Cakewalk.
 
Then a day later after installing tons of other stuff my SSD drive started acting like it had a bad sector or area. It would not let me delete files from downloaded files folder.
 
I ran Windows check disk and the computer went to a very odd screen (the new blue screen) Windows would not reload without doing a system restore to an earlier point.
 
What point you might ask? The point just before I installed Dimension pro. I reinstalled Dimension pro.. It happened again, infinite loop. Command center just keeps saying it is installing when it is not. I am aware Dimension takes a long time but not this long.
 
Please fix this.
 
Windows 10, 64 bit, Intel quad core, Cakewalk Platinum   PNY SSD -
 
https://www.amazon.com/gp/product/B019H3B6SU
 

I would agree with you had it not happened twice.
I have installed nearly 50 "large" apps and had no hiccups whatsoever on the SSD drive.
 
Only with dimension pro.
 
I also ran a disk check and it came out fine except for that once.
 
I will run the diagnostics you suggest thanks for the input. I am not nearly an expert at programming but I am above expert when it comes to installing apps.
  
When it happens twice it would seem there is an incongruency with D Pro  and/or command center (which i used both times) and Windows.
 
Dimension Pro is not telling command center it is done.
 
 
 

Make sure when installing Dim Pro that some other window isn't hidden behind other open apps, waiting for a confirmation from you

Ive had some experiences with backing up using SSD drives that remind me of this. My attempts to backup my music PC (chock full of big files of course) would go for hours, sometimes endlessly, sometimes terminating with an arcane error message, something about "semaphores", as I recall. The SSD was an one of the smaller, USB-powered ones, but with enough capacity. When I switched to a more robust SSD (larger, but also with separate AC power) the backup worked flawlessly. I don't know the technical reasons behind this--and it may be something completely different--but it seemed to suggest that all SSDs aren't created equal.

Sheanes
whenever I used to have something like this, first thing to do is shut down and restart the computer.
then try if a disk is heavily fragmented and fix that, and then again restart everything.
Dimensions Pro has caused me probs on installing, now I know it's probably due to the fact it uses it's own samples folder on your harddrive under 'Program Files' at Cakewalk 'Dimension Pro'.
Indeed takes quite long to install and it's quite a big folder.
Personally I try not to move folders/files around too much and aim to save them in the correct destination on installing.
Rebooting Windows etc is always the last option for me, try to avoid that as much as you can I'd say.

I have read many sources which suggest you should *NEVER* defrag a SSD

Windows 10 defrags drives automatically. Check out sequoiaview great app to visualize drive storage and yes I looked for background windows asking for user input while installing Dimension Pro. There were none. Also, rapture installed fine. If there was a problem with the drive it had numerous opportunities to fail during these other installs. 
 
Briefly a window came up showing it was unpacking samples then it disappeared yet command center stayed open.
 
Both times Dimension Pro seemed to install correctly. It opened and worked fine in Cakewalk. The problem was I had to shut off command center manually in spite of its complaint that a program (It said) was still installing, after waiting two hours on both occasions.
 
I am just being more careful to create restore points after each and every install of consecutive programs.

Before installing create a directory junction for the multisample folder pointing to the actual location where the samples should go. If you need help with the syntax, provide the full path to the folder on the D: drive and I can provide the command. The folder on D: must exist before creating the directory junction.