Disputed every inch--space for the recovery drive cache encroachment

The cause of the matter is simple. I am using the tablet Lenovo Helix last year Sea Amoy, because the discount is good, the configuration is not high. SSD is only 128GB.

After Windows 10 Push Installation, the SSD remaining space is smaller than a day, even if I often clean up the disk, still always hovering around 20GB. Suddenly one day, space only left 15GB, who suddenly stole my disk space?

In my experience, the space is in all likelihood to be occupied by Windows. So in the Windows directory for a meal, sure enough to find a directory is much larger than before, this directory is:

C:\Windows\System32\DriverStore

A driver's directory, by what use my 10GB space ... Be resolute in trying to solve the problem.

Take a closer look at the size of each directory, and find a bunch of HDX-led drive folders that are large. Open look, inside incredibly are Realtek audio driver. Ranging from 100mb+ to 200+MB, these drive folders account for nearly 8GB of space. It appears that each INF file has a large number of drive files saved in one copy.

It is necessary to delete it, but ... Not to be deleted ...

Driverstore is a library of drivers managed by Windows systems and is not recommended to be manually deleted by itself. Open the properties of the folder, as you can see on the Security page, that the owner of these files is system, so the user cannot delete the folders even if they are administrator permissions.

However, I am (NO) Gao (Zuo) person (NO) gall (Died) Big (why) die (You) knock (Try) Ah. Rob the owner (ownership), change the permissions, and then delete. Here's the question, dozens of folders, is this what I'm doing this weekend?

Of course not, I want to elevate the permissions to system.

In the Windows XP era, elevated system permissions can be done by task because the task runs under System permissions and it is easy to use it to get a process running as a system identity. Later Windows modified the vulnerability. The only possible way is psexec.

PsExec is a tool in the Systeminternals toolset. Use it to run processes in a specific identity. So, I run:

650) this.width=650; "title=" N01 "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" N01 "src=" http://s3.51cto.com/wyfs02/M01/74/97/ Wkiom1yiasmd0qjpaacom5anstc224.jpg "width=" 578 "height=" 153 "/>

Open a command-line window that runs under System permissions and start the deletion.

650) this.width=650; "title=" N02 "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" N02 "src=" http://s3.51cto.com/wyfs02/M02/74/97/ Wkiom1yiasudbiakaaimeh0zy3k196.jpg "width=" 578 "height=" 387 "/>

Soon I'm tired of it, and it's not much faster than changing the owner and permissions in the UI interface. Besides, delete the folder directly, the heart is still a bit empty ...

I have to find a way. Microsoft Official has the countermeasure:

Remove a Driver package from the Driver Store

Https://technet.microsoft.com/en-us/library/cc730875.aspx

In fact, there is a program I am not unfamiliar, used it in the system Center Configuration Manager OSD When installing the driver, this program is PnPUtil

This program can also export all the existing non-Microsoft operating system drivers, namely the OEM-driven checklist, in addition to installing the driver from the INF file at the command line:

Pnputil.exe–e > X:\oemdrv.txt

Open this text file and find my Realtek drive to invade my disk space:

650) this.width=650; "title=" Y02 "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" Y02 "src=" http://s3.51cto.com/wyfs02/M00/74/97/ Wkiom1yias3zo3craakmwmulob0912.jpg "width=" 587 "height=" 472 "/>

Locate the Oem#.inf after the publication name, remembering the file name, such as Oem101.inf.

Go back to the command line and use PnPUtil to safely delete this drive folder.

650) this.width=650; "title=" Y01 "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" Y01 "src=" http://s3.51cto.com/wyfs02/M01/74/97/wKiom1YiaS7CzgZHAAE2m-mkc_ G329.jpg "width=" 589 "height=" 386 "/>

This repulsed the drive folder that was occupying the disk.

The story is not over yet, to be continued ...

Disputed every inch--space for the recovery drive cache encroachment