Windows 10 October 2018 Update Inches Closer to Re-Release

Posted on October 16, 2018 by Mehedi Hassan in Windows, Windows 10 with 38 Comments

Microsoft’s Windows 10 October 2018 Update had a very rough start. It all started when Microsoft released the update to the public, soon following multiple reports of a data deletion issue affecting some users. The company later pulled the update, proceeding to provide an explanation to users as the company continued to work to fix the issue.

Although Microsoft has supposedly fixed the data deletion issue in a recent Insider release of the Windows 10 October 2018 Update, the company today released another build for Insiders in the Slow and Release Preview rings with some additional fixes. The company today delivered KB4464455, which brought the OS build number up to 17763.104.

  • We have fixed the issue where the incorrect details were being shown in Task Manager under the “Processes” tab.
  • We fixed an issue where in certain cases IME would not work in the first process of a Microsoft Edge user session.
  • We fixed an issue where in some cases applications would become unresponsive after resuming from Connected Standby.
  • We fixed several issues causing application compatibility problems with 3rd-party antivirus and virtualization products.
  • We fixed several issues with driver compatibility.

It’s not clear when exactly Microsoft plans on releasing the update to the public once again. For now, it’s clear Microsoft is busy fixing some of the other early, albeit minor, issues in the update as it gets ready for a re-release to the public. The rollout will likely be a lot more cautious this time around, though.

Tagged with , ,

Join the discussion!

BECOME A THURROTT MEMBER:

Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Register
Comments (41)

