Discussion in 'Operating Systems' started by Extraordinary, Dec 11, 2019.
i'm glad windows didn't push the 2004 build to me in widows update yet
So i updated manually now, luckly you dont need to set too many prev. settings on your os not like before with prev. "large" updates Also no "bugs" yet like start menu lag and other things mentioned here.
not sure what you getting at, but it does not change the fact drivers got upgraded and bypassed WU all together
What the hell - 144.001Hz? Before update it was 144Hz - can anyone verify this?
AOC 24G2U, Nvidia 446.14:
windows doesn't display it rounded to a whole number anymore.
but your display was indeed always 144.001Hz
I see but how it looks like in your case?
I don't understand, for me it looks like it is bugged somehow - just look here:
59 = 59.940
So why in the first screen you can see 144.001Hz and in the second normal value 144Hz? System glitch?
Before update in both places it was 144hz without .001Hz addon.
Can anyone else verify this?
its just reporting differences.
I even tried to reinstall Nvidia and monitor drivers using DDU and checked that this is not a specific glitch after the update.
I understand that 144Hz and 144.001Hz are the same values but I wanted to know why now after the update my system started to show 144.001Hz in one place and 144Hz in the other.
If after the update everyone has such values then it is not an error so I would like to know if someone else noticed this.
Sometimes there isn't an explanation, microsoft just changes things for undisclosed reasons.
Thank you for your help and support.
The DISM issue with 2004 (build 19041.x) was recently added on May 28
edit - so much for using DISM /cleanup-image /restorehealth on v2004 - will wait for a fix next month
Cumulative Update for Windows 10 Version 2004 KB4557957 Build 19041.329 (Mostly security updates)
So that's what this one does, mostly security related but it updated quite a number of files from a quick glance although if it is related to various security issues and possibly minor bugs that's not surprising.
Expected a bit more around some outstanding issues like the DISM one above or the disk defragment issue but those could still land later now that 19041.x is wrapped up and fixes are rolling out over the next couple of months.
And then we start it all over once more for 20H2 or whatever the next build will be. (21/H1 and just going with larger yearly builds again?)
Don't think even MS knows what's next, the whole covid business isn't helping either.
Yeah that situation is becoming a real hassle as it's slowly diminishing so people just treat it like it's gone immediately which causes problems because well it isn't and then the uncertainty around what might still come.
Business wise there's a whole order and organization thing around working from home or getting back to the actual office and world-wide businesses having to solve how this is handled from country to country whether it's more lax like here or handled far more strictly.
Windows 10 itself I don't really know what the plan is, Vanadium 1 I think this new lineup of builds is starting with moving away from Redstone (In turn moving away from Threshold.) but the fast build is just a new Windows build which I don't believe is slotted into any specific yearly or bi-yearly lineup yet it's just the latest fast-ring release and can be anything from there.
19041 / VA1 here just hit release in full and is slowly rolling out in the usual staged fashion and might be blocked a bit as some compatibility issues are found and resolved and more monthly cumulative patches with this first patch resolving security concerns and probably some other smaller outstanding issues then perhaps slowly rolling in fixes found in newer builds or addressing other existing or newly discovered issues as well.
I suppose the status is better than some of the earlier build launches and this should also break away from the little thing that was 1903 with a mini patch making it 1909 to fill up the 19H2 requirement or criteria as Microsoft initially appeared to be moving away from bi-yearly to yearly builds but then yeah Corona and all that and now things are a bit messy.
Or what to say, there's probably some plan or structure for how to proceed on Microsoft's end of things but there might be some delays or hiccups.
I should look up the state of things better, none of the issues I am aware of appear to be breaking or otherwise severe but I'm probably missing some of the newer developments once this build hit general availability.