Note on archived topics.

This topic has been archived. Information and links in this thread may no longer be available or relevant.
If you have a question create a new topic by clicking here and select the appropriate board.
camelotshadow Tutor
Tutor
16 12 0 1
Message 1 of 4
725
Flag Post
HP Recommended

How to Delete Empty Recovery Partition HP System Recovery Error

Zbook 15 G2
Microsoft Windows 10 (64-bit)

I am trying to set up my Zbook 15 G2

It is a refurbished model with set up warranty til 8/23/16.

I just got it & it was upgraded to win 10 (1511).

There was no recovery partition on the hardrive.

 

I upgraded to the win 10 aniversary edition (1607) & have been updating software/drivers as per HP support suggestions.

 

It was recommended to create a system recovery thru a HP support message which I attempted to do but there was an error & it failed which led to a empty recovery partition being made on the harddrive.

 

Here is the summary & details..I am trying to delete this empty recovery partition but right clicking in disk management is not giving me anything. Can someone please advise a solution...

 

Tried to create System Recovery as suggested by HP support (Launch recovery media creation tool) & it attempted to make a recovery disc & partitioned the hard drive.The recovery failed (error 1AstorA.sys System Thread Exception not handled) & a empty recovery partition was made. I am trying to delete this partition & gain back the 784 MB space.

 

This entry was made in OS (C)/Windows/System32/Recovery/$PBR_Diskpart 

$PBR_Diskpart Notepad same day

 

rem == ResetPartitions-BIOS.txt ==convert mbr
rem == 1. System partition =========================
create partition primary size=100
format quick fs=ntfs label="System"
assign letter="S"
active
rem == 2. Windows partition ========================
rem == a. Create the Windows partition ==========
create partition primary
rem == b. Create space for the recovery tools partition ===
shrink minimum=464
rem == c. Prepare the Windows partition =========
format quick fs=ntfs label="Windows"
assign letter="W"
rem == 3. Windows RE tools partition ===============
create partition primary
format quick fs=ntfs label="Windows RE tools"
assign letter="T"
set id=0x27
list volume
exit

 

 

Thank You in advance for your help!

 

