Windows OS Hub
  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange

 Windows OS Hub / Windows 10 / Windows 10 1803 Update Creates an Additional OEM Partition

May 10, 2018 Windows 10

Windows 10 1803 Update Creates an Additional OEM Partition

Users have noticed that when upgrading to Windows 10 1803 (April 2018 Update), a separate additional OEM (recovery) partition appears on the local drive. This partition is assigned a separate drive letter, it is displayed in File Explorer and in the Disk Manager snap-in. The size of the additional OEM partition with the NTFS is about 450 – 500 MB. However, there is not enough free space on this volume, less than 9%. As a result, Windows 10 starts constantly displaying notifications that this disk is almost full.

I’ll try to explain briefly for which this partition is used, and whether you can delete it or just remove annoying notifications.

Windows 10 v1803 creates an extra Disk Partition

On the new OEM partition, only the Recovery and System Volume Information folders are present.

If you run the command reagent /info, you can verify that the new OEM partition is used to store boot image of the Windows Recovery Environment (WinRE). Why the developers of Windows 10 decided to move the image of the partition to a separate disk is not clear.

reagent /info

If you want to save the ability to restore the system using WinRe, you do not have to delete this partition (using the article How to remove the OEM partition in Windows). However, it’s completely safe to just remove the drive letter from this partition. On WinRE this will not affect, because as the path to the image of Winre.wim is used the address in the format \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE (as you can see, the path does not contain the drive letter).

You can hide an extra OEM partition this ways:

  1. You can delete the drive letter assigned to it via Disk Manager (diskmgmt.msc). Right click on the OEM partition -> Change drive letter and paths -> Remove. In this case, the volume will simply stop displaying in the File Explorer, but it will not be deleted from the HDD. You can’t remove this additional partition from the Disk Manager console (the delete button is inactive). can't delete oem extra partition
  2. It is even easier to remove the mount point of the disk using the following command that is run on the command prompt with administrator privileges: mountvol E: /D
  3. You can also remove the drive letter on this partition with the diskpart command, but this is a little more complicated. To delete a drive letter, you need to use the following commands:
    diskpart
    list volume
    select volume <volume_number>
    remove letter=<drive_letter>
    exit

That’s all, you hide the new OEM partition from the user, and there are no more notifications about the end of disk space.

2 comments
3
Facebook Twitter Google + Pinterest
previous post
Error 0x0000007e: Windows cannot connect to network printer, Operation failed
next post
Sending Emails from Excel using VBA Macro and Outlook

Related Reading

How to Sign a PowerShell Script (PS1) with...

February 25, 2021

How to Shadow (Remote Control) a User’s RDP...

February 22, 2021

Configuring PowerShell Script Execution Policy

February 18, 2021

Configuring Proxy Settings on Windows Using Group Policy...

February 17, 2021

Updating Group Policy Settings on Windows Domain Computers

February 16, 2021

2 comments

Klaus May 16, 2018 - 4:44 pm

Awesome, those notifications were really annoying. Thanks 🙂

Reply
Irfan September 12, 2018 - 5:21 pm

Thanks for the solution, solved my problem. It was really annoying constantly getting those notifications..

Reply

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange
  • Windows 10
  • Windows 8
  • Windows 7
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2008 R2
  • PowerShell
  • VMWare
  • MS Office

Recent Posts

  • Accessing USB Flash Drive from VMWare ESXi

    February 26, 2021
  • How to Sign a PowerShell Script (PS1) with a Code Signing Certificate?

    February 25, 2021
  • Change the Default Port Number (TCP/1433) for a MS SQL Server Instance

    February 24, 2021
  • How to Shadow (Remote Control) a User’s RDP session on RDS Windows Server 2016/2019?

    February 22, 2021
  • Configuring PowerShell Script Execution Policy

    February 18, 2021
  • Configuring Proxy Settings on Windows Using Group Policy Preferences

    February 17, 2021
  • Updating Group Policy Settings on Windows Domain Computers

    February 16, 2021
  • Managing Administrative Shares (Admin$, IPC$, C$, D$) in Windows 10

    February 11, 2021
  • Packet Monitor (PktMon) – Built-in Packet Sniffer in Windows 10

    February 10, 2021
  • Fixing “Winload.efi is Missing or Contains Errors” in Windows 10

    February 5, 2021

Follow us

woshub.com
  • Facebook
  • Twitter
  • RSS
Popular Posts
  • Booting Windows 7 / 10 from GPT Disk on BIOS (non-UEFI) systems
  • How to Run Program without Admin Privileges and to Bypass UAC Prompt?
  • Removable USB Flash Drive as Local HDD in Windows 10 / 7
  • How to Create a Wi-Fi Hotspot on your Windows 10 PC
  • How to increase KMS current count (count is insufficient)
  • Error Code: 0x80070035 “The Network Path was not found” after Windows 10 Update
  • How to Configure Google Chrome Using Group Policy ADMX Templates?
Footer Logo

@2014 - 2018 - Windows OS Hub. All about operating systems for sysadmins


Back To Top