41 responses to “Windows 10 October 2018 Update Inches Closer to Re-Release”

  1. MikeCerm

    Did Microsoft change the way OneDrive works in 1809? On every PC I've installed it on, anytime I make changes to a file it just perpetually says "sync status: pending." I've tried resetting and reinstalling OneDrive, but nothing helped, and it's on multiple systems.

  2. Tony Barrett

    Windows 10 is now a running joke with many. The updates are a joke, and now becoming such a high risk issue, people are actually deferring or delaying them indefinitely. Once you have Win10 running stable, it's best not to let MS ruin it with one of their 'upgrades' that are actually nothing of the sort. If only MS could have had a time machine back in 2014/15 when they were planning all this - I think a lot of things would have been done differently.

    • RM

      In reply to ghostrider:I have not had a problem with an upgrade since Windows Vista (now that was bad). However, all of the fixes Microsoft just sent out to the insiders, should have been fixed already. They do have a quality issue, hopefully they get it figured out soon!.


    • Stooks

      In reply to ghostrider:

      Joke?


      So my company hs been on it since August of 2016? At Home we (family of 5) have been on it by December of 2016. 3 kids have been using it on school laptops sine 2016 as well.


      None of of us has had any issues. On top of that we all use Office 365/One Drive as well.

      • Adolf von Württemberg

        In reply to Stooks: Ditto here. We've seen no problems with 1809 on our home computers.


      • ragingthunder

        In reply to Stooks:

        Then you're in the relative minority. I don't have 10 kids to compare stability of Windows across various machines, but on my main workstation, Windows updates are definitely becoming a risky gamble. If you think your files being deleted from Documents is not an issue, you are delusional my friend!

        • Stooks

          In reply to ragingthunder:

          "If you think your files being deleted from Documents is not an issue, you are delusional my friend!"


          Lol you are delusional. Seriously this happened to 1/100th of people that had to go find the update. Then they had to have moved the default folders and have no backup. So bascially nobody. If this happened to "you" and you really lost files, you are special kind of dumb for not having a backup and installing a major update the first day it came out.


          Does Microsoft need to have a better process around bug reporting...sure. However not pushing it out on day one was good on them because thanks to these special users they got alerted to a problem that did not impact 99.99% of users.


          My 3 kids, each at different schools are 3 among thousands that use these school provided laptops running Windows 10....for 2 years now.

      • Winner

        In reply to Stooks:

        I love all of these "I and my friends have had no problems" posts. As if that means there are no problems for the entire user population.

  3. gerardt

    I successfully installed update upon release. Have not had a hiccup since. I suppose installing revised update upon release wise?

  4. waethorn

    Who needs 1809 when the October Cumulative Update for 1803 from late last week just borked about two dozen HP business desktops at 3 separate clients of mine with a Startup Repair reboot loop. As per the prescribed "solutions", NO, turning off recovery via BCDedit didn't fix it, System Restore didn't fix it (Microsoft says not to bother using it anymore anyway, but that's another issue altogether), the RegBackup folder had 0-byte hive backups (which says to me there is no automated RegBackup in Windows 10), and you couldn't get out of the startup repair loop to get into any Safe Mode option. The only repair option that worked (aside from flattening each install and redoing it from scratch, which I wasn't prepared to do) was PC Reset, which meant having to reinstall all desktop apps....try doing that on 2 dozen PC's without an in-house deployment server, because "SMB's should be using cloud computing cuz servers are too much work and too expensive" as per the advice on this website.


    The next business desktop deployment I'm doing, I'm using Enterprise LTSB 2016. 1607 never had these problems. And they respected International-English (English-UK-based) off-shoot languages by not including UK-English keyboards automatically, unlike the reversion since 1803.


    And just FYI: new updates to the Windows Store are just plain retarded. Microsoft uses the 2-digit ISO country code for language instead of the correct xx-yy code, so what should be "Devices" for English-Canada (en-ca) ends up being "Dispositius", which is Catalan (ca).


    After they got rid of practically the entire lot of internal QA testers before Windows 10's launch, did they now fire the team responsible for regionalization? And yes, Microsoft, in Canada, we spell words like "regionalization" with a Z like the US, but we call it 'zed', like the UK, whereas the UK spells those words with an S. The Canadian government even has examples of this on their own website. Clue in!

    • EZAB

      In reply to Waethorn:

      Yes, it hit me to with that stupid Keyboard HP driver update on an HP ProDesk 400, (Skylake). BSOD. WDF Violation. Nothing worked to bring it back including System Restore. System Restore Error (0x80070003). I pulled the SSD drive and installed in another PC as a second drive, the PC wouldn't even recognize it! Luckily I had everything backed up anticipating 1809. Did a clean reinstall of 1803 I had burned to a disk. This was as bad as I've seen.

      • waethorn

        In reply to EZAB:

        Some of the ones I was doing were ProDesk 400's. Some 600's. Some EliteDesk units too. Various ages of Intel-based units from 4th-8th gen CPU's.


        Your SSD is fine. This doesn't affect the hardware in such a way unless you already had some fault with it. PC Reset should work but you'll have to reinstall your Win32 applications, and possibly some drivers, but I usually use HP Support Assistant on these machines to make the drivers come from HP, not Windows Update. Windows Updates should be more or less already installed too.

  5. ramansinh

    Perhaps MS. should just skip release of 1809 and work on bugs and release actual 1809 in 2019 and call it 1909. One year of bug fixing, making it more stable and polishing user interface, no new features at all!


  6. ramansinh

    The damage to their reputation is in the past, nothing can be done about it now. Why not hold off the "fix" release for awhile and take the time to test it more thoroughly?

  7. madthinus

    Would be nice if they pushed that update to all, not just slow and release preview.

  8. NT6.1

    This is pathetic. Stop with these useless updates!!! Scrap Windows 10 and start over with Windows 7. No one is checking for UWP anyway...

  9. martinusv2

    Glad I waited. We will start like we did in the Service Pack era. Waiting some time before upgrading.

  10. mclark2112

    I installed the update on my Surface Pro LTE the day it was available, didn't lose anything. But the system was so unsable I uninstalled it a week later. Multiple reboots required to get through a day. Fool me once...

  11. skane2600

    The damage to their reputation is in the past, nothing can be done about it now. Why not hold off the "fix" release for awhile and take the time to test it more thoroughly? The consequences of another bad release are an order of magnitude more significant than the value of what the release would add to Windows.

  12. glenn8878

    We fixed the issue where Windows 10 works the way you want it to.

  13. lalit12

    We fixed the issue where Windows 10 works the way you want it to.

  14. lalit12

    Did Microsoft change the way OneDrive works in 1809? On every PC I've installed it on, anytime I make changes to a file it just perpetually says "sync status: pending." I've tried resetting and reinstalling OneDrive, but nothing helped, and it's on multiple systems.

    <a href="www.wifinames.xyz/">Funny WiFi Nammes</a>

  15. lalit12

    <a href="www.wifinames.xyz/">Funny WiFi Nammes</a>

  16. lalit12

    <a href="www.wifinames.xyz/">The damage to their reputation is in the past, nothing can be done about it now. Why not hold off the "fix" release for awhile and take the time to test it more thoroughly? The consequences of another bad release are an order of magnitude more significant than the value of what the release would add to Windows.</a>

    • Stooks

      In reply to lalit12:

      Outside of the tech blog/followers world NO ONE has any idea about any of these updates. No one got it unless they sought it out and installed it.


      I did seek it out it out and have been running it without issue.

  17. nik9000

    Still no fix for the massive problem of crackling, hissing and clicking noises experienced by literally thousands of users after 1709.

    My new studio PC build is useless for audio until a patch is released.


    Win 7 was near perfect - why Microsoft?!!


    I have identified that it's not a sound driver problem as everyone seems to think. HD audio is turned off in the BIOS, and the onboard Realtek drivers are not even loaded, and it's still making the noises through an exterior USB interface.

    I'm thinking it's a graphics driver issue, as just accessing menus causes the noises to increase.


    MS programmers are more concerned about making sure you can't get rid of Candy Crush than fixing real issues.

    • PanamaVet

      In reply to nik9000:

      I love listening to music using Windows 10. It always works without skipping a beat and I have it set to ultra high def. I think my experience has to do with not click-clicking on everything in sight...

      • nik9000

        In reply to PanamaVet:

        Well, don't accuse me of being one of those morons (who deserve everything they get) I know exactly what I'm doing.


        It's great that you don't have this problem like thousands of others do, so how about helping us fix it? MS have no clue what is causing this, and it's been going on for years, this is not a trivial issue. None of the 'fixes' currently work (my research is ongoing).


        I just installed Win10Pro like everyone else does and it did this straight away and won't stop doing it (like thousands of other users have experienced).


        Not a helpful comment.



    • locust infested orchard inc

      Quote by nik9000, "I'm thinking it's a graphics driver issue, as just accessing menus causes the noises to increase."

      Believe it or not, but I experienced the exactly same bizarre problem as you face.


      I still have a 15 year old PC lying about with an installation of WinXP SP1. About two years ago the nVIDIA graphics card burnt out due to the failure of the GFX fan not spinning, so I replaced it with a dirt-cheap $20 no-frills nVIDIA card from a local electronics store who were clearing obsolete stock.


      Upon slotting this $20 GFX card, the exact same problems you describe were glaring at me. In addition, simply moving the mouse cursor caused noises to emanate (but not from the Creative-Blaster sound card).


      Moving the mouse swiftly and randomly caused the noises to increase in beats per minute.


      Clearly it was a problem with the GFX card as it was the only item changed.


      I eventually returned the dodgy no-frills GFX card (that was a challenge in itself) and replaced it with a second-hand one from eBay. Problem resolved.


      I suspect it's not an OS problem, but rather a problem with the drivers (as you elude to) and the GFX card in question.


      I believe it might be worthwhile swapping out your existing GFX card with another brand to see if it resolves the ongoing issues of hissing and clicking.


      It that doesn't resolve matters, if your current GFX card is an nVIDIA one, swap it with a Radeon one (or vice versa as the case may be), in an attempt to rid these unspecified gremlins from your PC.


      I wish you good luck, because the hisses and clicks must be driving you absolutely insane.


      Keep us updated with your trials and tribulations as it would be fascinating to see how this ongoing battle can be won.

      • nik9000

        In reply to locust infested orchard inc:

        Thanks for the input.

        This makes my new build unusable at the moment, and MS don't seem to be doing anything about it. A Google search on this issue turns up thousands of hits, so I'm not the only one.


        I don't have a graphics card as I don't do games and the onboard has outputs for the two screens I need anyway, so will try loading different drivers to see if it goes away.


        People are sure it's a sound issue because they hear it in their speakers, but as I said, I'm sure it's graphics drivers interfering with the sound. Amazingly, some users have solved this by disabling their LAN drivers, so will try going through the endless list of 'fixes' doing the rounds.


        If you hear anything about this please post the info. Thanks

  18. hackerman

    Thank a lot for sharing this awesome Windows 10 Update. It's really wonderful .

Leave a Reply