Windows 10 October 2018 Update rollout now paused
-
Been on 1809 since day one and have had no issues. One computer has user folders on second drive.
Neither have I. Why MS will not release it is a mystery.
-
Neither have I. Why MS will not release it is a mystery.
Of course, I have always used 7zip so I did not see or test that issue, and I know how to move user folders so there are not leftovers in 2 places. And my only 3rd party protection is Malwarebytes.
-
The CU to bring 1809 up to scratch is already in the Release Preview and Slow Rings so that will be released to those of us on 1809. Whether they will release a new iso or re-release the old one with the CU is less certain. I think they have already patched 1803 so that the data loss won't happen again.
Thanks @kado897
I'm quite looking forward to seeing how all this pans out, both in the short term and in the long term.
-
-
Updated version of Windows 10 October 2018 Update released to Windows Insiders
NOT to The General Public. They still cannot get it. It was released under 17763.1 then it was pulled and re released with a CU making it 17765.55 then it was given another CU making it 17763.104, then another CU making it 17763.107 , the last two only available to members of The Insider Group.
Updated version = 17763.1 -> .17 here. If memory serves me well, they released FU .17 for RP (for upgrades from 1803) and CU .55 for public at the same time (Oct patch tuesday)..
Last edited by sunberg; 03 Nov 2018 at 13:45.
-
Updated version = 17763.1 -> .17 here. If memory serves me well, they released FU .17 for RP (for upgrades from 1803) and CU .55 for public at the same time (Oct patch tuesday)..
The current release is 17763.107 in The IP which I am using! 17763.1 is not greater than 17763.107. Once again this build is currently not available for the GP by using the WCT. One would have to joint the IP. If a not member used the WCT today it would fail. Build 1809 is not available by use of The WU or The WCT for anyone not in The IP. If you currently are on 17763.55 and try to use the WCT it will fail as well. I am aware that MS has made many confused over this build but if you want the latest release of it you have to be in The Slow or Release Preview Ring of The Insider Program. I cannot make it any clearer that that.
-
-
I'm thinking the re-release will come next Tuesday unless it hasn't been fixed yet. If they haven't done it by then, it probably means either the flaw(s) are catastrophic or MS has fired or transferred all the Windows people who know how to do anything. 
-
I'm thinking the re-release will come next Tuesday unless it hasn't been fixed yet. If they haven't done it by then, it probably means either the flaw(s) are catastrophic or MS has fired or transferred all the Windows people who know how to do anything.
I hope so but I have read that they found Registry problems but I believe that is fud.
-
Had it been Registry errors wouldn't we all have had problems. I believe the issue was users losing all of their data, and MS are now gun shy. Josey are you ready "The "Showdown at MS Corral" will be here sooner than later, I hope it's the latter.
-
I hope so but I have read that they found Registry problems but I believe that is fud.
Or it's similar to what we called it on an aircraft carrier's flight deck, FOD. Foreign Object Damage
-
Had it been Registry errors wouldn't we all have had problems. I believe the issue was users losing all of their data, and MS are now gun shy. Josey are you ready "The "Showdown at MS Corral" will be here sooner than later, I hope it's the latter.
I said it was probably FUD. They are claiming that there are two entries in Windows System32 that contain registry data but only one has Data.--FUD. The system would not boot I would think if true. They also were claiming that this existed in 1803 which makes it more FUDDY. If I do not read it here or from MS, I do not pay it much attention.
