Need help with Cakewalk setup on new computer

(I have a thread about this in the Computers forum but am not getting very many views so, I thought I would try it here. I didn't know how to move it here or delete the other one. If double posting is not allowed, please Admin, delete one.)
 
New computer = Dell XPS - i7 8700 6 core - 16 gb 2666 RAM - two 2 Tb 7200 RPM hdd's - Windows 10 - Focusrite Saffire Pro 40 & Octapre
When I hit play, I get the spinning blue thing for about a second. 
The first time I set up looping points it runs to the end of the loop and stops for about a second before returning to the start of the loop. This only happens the first time, after that all looping acts normal.
Some (not all) plugins cause gapping when assigning to a track during playback.
While editing tracks, everything is sluggish acting. I'm stumped.
Is this normal behavior for CbB? I am a LONGTIME Sonar user and these behaviors started showing up near the end of Platinum for me (On my old, much lower powered computer). I do not remember any of this happening in earlier versions of Platinum. (BTW, I also have Studio One and, everything works fine on it but, I really prefer to use Cakewalk)
Any thoughts from anyone?

what driver-mode are you using?

I am using ASIO.
No, I cannot afford to add RAM at the moment.
As far as I know, I have updated all drivers, programs, plugins, etc.
I will try loading a project with absolutely no plugins and see what happens. As it is, if I toggle off all plugins, it still does it.
Also, LAtencyMon tells me everything is fine for running audio.
Thanks for the suggestions!
The reason I bought this new computer is because this same thing was happening on my old computer which led me to believe it was failing (It was a six year old i5 with half the RAM of this new one). So, now the same problem is still happening on this new machine. Very frustrating.

RAM is not the issue. My i7-8700 showed up today and I am in the process of installing a better PSU and moving my drives over. It will be a clean Windows 10 Pro 64 bit environment and I'll need to install a bunch of stuff before I can test audio recording in CbB.
 
ASIO should be fine. What you are describing is NOT NORMAL.
Are you testing with a clean empty project?
Also, pay attention to anything scook says.

stickman393 - I always listen to scook! No, I am not testing with a clean, empty project. I am testing with recently recorded tracks. I will try with a clean, empty project.
chris.r - Actually, I have not used Studio One on this new computer yet besides just checking to see if this issue was present in it.
scook - I was under the assumption the MIDI settings only affected MIDI. I do not run MIDI at all. I was also under the assumption that ASIO is always the best driver (That seems to be what we are always told.) Of course, I will try these things, though.

Cakewalk uses your computer  soundcard to delineate its inputs.  I am using the sound on my motherboard because it actually sounds good.  And is a pretty high quality card.  Look at the Sound Settings or anything that affects sound in Control Panel.  Make sure you set up your inputs from there.  ASIO4All  is ideal, but it may be easier to get it working in MME mode.  But you have to use the Control Panel programs for your input.  Sonar reads those.   As far as 8 Gigs it should work well as long as you don't have a ton of programs running in the background.  I have 12 on this machine and everything seems to run fine.  

rodreb
In Preferences>Audio Data the Global Audio Folder points to C:\Cakewalk Projects\Audio Data. That is not what I use. I have all my audio data going to F:\ song name\Audio. Should these match? I checked, the location on C: is empty. Is this a possible conflict?

The Global Audio folder default is "C:\Cakewalk Projects\Audio Data." On startup, the program will actually reset the Global Audio folder to the default if the path provided is unreachable. This used to be a problem for those wanting to use a Global Audio on a removable drive. It is rarely an issue with internal drives. I like to have the Global Audio folder on the same drive as the active projects. Not sure if it matters any more. It is definitely not the cause of the problem described in the OP.
 

rodreb
Also, in Device Manager, in Properties>Events for my audio drive that I installed, it says "Device not migrated". Is this cause for concern?

Could be. There are a lot of hits on "Device not migrated" on Google. I will defer to Windows experts about the this error.

Do you still have the old machine available? When I loaded my new machine I actually launched SONAR on both so that I could walk the dog on each page in preferences. With all of the tweaks done over time, a new installation will lose them which is why a side-by-side comparison is easiest to verify.
 
I did catch one LatencyMon post (I think it was yours), which showed Automatic Network Discovery being on. Type "Manage Advanced Sharing Settings" in the Windows Search, and you will see "Network Discovery" under each section (Private, Guest or Public). Be sure to check "Turn off network discovery," which is a ping the system does every 3-4 seconds. That particular "feature" is the #1 latency issue IME - if you are adding things to the computer, manual is safer than having Windows trying to connect to everything it sees every 4 seconds of its life.
 
This item is not an easy task, and more for reference. Definitely start with Task Manager as mentioned above, but keep the following in mind. On a new machine, "Services" often need to be scrutinized. Unless something is required to run the machine, "Automatic" startup is not recommended. Most of these should show in the task manager; however, some are hidden and will only show up in Services (can type "Services" in the startup search). Right-clicking services that look odd and chaning startup type to "Manual" will force them to only launch when you launch them as a user. All of Adobe's services fall into this category, yet Adobe is also religious about resetting them to "Automatic" as well. All apps that have "automatic updates" or similar should be manual.

@ Rod,
 hope you will get it fixed, but don´t have any idea how.
 
It´s also interesting for me cause one day in the future I
will have to look for a new box - hopefully with a configuration which allows me
to work with the Focusrite Saffire Pro 40 - love the sound of this  audio interface.
 

Any how , thank you for sharing  your experience so far -
giving a lot of helpful  infos about the firewire card , DAW aso.
Hope that your helpfulness will get paid back.
 
Pragi
 

FWIW i had this problem/message when using my Boss GT100 multi pedal with W10 creators update in April

Tonelab (the software you use to alter the settings on the unit) would not rcognise or shake hands with the hardware. I’m using W10 prof. However on my laptop, running W10 Home, the unit worked perfectly, with the same update. Go figure ...... !

So, what fixed the issue for me, is you need to go into Privacy settings and make sure the mic options are turned ON. Then reboot. Creators edition, for whatever reason, defaults it OFF for some people. If you google you’ll find you’re not alone with this message.

This may (or may not) help you !

Cheers,
Jerry

So, at this point, I have tried everything I can and here's where I am....
Everything "works" but, whenever I press Play, I get the spinning blue disk with about a one second hesitation before play actually starts. When I set up a loop, the first time through, at the end of the loop, it stops play and hesitates (with the spinning blue disk) for about one second. After that first time through, the loop plays fine.
This is the same behavior I had on my old computer (which is what led me to getting a new computer).
The constants between my old computer and the new computer are Cakewalk by BandLab and, my firewire card, which I transferred from my old computer to my new one. (NOTE: The firewire card is a Siig unit with a TI chipset) 
All my issues started about six months ago on my old computer. It was over six years old and I just assumed it was the culprit, that's why I got this new computer.
Unless anybody has any better ideas, I guess I will have to buy a new firewire card and see if it makes any difference.
Oh, also, Studio One works just fine on both computers. No lag, no hesitation, works perfectly. I just REALLY prefer Cakewalk to Studio One.

scook - This is so frustrating. I even went so far as to buy a new computer to try to resolve this issue. Yes, I do believe this all started right near the end of Platinum (I have lost track since it's been going on so long).
This being a new computer, everything is, obviously, a fresh install.
The driver for the Focusrite Saffire Pro 40 is still the same version as before. As I said, I transferred my old firewire card. (I wanted to buy a new one but, my Wife said I had already spent too much$$ Ha ha!!) I guess my next thing is to buy the new firewire card and see if that fixes things.
 

Hmmmm, failure to migrate, slow data transfer from disc to memory,, this kind of reads like......… You may quite possibly be experiencing the first stages of mechanical hard drive failure with your audio drive.... (?)
 
You did mention transfer these problems over from your older system.
 
And you should also experience a very noticeable increase in speed and power from a 6 year old i5 to a current tech i7.