I checked file explorer & the partition does not show (It's an unnamed partition with no letter assigned) so I am not sure if the laptop came with this empty partition & I never noticed it.I 'm not sure if I checked disk management before but I thought I had. Its been a bit hectic & confusing as I updated 2 computers so the various details are sort of merging.

 

Anyway even if the created recovery error did not make the partition (I can't find a date t was made)

I still would like to remove it as its empty. I have a 1 GB HDD but still I don;t like a almost 1GB partition just doing nothing.

 

Any advise is appreciated...

 

Update

This thread in MS addresses it. IT's a hidden unnamed recovery partition so it may hae been just made from the create recovery error or it was always there & I never noticed it.

 

https://social.technet.microsoft.com/Forums/en-US/4f1b84ac-b193-40e3-943a-f45d52e23685/cant-delete-e...

 

There is a way to assign a letter to the drive & unhide it described in bottom of the previous thread

so disk manage can delete it... 

 

Still would like to remove it if its not needed. It is empty...but there have been some who have reported after removal that the system did not function so I am trying to be careful.

 

I thought maybe the error created this partition but maybe it was always there & I am obsessing for nothing. Just trying to keep my system clean.

 

Thanks for taking the time to help me address this concern.

 

Diskpart lists this:

 

Partition 1 Primary 930 GB offset 1024 KB
Partition 2 Recovery 784 MB Offset 930 GB

 

Not sure what the offset means.

 

There is alot of disussion on all the recovery partitions created on this forum with some frees tools to check whats in the partitions & to reallocate or remove them. I might have to download some software but I'd rather keep my laptop as simple as possible.

 

http://www.tenforums.com/installation-setup/38422-old-recovery-partition.html

 

This has turned into a all nighter from since 6pm.

 

Hope someone can help me figure it out.

 

Thanks

 

 

 

 

 

 

0 Kudos
3 REPLIES 3
camelotshadow Tutor
Tutor
16 12 0 1
Message 2 of 4
697
Flag Post
HP Recommended

How to Delete Empty Recovery Partition HP System Recovery Error

Searching all files for the time & found this one that mentions partition 2 recovery drive

 

Could this have made partition 2?

 

OS (C)/Windows/logs/Recoverydrive/Setupact

 

Setupact

 

2016-08-09 17:37:23, Info DlpMgrInit: WorkingPath = [C:\Users\CHRIST~1\AppData\Local\Temp\], Disposition = [None], Flags = [0x0], Diagnostics = [Yes], StockRegistrar = [Yes], UserRegistrar = [No]
2016-08-09 17:37:23, Info Command line: "C:\Windows\System32\RecoveryDrive.exe"
2016-08-09 17:37:23, Error GetESDImageLocation(189): Result = 0x80070002
2016-08-09 18:29:00, Info DlpMgrInit: WorkingPath = [C:\Users\CHRIST~1\AppData\Local\Temp\], Disposition = [None], Flags = [0x0], Diagnostics = [Yes], StockRegistrar = [Yes], UserRegistrar = [No]
2016-08-09 18:29:00, Info Command line: "C:\Windows\System32\RecoveryDrive.exe"
2016-08-09 18:29:00, Error GetESDImageLocation(189): Result = 0x80070002
2016-08-09 18:29:26, Error GetESDImageLocation(189): Result = 0x80070002
2016-08-09 18:29:27, Info Generate Reconstruction BMR config successfully
2016-08-09 18:29:27, Info Creating snapshot of drive [C:\] ([\\?\Volume{104ea69d-0000-0000-0000-100000000000}\])
2016-08-09 18:29:27, Info Initializing VSS
2016-08-09 18:29:33, Info Selecting writers and components
2016-08-09 18:29:33, Info Adding [Task Scheduler Writer] component [TasksStore] to snapshot
2016-08-09 18:29:33, Info Adding [VSS Metadata Store Writer] component [WriterMetadataStore] to snapshot
2016-08-09 18:29:33, Info Adding [Performance Counters Writer] component [PerformanceCounters] to snapshot
2016-08-09 18:29:45, Info Adding [System Writer] component [System Files] to snapshot
2016-08-09 18:29:46, Info Adding [ASR Writer] component [ASR] to snapshot
2016-08-09 18:29:46, Info Adding [ASR Writer] component [Volume{104ea69d-0000-0000-0000-100000000000}] to snapshot
2016-08-09 18:29:46, Info Adding [ASR Writer] component [Volume{104ea69d-0000-0000-0000-b0afe8000000}] to snapshot
2016-08-09 18:29:46, Info Adding [ASR Writer] component [harddisk0] to snapshot
2016-08-09 18:29:46, Info Adding [ASR Writer] component [BCD] to snapshot
2016-08-09 18:29:46, Info Adding [Registry Writer] component [Registry] to snapshot
2016-08-09 18:29:46, Info Adding [COM+ REGDB Writer] component [COM+ REGDB] to snapshot
2016-08-09 18:29:46, Info Adding [WMI Writer] component [WMI] to snapshot
2016-08-09 18:29:46, Info Creating snapshot
2016-08-09 18:29:47, Info VSS Writer Status: Writer: [Task Scheduler Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:47, Info VSS Writer Status: Writer: [VSS Metadata Store Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:47, Info VSS Writer Status: Writer: [Performance Counters Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:47, Info VSS Writer Status: Writer: [System Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:47, Info VSS Writer Status: Writer: [ASR Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:47, Info VSS Writer Status: Writer: [MSSearch Service Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:47, Info VSS Writer Status: Writer: [Shadow Copy Optimization Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:47, Info VSS Writer Status: Writer: [Registry Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:47, Info VSS Writer Status: Writer: [COM+ REGDB Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:47, Info VSS Writer Status: Writer: [WMI Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:53, Info VSS Writer Status: Writer: [Task Scheduler Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:53, Info VSS Writer Status: Writer: [VSS Metadata Store Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:53, Info VSS Writer Status: Writer: [Performance Counters Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:53, Info VSS Writer Status: Writer: [System Writer] State: [5], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:53, Info VSS Writer Status: Writer: [ASR Writer] State: [5], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:53, Info VSS Writer Status: Writer: [MSSearch Service Writer] State: [5], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:53, Info VSS Writer Status: Writer: [Shadow Copy Optimization Writer] State: [5], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:53, Info VSS Writer Status: Writer: [Registry Writer] State: [5], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:53, Info VSS Writer Status: Writer: [COM+ REGDB Writer] State: [5], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:53, Info VSS Writer Status: Writer: [WMI Writer] State: [5], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:54, Info VSS Writer Status: Writer: [Task Scheduler Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:54, Info VSS Writer Status: Writer: [VSS Metadata Store Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:54, Info VSS Writer Status: Writer: [Performance Counters Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:54, Info VSS Writer Status: Writer: [System Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:54, Info VSS Writer Status: Writer: [ASR Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:54, Info VSS Writer Status: Writer: [WMI Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:54, Info VSS Writer Status: Writer: [Shadow Copy Optimization Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:54, Info VSS Writer Status: Writer: [MSSearch Service Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:54, Info VSS Writer Status: Writer: [Registry Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:54, Info VSS Writer Status: Writer: [COM+ REGDB Writer] State: [1], Writer Error: [0x00000000], App Error: [0x00000001]
2016-08-09 18:29:54, Info Looking up snapshot volume
2016-08-09 18:29:55, Info Found snapshot volume: [\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3]
2016-08-09 18:29:55, Info CreateTask: Name = [], WorkingPath = [(inherited) C:\Users\CHRIST~1\AppData\Local\Temp\], TransportId = [00000000-0000-0000-0000-000000000000], Flags = [0x0]
2016-08-09 18:29:55, Info LayoutUsb: Initializing Boot WIM Path: [\\?\GLOBALROOT\device\harddisk0\partition2\Recovery\WindowsRE\WinRe.Wim]
2016-08-09 18:29:55, Info LayoutUsb: Initializing Install WIM Path: []
2016-08-09 18:29:55, Info LayoutUsb: Initializing Customization WIM Path: []
2016-08-09 18:29:55, Info LayoutUsb: Initializing OEM Winre WIM Path: []
2016-08-09 18:29:55, Info LayoutUsb: Initializing Reconstruction Drive: [E]
2016-08-09 18:29:55, Info LayoutUsb: Initializing Reconstruction Path Count: [9]
2016-08-09 18:29:55, Info LayoutUsb: Initializing Reconstruction Path: [ProgramData\Microsoft\Provisioning]
2016-08-09 18:29:55, Info LayoutUsb: Initializing Reconstruction Path: [ProgramData\Microsoft\Windows\AppxProvisioning.xml]
2016-08-09 18:29:55, Info LayoutUsb: Initializing Reconstruction Path: [ProgramData\Microsoft\Windows\ClipSvc\Archive]
2016-08-09 18:29:55, Info LayoutUsb: Initializing Reconstruction Path: [Users\Default]
2016-08-09 18:29:55, Info LayoutUsb: Initializing Reconstruction Path: [Windows\INF]
2016-08-09 18:29:55, Info LayoutUsb: Initializing Reconstruction Path: [Windows\InfusedApps]
2016-08-09 18:29:55, Info LayoutUsb: Initializing Reconstruction Path: [Windows\servicing]
2016-08-09 18:29:55, Info LayoutUsb: Initializing Reconstruction Path: [Windows\System32]
2016-08-09 18:29:55, Info LayoutUsb: Initializing Reconstruction Path: [Windows\WinSxS]
2016-08-09 18:29:55, Info LayoutUsb: Initializing Customizations Directory: [C:\Recovery\Customizations]
2016-08-09 18:29:55, Info LayoutUsb: Initializing OEM Extensibility Directory: [C:\Recovery\OEM]
2016-08-09 18:29:55, Info LayoutUsb: Initializing USB Drive: [?:]
2016-08-09 18:29:55, Info LayoutUsb: Initializing File System: [FAT32]
2016-08-09 18:29:55, Info LayoutUsb: Initializing Flags: [0x37]
2016-08-09 18:29:55, Info LayoutUsb: Initializing Volume Label: []
2016-08-09 18:29:55, Info LayoutUsb: Initializing Max Volume: [0x800000000]
2016-08-09 18:29:55, Info LayoutUsb: Initializing File Split Size: [0xED800000]
2016-08-09 18:29:55, Info LayoutUsb: Initializing Use Simplified Wim Split: [FALSE]
2016-08-09 18:29:55, Info LayoutUsb: Populating Boot Path: [C:\WINDOWS\Boot, EFI\bootmgfw.efi] -> [efi\boot\bootx64.efi]
2016-08-09 18:29:55, Info LayoutUsb: Populating Boot Path: [C:\WINDOWS\Boot, PCAT\bootmgr] -> [bootmgr]
2016-08-09 18:29:55, Info LayoutUsb: Populating Boot Path: [C:\WINDOWS\Boot, DVD\PCAT\BCD] -> [boot\BCD]
2016-08-09 18:29:55, Info LayoutUsb: Populating Boot Path: [C:\WINDOWS\Boot, resources\bootres.dll] -> [boot\resources\bootres.dll]
2016-08-09 18:29:55, Info LayoutUsb: Populating Boot Path: [C:\WINDOWS\Boot, EFI\bootmgr.efi] -> [bootmgr.efi]
2016-08-09 18:29:55, Info LayoutUsb: Populating Boot Path: [C:\WINDOWS\Boot, DVD\EFI\boot.sdi] -> [boot\boot.sdi]
2016-08-09 18:29:55, Info LayoutUsb: Populating Boot Path: [C:\WINDOWS\Boot, fonts] -> [boot\fonts]
2016-08-09 18:29:55, Info LayoutUsb: Populating Boot Path: [C:\WINDOWS\Boot, DVD\EFI\BCD] -> [efi\microsoft\boot\BCD]
2016-08-09 18:29:55, Info LayoutUsb: Populating Boot Path: [C:\WINDOWS\Boot, fonts] -> [efi\microsoft\boot\fonts]
2016-08-09 18:29:55, Info LayoutUsb: Populating Boot Path: [C:\WINDOWS\Boot, resources\bootres.dll] -> [efi\microsoft\boot\resources\bootres.dll]
2016-08-09 18:29:55, Info LayoutUsb: Populating WIM Path:
[\\?\GLOBALROOT\device\harddisk0\partition2\Recovery\WindowsRE\WinRe.Wim] -> [sources\boot.wim]
2016-08-09 18:29:55, Info RecoverUsb: Entering Prepare Method
2016-08-09 18:29:55, Info RecoverUsb: Leaving Prepare Method
2016-08-09 18:29:55, Info DlpTask: Entering Execute Method
2016-08-09 18:29:55, Info DlpTask: Transport not set. Skipping download phase.
2016-08-09 18:29:55, Info DlpTask: Executing Actions...
2016-08-09 18:29:55, Info Action execution thread timeout period: [1000 ms]
2016-08-09 18:29:55, Info ProgressHandlerAction: Sending initial progress message for action [0].
2016-08-09 18:29:55, Info RecoverUsb: Entering Execute Method
2016-08-09 18:29:55, Info RecoverUsb: Populating Oem Path: [C:\WINDOWS\system32\recovery\reagent.xml] -> [reagent.xml]
2016-08-09 18:29:55, Info RecoverUsb: Populating Oem Path: [C:\WINDOWS\system32\recovery\$PBR_ResetConfig.xml] -> [sources\$PBR_ResetConfig.xml]
2016-08-09 18:29:55, Info RecoverUsb: Populating Oem Path: [C:\WINDOWS\system32\recovery\$PBR_Diskpart.txt] -> [sources\$PBR_Diskpart.txt]
2016-08-09 18:30:01, Warning Wim Capture: Skipping [E:\Users\Default\Application Data] because access was denied
2016-08-09 18:30:01, Warning Wim Capture: Skipping [E:\Users\Default\Cookies] because access was denied
2016-08-09 18:30:01, Warning Wim Capture: Skipping [E:\Users\Default\Local Settings] because access was denied
2016-08-09 18:30:01, Warning Wim Capture: Skipping [E:\Users\Default\My Documents] because access was denied
2016-08-09 18:30:01, Warning Wim Capture: Skipping [E:\Users\Default\NetHood] because access was denied
2016-08-09 18:30:01, Warning Wim Capture: Skipping [E:\Users\Default\PrintHood] because access was denied
2016-08-09 18:30:01, Warning Wim Capture: Skipping [E:\Users\Default\Recent] because access was denied
2016-08-09 18:30:01, Warning Wim Capture: Skipping [E:\Users\Default\SendTo] because access was denied
2016-08-09 18:30:01, Warning Wim Capture: Skipping [E:\Users\Default\Start Menu] because access was denied
2016-08-09 18:30:01, Warning Wim Capture: Skipping [E:\Users\Default\Templates] because access was denied
2016-08-09 18:30:30, Warning Wim Capture: Skipping [E:\Users\Default\Documents\My Music] because access was denied
2016-08-09 18:30:30, Warning Wim Capture: Skipping [E:\Users\Default\Documents\My Pictures] because access was denied
2016-08-09 18:30:30, Warning Wim Capture: Skipping [E:\Users\Default\Documents\My Videos] because access was denied
2016-08-09 18:30:32, Warning Wim Capture: Skipping [E:\Users\Default\AppData\Local\Application Data] because access was denied
2016-08-09 18:30:32, Warning Wim Capture: Skipping [E:\Users\Default\AppData\Local\History] because access was denied
2016-08-09 18:30:32, Warning Wim Capture: Skipping [E:\Users\Default\AppData\Local\Temporary Internet Files] because access was denied
2016-08-09 18:30:36, Warning Wim Capture: Skipping [E:\Windows\System32\LogFiles\WMI\RtBackup] because access was denied
2016-08-09 18:30:39, Warning Wim Capture: Skipping [E:\Users\Default\AppData\Local\Microsoft\Windows\Temporary Internet Files] because access was denied
2016-08-09 18:30:41, Warning Wim Capture: Skipping [E:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\INetCache\Content.IE5] because access was denied
2016-08-09 18:30:41, Info LayoutUsb: Source directory size -> [12790513014] bytes
2016-08-09 18:30:41, Info LayoutUsb: Source maximum file size -> [435107052] bytes
2016-08-09 18:30:41, Info LayoutUsb: Restoring previous error mode: [0x0]...
2016-08-09 18:30:41, Info RecoverUsb: Leaving Execute Method
2016-08-09 18:30:41, Info ProgressHandlerAction: Sending final progress message for action [0].
2016-08-09 18:30:41, Info ProgressHandlerAction FinalUpdate: 0x0, 0x0 / 0x2FA5FBD76, 0x0
2016-08-09 18:30:41, Info ProgressHandlerAction: Sending final progress message for action [0].
2016-08-09 18:30:41, Info ProgressHandlerAction FinalUpdate: 0x0, 0x0 / 0x2FA5FBD76, 0x0
2016-08-09 18:30:41, Info Waiting for actions thread to exit.
2016-08-09 18:30:41, Info Actions thread has exited.
2016-08-09 18:30:41, Info DlpTask: Leaving Execute Method
2016-08-09 18:31:00, Info RecoveryDrive.exe completed with return value: 0x0

 

0 Kudos
camelotshadow Tutor
Tutor
16 12 0 1
Message 3 of 4
693
Flag Post
HP Recommended

How to Delete Empty Recovery Partition HP System Recovery Error

I checked disk defragmentation & I have run that on this system.

It lists another drive \\?\Volume 104ea. I sort of remember as I was afraid to defragment it not knowing what is was for.

I sort of remember it being there when I optimized the C drive last time.

Not sure why my memory is vague but maybe the empty recovery partition has always been there.

 

Makes me feel alot better as I thought my stupidly trying to create a recovery & the error messed up the HDD. Funny thing as it should not even have run as far as it did as it needs a USB flash which I don;t have.

I ran it a 2nd time & this time it correctly aborted after no usb drive was available.

 

I don;t know why HP doesn;t allow you to create a recovery on discs?

I feel more comfortable with that.

 

I was trying to get the system set up perfectly before I did a sytem image but I guess its good enough

& at least I'll have something to work with if something goes wrong. ( I do have one for win 10 1511)

 

I guess I can't worry about that 1 GB recovery partition for now but still appreciate any advice on this matter.

 

 

Should I contact HP to try to get a copy of the recovery disk? I only want the software not really the OS

as I think it was originally win 8 & I don;t want that. Still I know if HP has to repair it that they turn it back to win 8. Gosh really can't get a break these days. This error cost me a whole day of my time.

I guess its useful to have the win 8 just in case. Then will have to do it all over again to get back to win 10...

 

Thanks Again!

 

 

 

 

0 Kudos
camelotshadow Tutor
Tutor
16 12 0 1
Message 4 of 4
650
Flag Post
HP Recommended

How to Delete Empty Recovery Partition HP System Recovery Error

Solved it myself!

 

Checked event viewer windows system logs

Went back & checked every event 98 error.

 

Seems the partion 2 named in diskpart was installed when win 10 anniversay was installed.

Found the partiton previous to the lauch recovery media error.

 

Further testing revealed each time launch recovery media was attempted even though usb flas media was unavailable it either aborted because media was not available or I had to cancel it.

 

Each time this happened a error event 98 was logged & a new shadow copy file was written in a log.

 

So the lauch media recovery does make a error event 98 each time I lauch it with a new shadow copy number but apparently did not make the recovery partition.

 

Least I feel better about keeping the hidden recovery partition & know the error did not cause it to be made.

 

 

0 Kudos

Note on archived topics.

This topic has been archived. Information and links in this thread may no longer be available or relevant.
If you have a question create a new topic by clicking here and select the appropriate board.
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation