Cooler Master MasterBox NR600 review
MSI to unveil 10th Anniversary RTX 2080 Ti Lightning Edition
Ballistix Elite 3600 MHz 16GB Dual Channel DDR4 review
ASUS ROG Rapture GT-AC2900 Gaming Router review
Asustor Nimbustor 4 (AS5304T) NAS Review
Promo: VIP-SCDKey Games and Windows 10 / Office
be quiet! Dark Rock SLIM review
Gigabyte GeForce GTX 1660 Gaming OC review
Edifier G4 Pro Headset review
Microsoft Office 2016 Pro and Windows 10 Pro for just $34
Windows 10 October update now fully available
It goes without saying that the Windows 10 October update rollout has had a few snags. It was redacted, then halted and then paused for specific end-users with even more specific hardware setups.
As it seems now, the light is finally green and the Windows 10 October update is now available for everybody. Roughly a month or so ago Microsoft actually even relaunch the update, but even then some problems had risen. Microsoft even warned users to now scan for the new update and download/install it.
Most users need to update to the new build manually and that is still adviced. We expect that over time the rollout will be automated with auto updates. If you peek at the history updates for Windows 10 there is this new update today, now also including advanced users:
Rollout Status as of December 17, 2018: Windows 10, version 1809, is now fully available for advanced users who select "Check for updates" via Windows Update.
Let's hope all problems have been resolved, but enthusiasts can now search and install the update via their PC.
Microsoft might offer Windows 10 as a subscription - 12/17/2018 09:43 AM
Microsoft has been playing with subscription-based models of their software for a while now, much like Office 365. From the looks of things. From the looks of it Microsoft could soon do the same with...
Microsoft fixes lots of issues with Windows 10 October 2018 Update KB4469342 - 12/07/2018 08:51 AM
Microsoft released an extensive update that will fix many issues with the plagued Windows 10 update. The company released cumulative update KB4469342, which Microsoft claims, has been thoroughly test...
Microsoft is working on Foldable Windows tablet - 12/05/2018 10:07 AM
Microsoft would once again work on a competitor for Chrome OS, Google's lightweight operating system for cheaper laptops. This time it would be a folding tablet....
Promo: Get Windows 10 Pro OEM under 12$ - 12/03/2018 09:59 AM
URCDKey is a license site available for various platforms, whether for software or games. This time URCDKeys brings as a novelty the offer at a competitive price known Microsoft widow 10 Pro OEM. Ex...
Windows 10: New Intel Microcode for Spectre V3a, V4 & L1TF Gets Released - 11/28/2018 06:15 PM
Microsoft began rolling out Intel's new countermeasure code against the Spectre V3a, Spectre V4 and L1TF vulnerabilities through Windows Update. It starts with a patch for the latest version of Wind...
anticupidon
Senior Member
Posts: 3514
Joined: 2008-03-06
Senior Member
Posts: 3514
Joined: 2008-03-06
#5618637 Posted on: 12/18/2018 07:05 PM
October is spelled D e c e m b e r in Microsoft's headquarters.
October is spelled D e c e m b e r in Microsoft's headquarters.
Fox2232
Senior Member
Posts: 8819
Joined: 2012-07-20
Senior Member
Posts: 8819
Joined: 2012-07-20
#5618643 Posted on: 12/18/2018 07:14 PM
You must be mistaken, it is February edition.
Anyway, I am on insider 18290. It is bit less problematic.
October is spelled D e c e m b e r in Microsoft's headquarters.
You must be mistaken, it is February edition.
Anyway, I am on insider 18290. It is bit less problematic.
Mateja
Member
Posts: 99
Joined: 2014-02-01
Member
Posts: 99
Joined: 2014-02-01
#5618675 Posted on: 12/18/2018 08:35 PM
or better yet, 18298
lots of bug fixes. and that Russian site w/ the ISOs doesn't 404 anymore. lol
18290. It is bit less problematic.
or better yet, 18298
lots of bug fixes. and that Russian site w/ the ISOs doesn't 404 anymore. lol
waltc3
Senior Member
Posts: 876
Joined: 2014-07-22
Senior Member
Posts: 876
Joined: 2014-07-22
#5618676 Posted on: 12/18/2018 08:37 PM
I moved back to the slow ring in the Insider's group after four years of being in the fast ring--started Win10 Insiders Oct 1, 2014, first day of the program. I downloaded 17763, the Oct release, the first time it was offered, before it was ever pulled, and have been there ever since--with no problems to report. 100% stable. Now on build 17763.168 (after a couple of cumulative updates.) I'm getting sort of tired of Microsoft trying to reinvent the wheel every six months, however. For me, 17763 (original Official Oct Windows release) is rock stable and always has been--bug reports can have so many causes other than OS bugs, it's not funny, so I don't pay attention until I myself actually encounter a described "bug," and in the case of the Oct release, I never did encounter such bugs--no little ones, and certainly no show-stoppers.
To illustrate what I mean, here's what Microsoft itself says about it's latest fast-ring insider release, build 18298:
REMINDER: As is normal with builds early in the development cycle, builds may contain bugs that might be painful for some. If this makes you uncomfortable, you may want to consider switching to the Slow ring. Slow ring builds will continue to be higher quality.
Microsoft has said the same for every fast-ring Insider's build released since the original release of 17763. Guess what's in the higher-quality slow ring...17763, of course.
So I've been as content as a bug in a rug in the slow lane these days. On 17763...! It makes sense to me to take the last official release and build on top of it towards the next official release, etc. That way you don't have to post stability warnings about the "early" builds in the next release cycle, presumably RS-6, in this case. I'm going to be staying in the slow ring for some time to come, I would imagine. Can't figure what Microsoft is trying to do here with an official release every six months--present a moving target to hackers? Maybe. At any rate, what's Microsoft going to do in five years when it has ~14 versions of Win10 to support? Someone @ Microsoft needs to think about this, imo.
I moved back to the slow ring in the Insider's group after four years of being in the fast ring--started Win10 Insiders Oct 1, 2014, first day of the program. I downloaded 17763, the Oct release, the first time it was offered, before it was ever pulled, and have been there ever since--with no problems to report. 100% stable. Now on build 17763.168 (after a couple of cumulative updates.) I'm getting sort of tired of Microsoft trying to reinvent the wheel every six months, however. For me, 17763 (original Official Oct Windows release) is rock stable and always has been--bug reports can have so many causes other than OS bugs, it's not funny, so I don't pay attention until I myself actually encounter a described "bug," and in the case of the Oct release, I never did encounter such bugs--no little ones, and certainly no show-stoppers.
To illustrate what I mean, here's what Microsoft itself says about it's latest fast-ring insider release, build 18298:
REMINDER: As is normal with builds early in the development cycle, builds may contain bugs that might be painful for some. If this makes you uncomfortable, you may want to consider switching to the Slow ring. Slow ring builds will continue to be higher quality.
Microsoft has said the same for every fast-ring Insider's build released since the original release of 17763. Guess what's in the higher-quality slow ring...17763, of course.
So I've been as content as a bug in a rug in the slow lane these days. On 17763...! It makes sense to me to take the last official release and build on top of it towards the next official release, etc. That way you don't have to post stability warnings about the "early" builds in the next release cycle, presumably RS-6, in this case. I'm going to be staying in the slow ring for some time to come, I would imagine. Can't figure what Microsoft is trying to do here with an official release every six months--present a moving target to hackers? Maybe. At any rate, what's Microsoft going to do in five years when it has ~14 versions of Win10 to support? Someone @ Microsoft needs to think about this, imo.
Fox2232
Senior Member
Posts: 8819
Joined: 2012-07-20
Senior Member
Posts: 8819
Joined: 2012-07-20
#5618681 Posted on: 12/18/2018 09:02 PM
I moved back to the slow ring in the Insider's group after four years of being in the fast ring--started Win10 Insiders Oct 1, 2014, first day of the program. I downloaded 17763, the Oct release, the first time it was offered, before it was ever pulled, and have been there ever since--with no problems to report. 100% stable. Now on build 17763.168 (after a couple of cumulative updates.) I'm getting sort of tired of Microsoft trying to reinvent the wheel every six months, however. For me, 17763 (original Official Oct Windows release) is rock stable and always has been--bug reports can have so many causes other than OS bugs, it's not funny, so I don't pay attention until I myself actually encounter a described "bug," and in the case of the Oct release, I never did encounter such bugs--no little ones, and certainly no show-stoppers.
To illustrate what I mean, here's what Microsoft itself says about it's latest fast-ring insider release, build 18298:
REMINDER: As is normal with builds early in the development cycle, builds may contain bugs that might be painful for some. If this makes you uncomfortable, you may want to consider switching to the Slow ring. Slow ring builds will continue to be higher quality.
Microsoft has said the same for every fast-ring Insider's build released since the original release of 17763. Guess what's in the higher-quality slow ring...17763, of course.
So I've been as content as a bug in a rug in the slow lane these days. On 17763...! It makes sense to me to take the last official release and build on top of it towards the next official release, etc. That way you don't have to post stability warnings about the "early" builds in the next release cycle, presumably RS-6, in this case. I'm going to be staying in the slow ring for some time to come, I would imagine. Can't figure what Microsoft is trying to do here with an official release every six months--present a moving target to hackers? Maybe. At any rate, what's Microsoft going to do in five years when it has ~14 versions of Win10 to support? Someone @ Microsoft needs to think about this, imo.
Its not like they have that many builds to support. Insiders are not getting any support whatsoever. Each Insider build has timebomb.
And each non-insider build is to be upgraded to newer one over time. That's if one wants to have all patches. Only exception is LTSB. And that itself is not really that good.
It's like support for Win XP in form of service pack. Who wants updates gets service pack.
I moved back to the slow ring in the Insider's group after four years of being in the fast ring--started Win10 Insiders Oct 1, 2014, first day of the program. I downloaded 17763, the Oct release, the first time it was offered, before it was ever pulled, and have been there ever since--with no problems to report. 100% stable. Now on build 17763.168 (after a couple of cumulative updates.) I'm getting sort of tired of Microsoft trying to reinvent the wheel every six months, however. For me, 17763 (original Official Oct Windows release) is rock stable and always has been--bug reports can have so many causes other than OS bugs, it's not funny, so I don't pay attention until I myself actually encounter a described "bug," and in the case of the Oct release, I never did encounter such bugs--no little ones, and certainly no show-stoppers.
To illustrate what I mean, here's what Microsoft itself says about it's latest fast-ring insider release, build 18298:
REMINDER: As is normal with builds early in the development cycle, builds may contain bugs that might be painful for some. If this makes you uncomfortable, you may want to consider switching to the Slow ring. Slow ring builds will continue to be higher quality.
Microsoft has said the same for every fast-ring Insider's build released since the original release of 17763. Guess what's in the higher-quality slow ring...17763, of course.
So I've been as content as a bug in a rug in the slow lane these days. On 17763...! It makes sense to me to take the last official release and build on top of it towards the next official release, etc. That way you don't have to post stability warnings about the "early" builds in the next release cycle, presumably RS-6, in this case. I'm going to be staying in the slow ring for some time to come, I would imagine. Can't figure what Microsoft is trying to do here with an official release every six months--present a moving target to hackers? Maybe. At any rate, what's Microsoft going to do in five years when it has ~14 versions of Win10 to support? Someone @ Microsoft needs to think about this, imo.
Its not like they have that many builds to support. Insiders are not getting any support whatsoever. Each Insider build has timebomb.
And each non-insider build is to be upgraded to newer one over time. That's if one wants to have all patches. Only exception is LTSB. And that itself is not really that good.
It's like support for Win XP in form of service pack. Who wants updates gets service pack.
schmidtbag
Senior Member
Posts: 3881
Joined: 2012-11-10
Senior Member
Posts: 3881
Joined: 2012-11-10
#5618684 Posted on: 12/18/2018 09:12 PM
Reminds me of this joke:
Why do programmers confuse Halloween with Christmas?
Because Oct 31 = Dec 25
October is spelled D e c e m b e r in Microsoft's headquarters.
Reminds me of this joke:
Why do programmers confuse Halloween with Christmas?
Because Oct 31 = Dec 25
TheDeeGee
Senior Member
Posts: 5876
Joined: 2010-08-28
Senior Member
Posts: 5876
Joined: 2010-08-28
#5618685 Posted on: 12/18/2018 09:16 PM
I will hold out untill October 2019.
I will hold out untill October 2019.
warezme
Senior Member
Posts: 175
Joined: 2007-05-26
Senior Member
Posts: 175
Joined: 2007-05-26
#5618692 Posted on: 12/18/2018 09:47 PM
In the world of Windows 10 users, knowing there is an update window and a button there to push to check updates is an "advanced user" INCREDIBLY sad as that is.
I really don't like them calling people who click that check for updates button to be advanced users. At least the OS is in better shape now anyway. They still need to fix shellexperiencehost being a pos though.
In the world of Windows 10 users, knowing there is an update window and a button there to push to check updates is an "advanced user" INCREDIBLY sad as that is.
Dimitrios1983
Senior Member
Posts: 201
Joined: 2018-03-01
Senior Member
Posts: 201
Joined: 2018-03-01
#5618706 Posted on: 12/18/2018 10:35 PM
Anyone notice a lot of updates for Windows 7 lately? Seems to be running a little slow versus my Windows 10 PC recently. Like a weird lag with the mouse.
Anyone notice a lot of updates for Windows 7 lately? Seems to be running a little slow versus my Windows 10 PC recently. Like a weird lag with the mouse.
RealNC
Senior Member
Posts: 2822
Joined: 2011-11-24
Senior Member
Posts: 2822
Joined: 2011-11-24
#5618740 Posted on: 12/19/2018 01:32 AM
Until next week when they'll pull it again.
Windows 10 October update now fully available
Until next week when they'll pull it again.
RavenMaster
Senior Member
Posts: 1006
Joined: 2009-08-19
Senior Member
Posts: 1006
Joined: 2009-08-19
#5618743 Posted on: 12/19/2018 01:37 AM
There's still a really frakking annoying bug present in 1809. When i start my PC in the morning, i get passed the motherboard post screen but just before the windows 10 login screen appears, my monitor comes up with the 'no signal.' The rig is running, all the lights are on, all the fans are on but the monitor becomes unresponsive. If i then go ahead and press the Reset button on my PC case, the computer boots up and gets the login screen and works no problem.
When i roll back to 1803, the problem is completely gone and the PC boots first time every time and always lets me login to my desktop.
There's still a really frakking annoying bug present in 1809. When i start my PC in the morning, i get passed the motherboard post screen but just before the windows 10 login screen appears, my monitor comes up with the 'no signal.' The rig is running, all the lights are on, all the fans are on but the monitor becomes unresponsive. If i then go ahead and press the Reset button on my PC case, the computer boots up and gets the login screen and works no problem.
When i roll back to 1803, the problem is completely gone and the PC boots first time every time and always lets me login to my desktop.
tsunami231
Senior Member
Posts: 9258
Joined: 2003-05-24
Senior Member
Posts: 9258
Joined: 2003-05-24
#5618744 Posted on: 12/19/2018 01:41 AM
to bad i still have this stuff defered for 180 days around june it should be pushed to me if I dont push derfer even farther
to bad i still have this stuff defered for 180 days around june it should be pushed to me if I dont push derfer even farther
nick0323
Senior Member
Posts: 925
Joined: 2010-02-24
Senior Member
Posts: 925
Joined: 2010-02-24
#5618749 Posted on: 12/19/2018 02:22 AM
There's still an upgrade block for several according to Microsoft's website... https://support.microsoft.com/en-gb/help/4464619
There's still an upgrade block for several according to Microsoft's website... https://support.microsoft.com/en-gb/help/4464619
Size_Mick
Senior Member
Posts: 285
Joined: 2002-03-22
Senior Member
Posts: 285
Joined: 2002-03-22
#5618764 Posted on: 12/19/2018 04:59 AM
Does anyone else have the File Explorer problem with Dark Mode, which is black text on a dark gray background, making it barely readable? None of the fixes I've found have worked for me. Does that make this a bug?
Does anyone else have the File Explorer problem with Dark Mode, which is black text on a dark gray background, making it barely readable? None of the fixes I've found have worked for me. Does that make this a bug?
Click here to post a comment for this news story on the message forum.
Senior Member
Posts: 11783
Joined: 2011-12-31
I really don't like them calling people who click that check for updates button to be advanced users. At least the OS is in better shape now anyway. They still need to fix shellexperiencehost being a pos though.