Current Status of Windows 10 October 2018 Update version 1809

  1. reddice's Avatar
    Posts : 615
    Windows 10 Pro x64
       #500

    I had this same issue after updating to the October update. I fixed it.
    1. Did a full Macrium image backup.
    2. Booted into Macrium recovery and only restored the FAT32, EFI System Partition and OS Partition. Make sure you restore them in that order.
    3. After booting into Windows used this tool Free Partition Manager Software Download Windows PC Server to delete the unalocated space.
      My Computer

  2. CountMike's Avatar
    Posts : 18,447
    W10+Developer Insider + Linux
       #501

    storageman said:
    @CountMike @IronZorg89 @Caledon Ken - Absolutely Correct. At the end is for provisioning. I can fix the 400mb at the front, but I wonder if anybody else has been seeing this ? It just seemed strange to me.
    This is my system with Samsung 960 (Disk 0) after a clean install of 1809 and updating to Skippy 18282, it has Samsung recommended over-provisioning partition.
    Disk2 has clean installed RP v1809 Build 17763.135 updated to 156 but is not a Samsung SSD but Kingston A400 which doesn't use special partition for over-provisioning.
    Current Status of Windows 10 October 2018 Update version 1809-image.png
    The rest are HDDs without any OS, just data.
      My Computers

  3. storageman's Avatar
    Posts : 1,020
    Windows 10 Pro 20H2 19042.572
       #502

    @CountMike I believe the issue is that the older 400mb recovery partition used for 1803 and earlier releases got bigger in 1809 (looking at yours its up to 499mb while mine is 431mb). ON my MBR which looks just like yours, the old recovery partition is still there, but a new one was carved out of the "C" drive partition.
    Attached Thumbnails Attached Thumbnails Current Status of Windows 10 October 2018 Update version 1809-desktop_partition_layout.jpg  
      My Computers

  4. f14tomcat's Avatar
    Posts : 53,621
    Multi-boot Windows 10 - RTM, RP, Beta, and Insider
       #503

    storageman said:
    @CountMike I believe the issue is that the older 400mb recovery partition used for 1803 and earlier releases got bigger in 1809 (looking at yours its up to 499mb while mine is 431mb). ON my MBR which looks just like yours, the old recovery partition is still there, but a new one was carved out of the "C" drive partition.
    I have exactly the same. Last time I clean installed 1803, it created Recovery up front partition #1, on update snagged a chunk from C. 2 solutions I know of: 1-clean install with total wipe of all partitions during the process. 2-fancy footwork with MiniTool or similar. (3 options if you just want to ignore it. )
      My Computers

  5. CountMike's Avatar
    Posts : 18,447
    W10+Developer Insider + Linux
       #504

    Yes, for some reason they started placing restore partition at the beginning of disk and it can't be merged with C: being in front of it.
      My Computers

  6. Kari's Avatar
    Posts : 17,438
    Windows 10 Pro
       #505

    CountMike said:
    Yes, for some reason they started placing restore partition at the beginning of disk and it can't be merged with C: being in front of it.
    That's why I prefer manually partitioning Windows system disk: DISKPART - How to Partition GPT disk | Tutorials

    When done, deploy Windows instead of traditional install: Apply Windows Image using DISM Instead of Clean Install | Tutorials

    Kari
      My Computer

  7. Stitch194's Avatar
    Posts : 430
    Windows 10 Pro
       #506

    CountMike said:
    Yes, for some reason they started placing restore partition at the beginning of disk and it can't be merged with C: being in front of it.
    Mike Is the problem with the recent ISO?
    I just performed a clean install from the ISO that was released prior to MS pulling the release of 1809.
    I installed 1809.1 then installed the .134 CU I had on USB. No changes in disk layout C is partition 1, Data 2 OEM reserved 3&4
      My Computer

  8. CountMike's Avatar
    Posts : 18,447
    W10+Developer Insider + Linux
       #507

    Stitch194 said:
    Mike Is the problem with the recent ISO?
    I just performed a clean install from the ISO that was released prior to MS pulling the release of 1809.
    I installed 1809.1 then installed the .134 CU I had on USB. No changes in disk layout C is partition 1, Data 2 OEM reserved 3&4
    You could kill those to partition after C: and merge them with C: if you want to, the first Restore partition is most probably made last. Just one question. is Windows installed with BIOS in legacy mode instead of UEFI mode ? I don't see EFI partition on that disk.
    See this 100MB EFI System partition:
    Current Status of Windows 10 October 2018 Update version 1809-image.png
      My Computers

  9. Stitch194's Avatar
    Posts : 430
    Windows 10 Pro
       #508

    Thanks Mike it was legacy mode. 10 year old Dell. LOL
      My Computer

  10. hello10's Avatar
    Posts : 204
    Windows 10 Home x64
       #509

    Latest cumulative updates for Windows 10 version 1809 break Windows Media Player (also causing issues with some first-party system apps).
      My Computer


 

  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 13:07.
Find Us




Windows 10 Forums