Cumulative Update KB4100403 Windows 10 v1803 Build 17134.81 - May 23

Page 11 of 15 FirstFirst ... 910111213 ... LastLast

  1. Posts : 124
    Windows 10
       #100

    Mooly said:
    I would reboot and run disk clean again. Be sure to click the clean up system files option. Its always difficult to say what is going on without being in front of it.
    I'm wary of using disc cleanup, because the last time I did, besides apparently wiping away all my cookies (which is fine), I ended up losing my Chrome session and all the tabs in the OneTab extension for Chrome.
      My Computer


  2. Posts : 1,871
    W10 pro x64 20H2 Build 19042.610
       #101

    I can't say how Windows interacts with Chrome as I use only Edge browser, but cookies should be stored within the browser normally and so not subject to deletion by a disk clean.

    As to disk cleanup, well I run it a couple of times a week on average and never have any issues.

    You can still run the cleanup and see what it offers to be cleaned. You've no need to accept, just click cancel when it asks 'are you sure you want to delete...'
      My Computer


  3. Posts : 88
    Windows 10 Pro x64 (Insider Beta)
       #102

    I just saw in my Reliability History and Windows Update History that apparently I got "Feature update to Windows 10, version 1803" successfully installed earlier today. This laptop had 1803 clean installed on release day and I installed the 17134.81 CU last Tuesday when it came out. Has anyone else gotten this?
      My Computers


  4. Posts : 122
    Windows 10
       #103

    MattMcD488 said:
    I haven't noticed this on my laptop, but I clean installed 1803 on release day. I did notice when I entered Insider Release Preview for 1803 before I decided to clean install that I would get the "Updating Windows" screen for at least 2 reboot cycles after each update. Does yours do that as well if you click one of those? Did you clean install 1803 or update from 1709? Do you have the failed update bug in Settings? Maybe it's related to that.
    I didn't clean install - I updated from version 1709. Not aware of the failed update bug in settings. Maybe I'll search for that here to see what it is.

    Thanks.
      My Computer


  5. Posts : 124
    Windows 10
       #104

    The situation right now is that I've deleted all the temp files using CCleaner and Windows is currently installing the 1803 update while the System menu shows me that I'm running Win10 version 1803.

    You tell me.
      My Computer


  6. Posts : 56,824
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #105

    Alfred001 said:
    The situation right now is that I've deleted all the temp files using CCleaner and Windows is currently installing the 1803 update while the System menu shows me that I'm running Win10 version 1803.

    You tell me.
    I believe you, but what does WINVER show? Hold Win Key, and type "R", then WINVER,
    and enter.....
      My Computers


  7. Posts : 210
    Windows 10 Pro
       #106

    Apparently, Windows has a will of its own. I installed this CU, but in one of my laptops, Windows Update keeps me asking to reboot over and over again. I checked winver and the build is 17134.81, and Update History confirms the KB4100403 was installed successfully. However, for some reason, Windows forgets that I have just installed the update. I uninstalled this CU through Features and Programs on Control Panel, reinstalled it and rebooted, but the issue persists. Does anyone know how to solve this? Thanks in advance.
      My Computer


  8. Posts : 1,560
    Windows 10 Home 20H2 64-bit
       #107

    ksio89 said:
    Apparently, Windows has a will of its own. I installed this CU, but in one of my laptops, Windows Update keeps me asking to reboot over and over again. I checked winver and the build is 17134.81, and Update History confirms the KB4100403 was installed successfully. However, for some reason, Windows forgets that I have just installed the update. I uninstalled this CU through Features and Programs on Control Panel, reinstalled it and rebooted, but the issue persists. Does anyone know how to solve this? Thanks in advance.
    It is a known issue since this April feature update. You just need to wait until you get a blue prompt on screen that tells you to restart -- should appear in the non-active hours -- and it should be succesfully installed if you click restart now. If not you may need to do some registry trickery. It's a really annoying bug for sure, and I hope Microsoft can fix it in the June update.
      My Computer


  9. Posts : 210
    Windows 10 Pro
       #108

    Faith said:
    It is a known issue since this April feature update. You just need to wait until you get a blue prompt on screen that tells you to restart -- should appear in the non-active hours -- and it should be succesfully installed if you click restart now. If not you may need to do some registry trickery. It's a really annoying bug for sure, and I hope Microsoft can fix it in the June update.
    I found the solution for my isuse: I had to delete the contents from C:\Windows\SoftwareDistribution folder. As some files were in use, I opened an elevated command prompt and typed net stop wuauserv and then net stop bits. Stopping both services allowed me to delete all the files and folders that were in use. After the deletion, I restarted both services with net start wuauserv and net start bits and then rebooted Windows, and Windows Update no longer asks me for restarting. If anyone else is having this issue, it's worth a short following these steps.
      My Computer


  10. Posts : 384
    Windows 10-Pro 64bit
       #109

    This version just crashed my OS.
    Monitor went blank, few minutes later computer restarted on it's own.
    Considering reverting to 1709 from an old Macrium Reflect image dated 4/27/18
    This build is becoming too much trouble to deal with.
    ==================================================
    Dump File : 053018-13578-01.dmp
    Crash Time : 5/30/2018 10:42:45 AM
    Bug Check String :
    Bug Check Code : 0x00000133
    Parameter 1 : 00000000`00000001
    Parameter 2 : 00000000`00001e00
    Parameter 3 : fffff802`256fa378
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+197680
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 10.0.17134.81 (WinBuild.160101.0800)
    Processor : x64
    Crash Address : ntoskrnl.exe+197680
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\WINDOWS\Minidump\053018-13578-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 17134
    Dump File Size : 705,726
    Dump File Time : 5/30/2018 10:43:19 AM
    ==================================================
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 14:14.
Find Us




Windows 10 Forums