Windows 10

Caporegime
Joined
8 Nov 2008
Posts
28,997
Have you done sfc /scannow to see if anything is corrected after the update?

No, I've not heard of that before (I've seldom used the command line previously anyway). I've bookmarked a rough guide and am looking into it at the mo. Cheers for the suggestion.
 
Soldato
Joined
10 Jul 2010
Posts
6,277
My 1709 version of Windows 10 tried to update 10 1803 tonight, with no warning other than the update will be applied upon reboot. So I ran CCleaner and Bleachbit straight away to delete the installation files, rebooted, then blocked the 1803 update with wushowhide.diagcab - so far so good and still on 1709.

But I do think my 1709 has had it's day now, even though there is absolutely zero incentive for me to move to 1903. Plus I keep reading that it's plagued with latency spike issues too. :(
 
Caporegime
Joined
8 Nov 2008
Posts
28,997
ng9gk8.png
 
Soldato
Joined
28 Sep 2014
Posts
3,430
Location
Scotland

Try run each DISM command a time attempt to repair corrupted Windows files.

Copy and paste each command on powershell and press enter:

DISM /Online /Cleanup-Image /CheckHealth

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /RestoreHealth

Then run sfc /scannow again to see if it fixed all corrupted files.

If not then try DISM repair using your Windows ISO or USB's source WIM image to replace corrupted files with matched versions. Open File Explorer and check which drive letter your Windows 10 installation media is used whether it is letter D, E or G then replace Source:F with your drive letter such as Source:E.

DISM /Online /Cleanup-Image /RestoreHealth /Source:F:\sources\install.wim

Then run sfc /scannow again.

If it still not worked then you will need to reinstall Windows 10 again that will replaced all corrupted files. Make sure you disabled anti-virus first before run Windows 10 setup.
 
Caporegime
Joined
8 Nov 2008
Posts
28,997
@AthlonXP1800 Thanks for that info.

I entered the commands and received these messages:

24xdpb5.png


I decided to restart the PC and although it still chugs at the beginning for a minute or so, it does seem to be doing it for less time than before. I might be wrong on that but that's what I think at present.

I'm doing a new build in a couple of months and was thinking of getting some more storage/drives anyway, as I think a new and untouched fresh SSD or NVME might be the answer.
 
Last edited:
Caporegime
Joined
8 Nov 2008
Posts
28,997
Just rebuild, back it up using Macrium Reflect and then open the backup image after rebuild and drag your games etc back.

The other day I backed up drive C and copied it on to my D drive. I'll look into macrium, maybe even this evening. Ta.
 
Last edited:
Soldato
Joined
25 Nov 2005
Posts
12,444
Bit of a weird one but it seems the latest security update has futzed something up in my settings for Win10

Previously I could switch on the rig, go make a cup of coffee and breakfast and come back, login and all programs would have been loaded before login (only user on the rig)
Now they only seem to load after login

It's not so much of an issue because I'm on SSD but I'm still finding it a little annoying, anyone know what changed this or how can I get the previous behaviour back ?
 
Associate
Joined
7 Mar 2005
Posts
1,630
@Minusorange - Under Settings > Accounts > Sign-in Options make sure that "use my sign in info to automatically finish setting up my device and reopen my apps after an update or restart" is enabled.
 
Soldato
Joined
10 Jul 2010
Posts
6,277
I've tested 1903 with the latest drivers and software and LatencyMon revealed issues with dxgkrnl.sys and ntoskrnl.exe. Googling reveals a LOT of others experiencing the same problem with 1903.

I must admit, I had music playing for a bit and didn't hear anything wrong. But I think I'll cling onto 1709 for a bit longer until the latency issues are rectified - by which time more problems will have surfaced to put me off. :p
 
Man of Honour
Joined
13 Oct 2006
Posts
90,805
I've tested 1903 with the latest drivers and software and LatencyMon revealed issues with dxgkrnl.sys and ntoskrnl.exe. Googling reveals a LOT of others experiencing the same problem with 1903.

I must admit, I had music playing for a bit and didn't hear anything wrong. But I think I'll cling onto 1709 for a bit longer until the latency issues are rectified - by which time more problems will have surfaced to put me off. :p

Not generally a problem with normal music stuff but if you are using a professional low latency audio interface it does and is causing people issues - another reason why the current updates approach is just stupid because it is impossible even with a full testing department to catch all these problems and for people who do audio production that is a big problem.

For some people, though seems fairly much a very small minority so far with 1903, it is causing noticeable stutter in games where high framerates and low latency are critical. (EDIT: Looks like similarly a small number of people are having video streaming stutter and/or dropped frames as well with the update).

Cue rebuttals of "but I googled and found someone with similar problem in Windows 7" totally missing the point.
 
Soldato
Joined
10 Jul 2010
Posts
6,277
Not generally a problem with normal music stuff but if you are using a professional low latency audio interface it does and is causing people issues - another reason why the current updates approach is just stupid because it is impossible even with a full testing department to catch all these problems and for people who do audio production that is a big problem.

For some people, though seems fairly much a very small minority so far with 1903, it is causing noticeable stutter in games where high framerates and low latency are critical. (EDIT: Looks like similarly a small number of people are having video streaming stutter and/or dropped frames as well with the update).

Cue rebuttals of "but I googled and found someone with similar problem in Windows 7" totally missing the point.
When MSMG Toolkit properly supports 1903, I might give it another go. But I'm in no great rush right now.
 
Soldato
Joined
28 Sep 2014
Posts
3,430
Location
Scotland
Not generally a problem with normal music stuff but if you are using a professional low latency audio interface it does and is causing people issues - another reason why the current updates approach is just stupid because it is impossible even with a full testing department to catch all these problems and for people who do audio production that is a big problem.

For some people, though seems fairly much a very small minority so far with 1903, it is causing noticeable stutter in games where high framerates and low latency are critical. (EDIT: Looks like similarly a small number of people are having video streaming stutter and/or dropped frames as well with the update).

Cue rebuttals of "but I googled and found someone with similar problem in Windows 7" totally missing the point.

Sorry you totally missing the point and not listened properly, people used professional low latency audio interface had caused people issues with Windows 7 too.

http://forum.cakewalk.com/Audio-Drop-outs-in-Sonar-7-Producer-using-Windows-7-64bit-m1925065.aspx

Interesting disabled hyper-threading in BIOS seemed fixed Windows 7 audio drop outs issues with Sonar 7 Producer.

https://audiosex.pro/threads/audio-drop-outs-on-cubase-10-focusrite.42875/

Back in Jan 2019 JudoLudo had audio drop outs issues with Cubase Elements 10 used Focusrite Scarlett 6i6 1st Gen with stable and beta Focusrite drivers on Windows 10 LTSC. The Pirate posted said Focusrite had issues with drivers all the time. Paul Pi posted said he had same issues with Cubase Elements 10 and Windows 10 1809 then he later installed Windows 7 and had no issues with Cubase Elements 10. BUT Paul Pi realised he made a mistake admitted Windows 7 still had issues with audio drop outs in last post.

...it may not at all be relevent in this instance, but on any version of windows you should ensure the focusrite is directly connected to a USB2 port on the PC - not via usb hub or USB3 port - i once made the mistake of plugging my Scarlett into a USB3 port (on win7) and it became most unstable, exhibiting random crackles, dropouts etc also...

Interesting isn't it! Plugged RME FireFace800 and Focusrite Scarlett 2i4 1st Gen in USB 3.0 ports or USB Hub caused audio drop outs and then plugged it in USB 2.0 ports did not caused audio drop outs on both Windows 7 and 10.

So you cant blamed Windows 10 and latest Windows 10 updates, guess maybe you should blamed on either AMD, ASMedia and Intel on poor USB 3.0 drivers for Windows 7, 8 and 10.

You replied to my post with 2 links in How to download pre 1903? thread.

https://forums.overclockers.co.uk/posts/32824791

The issue seemed died down a month ago with no further posts on reddit and 29 June on audiosex forum so it seemed issues is already fixed with latest 1903 updates. Focusrite audio team would not reproduced latency issue with 1903 confirmed they not had issues with 1903.

Interesting to see no further replies in How to download pre 1903? thread, looked like RyzenJunkie resolved 1903 issue by followed Focusrite guide Optimising your PC for Audio on Windows 10.

I found Focusrite has guides for Windows 8, Windows 7, Windows Vista, Windows XP and Mac.

https://support.focusrite.com/hc/en-gb/articles/207546695-Optimising-your-PC-for-audio-on-Windows-8

https://support.focusrite.com/hc/en-gb/articles/207359245-Optimising-your-PC-for-audio-on-Windows-7

https://support.focusrite.com/hc/en...Optimising-your-PC-for-Audio-on-Windows-Vista

https://support.focusrite.com/hc/en-gb/articles/206674219-Optimising-your-PC-for-Audio-on-Windows-XP

https://support.focusrite.com/hc/en-gb/articles/207546515-Optimising-your-Mac-for-Audio

Interested to see Mac also has same latency issue with professional audio interface as all Windows versions.
 
Man of Honour
Joined
13 Oct 2006
Posts
90,805
Sorry you totally missing the point and not listened properly, people used professional low latency audio interface had caused people issues with Windows 7 too.

http://forum.cakewalk.com/Audio-Drop-outs-in-Sonar-7-Producer-using-Windows-7-64bit-m1925065.aspx

Interesting disabled hyper-threading in BIOS seemed fixed Windows 7 audio drop outs issues with Sonar 7 Producer.

https://audiosex.pro/threads/audio-drop-outs-on-cubase-10-focusrite.42875/

Back in Jan 2019 JudoLudo had audio drop outs issues with Cubase Elements 10 used Focusrite Scarlett 6i6 1st Gen with stable and beta Focusrite drivers on Windows 10 LTSC. The Pirate posted said Focusrite had issues with drivers all the time. Paul Pi posted said he had same issues with Cubase Elements 10 and Windows 10 1809 then he later installed Windows 7 and had no issues with Cubase Elements 10. BUT Paul Pi realised he made a mistake admitted Windows 7 still had issues with audio drop outs in last post.



Interesting isn't it! Plugged RME FireFace800 and Focusrite Scarlett 2i4 1st Gen in USB 3.0 ports or USB Hub caused audio drop outs and then plugged it in USB 2.0 ports did not caused audio drop outs on both Windows 7 and 10.

So you cant blamed Windows 10 and latest Windows 10 updates, guess maybe you should blamed on either AMD, ASMedia and Intel on poor USB 3.0 drivers for Windows 7, 8 and 10.

You replied to my post with 2 links in How to download pre 1903? thread.

https://forums.overclockers.co.uk/posts/32824791

The issue seemed died down a month ago with no further posts on reddit and 29 June on audiosex forum so it seemed issues is already fixed with latest 1903 updates. Focusrite audio team would not reproduced latency issue with 1903 confirmed they not had issues with 1903.

Interesting to see no further replies in How to download pre 1903? thread, looked like RyzenJunkie resolved 1903 issue by followed Focusrite guide Optimising your PC for Audio on Windows 10.

I found Focusrite has guides for Windows 8, Windows 7, Windows Vista, Windows XP and Mac.

https://support.focusrite.com/hc/en-gb/articles/207546695-Optimising-your-PC-for-audio-on-Windows-8

https://support.focusrite.com/hc/en-gb/articles/207359245-Optimising-your-PC-for-audio-on-Windows-7

https://support.focusrite.com/hc/en...Optimising-your-PC-for-Audio-on-Windows-Vista

https://support.focusrite.com/hc/en-gb/articles/206674219-Optimising-your-PC-for-Audio-on-Windows-XP

https://support.focusrite.com/hc/en-gb/articles/207546515-Optimising-your-Mac-for-Audio

Interested to see Mac also has same latency issue with professional audio interface as all Windows versions.

I have to hand it to you that is a convincing arguement for just how stupid the approach to updates is in Windows 10.

But yet again the point flew right over your head...
 
Last edited:
Soldato
Joined
22 Sep 2006
Posts
3,323
Not generally a problem with normal music stuff but if you are using a professional low latency audio interface it does and is causing people issues - another reason why the current updates approach is just stupid because it is impossible even with a full testing department to catch all these problems and for people who do audio production that is a big problem.

For some people, though seems fairly much a very small minority so far with 1903, it is causing noticeable stutter in games where high framerates and low latency are critical. (EDIT: Looks like similarly a small number of people are having video streaming stutter and/or dropped frames as well with the update).

Cue rebuttals of "but I googled and found someone with similar problem in Windows 7" totally missing the point.

Gaming problems never go away for some people, all I can say is Win10 has been fine for me in gaming with regards to sound etc, problem with gaming is there will always be problems with some gamers, these sort of things are hard to fix, because you can't get every gamer with 100% stability with no issues. I would be lying if I said I never had any gaming/audio issues on any of my Windows Operating Systems I have owned. There still a bug sometimes in Mass Effect 3 multi-play where audio goes silent, do I blame Windows, drivers or the game? (game IMHO)..Point is there are bugs in everything ie games,OS,drivers etc ,that's why you get new updated drivers for bugs fixes and improvements, same goes for Windows updates, but you will never catch them all or new ones will appear, as you are aware even with new updates it can break something old.

End of the day not much you can do apart from report your valid issues you to have to Microsoft and hope for the best ie possible fix or solution (yes I know I keep saying that). Just remember no OS is perfect just like users ie some will have issues regardless of right or wrong.

Btw latency issues are nothing new, remember the old USB latency issues? I do. You can bet some new issue will pop up down the road.

We can all moan and bitch about it, but only Microsoft can fix them. Be patient and hope for the best is all you can do (apart from reporting it that I'm sure you have).

Right I 'm off to game online :) .
 
Back
Top Bottom