No i did upgraded from 1803 and always do a sfc /scannow and after upgrade it finds integrity violations and repairs it
Turn background apps off -> restart -> Turn background apps on -> restart. But even this fix isnt reliable and sometimes requires more restarts so I currently live with no notifications at all.
My guess it's that you have different types of people here. - one type that enjoys Windows 10 testing for testing sake, installs on VMs and secondary PCs - another type that wants to see the new features and installs once its RTM, but stability is still paramount as it's their main PC I installed RTM versions and Service Packs the day they were released since early Windows XP days, and I never remember having significant issues. There's a reason why XP and 7 are generally praised. Since Windows 10 however, we have this perpetual testing mode, and it affects all the software system. Now Nvidia and Intel and AMD have to keep up with Microsoft doing aggressive changes to their OS and pushing it through the WU as if it's a simple CU. If you're a smaller manufacturer, you'll take even longer to bring your drivers and software up to date. For example, in 1803 I had an issue with KIS and Edge. Edge would crash in the background each reboot. Kaspersky and Microsoft both recognized the bug in the first 1-2 weeks from 1803 being RTM, and said they were working with each other to solve it. It took SIX MONTHS and RS5 to fix it. That is disgusting. And that is a small bug that's somewhat irrelevant, although it will make your Reliability History look like you have the most unstable PC in the world. Now, that bug was replaced by backgroundtaskhost/cortana.signals.dll crashing each reboot, and hey, now you don't even need KIS installed. It's something else this time that causes the crashes. Daily. Others are having those 2 confirmed on the feedback hub entry. Adding to this 2 BSODs and Destiny 2 crashing, NEITHER happened in 1803. Add the file deletion issue for those naive enough to use WU instead of clean installs and dared to have custom library locations. So I'm sure you can see how all this can sour the whole Windows experience and makes one feel like an unpaid tester?
Errr ... yeah, 1 cosmetic error entry and ERRORS MOST LIKELY CAUSED BY DRIVER CONFLICT (the games errors), so only the file deletion bug (NOTE: only appears for KFR users) is left. What a s**tty build, indeed .
^^ Hi brother, I think like this: when things start wrong from the beginning it is evident that they can only end badly there is no way to repair an already unsupported base you understand what I mean by right; if you for some reason NEED to quickly release an operating system of course it is already wrong lol once you need management \ supervision and charge software engineering (among other key elements) everything that was done beforehand and CHECK if everything was gone really tested before the next step and there has to be a central coordination to confirm once again if the really "things" really work and not only get martyred with the projection of 1,000,000 devices operating worldwide !! and absolutely without a technical support of the contrary for WHQL etc. etc ... this is not being professional in each of the sectors of the hive in which Windows 10 is formed...
Sorry for those who experienced problems, but my own is a happy one up to know I decided to upgrade to 1809 manually on my main PC. This was done inside my old 1803. The problems I faced was all cosmetics. No files deletion, no drivers issues and no BSOD. Video editing works fine Office apps works fine Programming in visual studio works fine Music no issues And finally thanks to this 1809, I become active in this awesome MDL Forums, discovering great peoples hidden behind their avatars but visible through the words they post.
"Likely" means nothing. Could be that, could be something else. What I do know is 1803 doesn't present these issues. And yes, do ignore the 6 months release cycle that's forcing drivers into obsolescence and the increased pressure to keep up with Microsoft's cycle. Also ignore how these were NON-ISSUES in Win 7. This is supposed to be the STABLE branch. Not Insiders. Not testing. BSODs while gaming on Pascal+Z370 without OCs and after countless stability testing done is NOT STABLE.
I agree, 1809 isn't stable on my hardware, 1803 is fine, i'm actually using 1607 LTSB but i can only recommend LTSB 2016 or 1803 for now. I didn't had any BSODs on 1809, i only had issues with stuttering in games, tried everything without success. I also noticed that when i tried to install the chipset driver, took almost 2 minutes to install, in 1803/1607 is blazing fast to install (5 seconds)... In my opinion, 1809 isn't stable, is it working in the X hardware? Good. But if isn't properly working on the Y hardware, isn't stable, and in my case, i'm using the Y hardware, but hey, check your drivers! i always use the latest drivers, chipset, audio, graphics etc etc... so, it all depends of your hardware.
Huh, stability tests say nothing at all. Had several occasions my rigg was running Prime stable even with OC (tested at least 6 times with no problems), still BF3 quitted with instant BSOD. Since that moment games are my stabilty tests. The version is fairly new, no-one can expect flawless drivers in all situations at that moment ... and to be fair the build is still IP .
Well there's a serious reason why MS has withdrawn this build. In one sentence: it's too buggy to be a production release. Not having problems with it doesn't mean it's like this for everyone. A stable build must cover at least the absolute majority of users, fixing smaller problems with cu later. It's not about negativity,but I have to agree with @s1ave77 about his statement. Btw I also had the wrong time display bug, but it fixed itself on one machine and still persists on another.
Not sure about that, there are various stuff in windows that trigger or not depending on that reporting. The nt api functions actually report the incorrect percentage. Anyway, this is actually a very old bug, since I've been experiencing it for sure in 1709 (and probably even older versions). I'm talking about FSB-overclocked CPUs (my htpc Core2) reporting up to rated fsb, so it will say usage is 100% when reaching 2Ghz when it actually goes to 2.8Ghz (and it's not SpeedStep, that one is measured correctly, albeit with the same limitation)