Page 1 of 1

To windows 10 (1903) users

Posted: Sun Jun 09, 2019 6:42 pm
by Jerok
Hello Fellow Cubase users.
I have installed windows 10 1903 both via upgrade and clean installation via usb on a couple of different computers.
I have as routine when new version of windows 10 will run SFC / SCANNOW via CMD on all computers.
irrespective of computer, clean installation from usb stick or upgrade found that SFC / SCANNOW finds fault as it repairs
This has nothing to do with upgrading, but seems to be a little bug in the release that is currently up for download.

So incase you have uppgraded to the new windows 10 1903
open the CMD in admin mode and run SFC /SCANNOW
to make sure windows is not having any minor buggs

Other then this i am happy to report
Cubase 10 is working with no issues for me.

/JeRoK

Re: To windows 10 (1903) users

Posted: Mon Jun 10, 2019 1:42 pm
by Prock
Interesting recommendation. Just wondering if there has there been a wide spread reported issue by MS? My system says there is no issues...

My results...
"Windows Resource Protection did not find any integrity violations"

Regards 8-)

Re: To windows 10 (1903) users

Posted: Mon Jun 10, 2019 9:49 pm
by Jerok
Could be some system based Stuff.
As far as i can tell system is working and this is just a ”make sure” situation. No harm in runbing SFC -Scannow
:)

Re: To windows 10 (1903) users

Posted: Sat Jun 15, 2019 3:41 pm
by ca-booter
Did the 1903 update today also, and tested Cubase and other stuff, everything works just fine.
Biggest advantage I guess is the now almost unlimted amount of FLS instead of max.128
A project I was working on with only 15 slots left now says 128(with the Filechecker plugin), I gues this p[lugin does not go any higher.

Re: To windows 10 (1903) users

Posted: Wed Jun 19, 2019 12:53 pm
by Home Studio 87
ca-booter wrote:
Sat Jun 15, 2019 3:41 pm
Did the 1903 update today also, and tested Cubase and other stuff, everything works just fine.
Biggest advantage I guess is the now almost unlimted amount of FLS instead of max.128
A project I was working on with only 15 slots left now says 128(with the Filechecker plugin), I gues this p[lugin does not go any higher.
The new limit is now : 4000 ;)

Re: To windows 10 (1903) users

Posted: Sat Jun 29, 2019 1:10 pm
by ca-booter
I have to reconsider my view on the windows 1903 update.
AFter working a couple of projects in C10 I now have many dropouts and everytime it is the windows ntoskrnl.exe that gives hughe spikes to be seen in the LatencyMon.
I came across some other people having this issue since W10 1903, but noit really a working solution found which worked for me.
Any help on this one? Before the 1903 update I did not have any issues in W10.

Re: To windows 10 (1903) users

Posted: Mon Jul 29, 2019 4:53 pm
by currentsound
ca-booter wrote:
Sat Jun 29, 2019 1:10 pm
I have to reconsider my view on the windows 1903 update.
AFter working a couple of projects in C10 I now have many dropouts and everytime it is the windows ntoskrnl.exe that gives hughe spikes to be seen in the LatencyMon.
I came across some other people having this issue since W10 1903, but noit really a working solution found which worked for me.
Any help on this one? Before the 1903 update I did not have any issues in W10.
Do you have a Sata to Hard Drive Caddy installed? This guy had this problem and fixed it: https://www.drivereasy.com/knowledge/sy ... indows-10/

Otherwise, I don't know. I'll let you know if I have any problems myself. Just had the update come through today.

Re: To windows 10 (1903) users

Posted: Mon Jul 29, 2019 6:58 pm
by Prock
ca-booter wrote:
Sat Jun 29, 2019 1:10 pm
I have to reconsider my view on the windows 1903 update.
AFter working a couple of projects in C10 I now have many dropouts and everytime it is the windows ntoskrnl.exe that gives hughe spikes to be seen in the LatencyMon.
I came across some other people having this issue since W10 1903, but noit really a working solution found which worked for me.
Any help on this one? Before the 1903 update I did not have any issues in W10.
Maybe this update will help.

viewtopic.php?f=283&t=165280

Regards. 8-)