Overclock.net - An Overclocking Community - Reply to Topic

Thread: [Official] The Windows 10 Club Reply to Thread
Title:
Message:

Register Now

In order to be able to post messages on the Overclock.net - An Overclocking Community forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.
User Name:
If you do not want to register, fill this field only and the name will be used as user name for your post.
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:

Log-in


  Additional Options
Miscellaneous Options

  Topic Review (Newest First)
09-18-2019 12:43 PM
kgtuning
Quote: Originally Posted by Catscratch View Post
Quote: Originally Posted by kgtuning View Post
Lol never.
Probably true [IMG class=inlineimg]/forum/images/smilies/biggrin.gif[/IMG] Hopefully there will come a cumulative update that fixes search and cpu usage and breaks something I never use [IMG class=inlineimg]/forum/images/smilies/biggrin.gif[/IMG]
My guess is on the next update it’ll be fixed. But anything is possible. Maybe one day it’ll be stable...
09-18-2019 11:48 AM
Catscratch
Quote: Originally Posted by kgtuning View Post
Lol never.
Probably true Hopefully there will come a cumulative update that fixes search and cpu usage and breaks something I never use
09-18-2019 10:58 AM
kgtuning
Quote: Originally Posted by Catscratch View Post
I've been skipping 2 cumulatives now. When will it end ? I mean when will they deliver a working update that won't kill other things ?
Lol never.
09-18-2019 09:33 AM
Catscratch I've been skipping 2 cumulatives now. When will it end ? I mean when will they deliver a working update that won't kill other things ?
08-16-2019 09:55 AM
ThrashZone Hi,
MS is updating 1809 regardless to 1903.

But you could mount a 1809 iso from 1709 or which ever build your on
I would use a system image rather than 10's roll back method though way cleaner break

But you will need to mount 1809 without an internet connection or you'll just end up back on 1903 again.
08-16-2019 08:58 AM
Mooncheese Hi, yeah so I did updated from 1703 to 1903, surprisingly (shockingly actually) without any issues whatsoever (I did wait over three months for them to work out the issues) but there is one rather serious issue for me, and that's that Nvidia 3D Vision doesn't work with the newer display drivers with 1903. With 1809 and below, we the 3D Vision community have managed to add the 3D Vision aspect of the display drivers to all newer drivers via 3D Fix Manager, but with 1903 this no longer works and youre stuck with the last driver that officially supports 3D Vision: 425.31. This is problematic if you wish to play a game some 6 months hence, say Doom: Eternal, as youre now confronted with the dilemma of having to update the display driver, and say goodbye to 3D Vision, or just don't play the new title. It's not just the games, but I have a vast library of 3D movies as well that I wish to continue to enjoy.

So I'm thinking about reverting to 1809, but I didn't upgrade from 1809, and I need to know if "Go back to the previous version of Windows 10" under Recovery options will install 1809 or 1703, considering I was on 1703 before upgrading to 1809. I've extended the period from 10 days to 60 days while I figure this out: https://www.intowindows.com/go-back-...after-10-days/ f

Any help greatly appreciated!
08-06-2019 02:27 PM
Mooncheese Is anyone having issues with Intel + Nvidia hardware with 1903 after updating (not clean install).
08-04-2019 03:21 AM
Catscratch Hey semi-dead thread

Here's a quick look on DPC latency issue fixed or not with the latest cumulative update kb4505903

This is before: Yellows happen when no app is requesting anything from the system. Reds are after running cpu-z and polling data. Second pic is cpu-z idle to cpu-z benchmark.



This is after: Idle is in yellows but cpu-z does not produce reds. Greens are lower when running the benchmark


These are on a relatively fresh windows 10 pro 1903 install on my ryzen setup.
07-10-2019 02:22 PM
ThrashZone
Quote: Originally Posted by valvehead View Post
Yep. Looking at CBS.log showed errors related to PowerShell Defender modules. I don't know if any of this would cause problems down the road, but thankfully running dism and sfc again solved my errors.


This is only the 2nd time I have found system errors after an update. I have had very few minor problems with Windows 10 since switching over three years ago. I have to wonder if many of the people that have major issues when upgrading (e.g to 1903) have tons of system errors that need to be repaired.
Hi,
Same deal on .175 of 1903 too so indeed WD crapware errors is the cause.

Thanks for the heads up
07-10-2019 09:15 AM
valvehead
Quote: Originally Posted by ThrashZone View Post
Hi,
Yep sure enough throwing errors
Had to also scannow after using restorehealth to actually report anything being repaired restart back to clean.

A while back sfc was reporting falsely errors guess it's doing it again
Someone pointed out windows defender update caused it which I wouldn't doubt it seeing the new bs account protection features if not used may throw an error.

Yep. Looking at CBS.log showed errors related to PowerShell Defender modules. I don't know if any of this would cause problems down the road, but thankfully running dism and sfc again solved my errors.


This is only the 2nd time I have found system errors after an update. I have had very few minor problems with Windows 10 since switching over three years ago. I have to wonder if many of the people that have major issues when upgrading (e.g to 1903) have tons of system errors that need to be repaired.
This thread has more than 10 replies. Click here to review the whole thread.

Posting Rules  
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off