KB2732487 is unable to update - Error Code 800700B7

NoelDP · 20 Mar 2013

Still the 800700b7 error?

See if this helps - it seems that it can be caused by corrupted Shadow Copies.

1 close all windows
2. Resize Maximum Shadow Copy Storage Space by running the following command, there may be caused by limited space.

1) Click Start, click All Programs, click Accessories, and then right-click Command Prompt.
2) Click Run as administrator.
3) At the command prompt, type the following command, and then press ENTER:

vssadmin list shadowstorage /for=c:

4) Note the Maximum Shadow Copy Storage Space value.
5) At the command prompt, type the following command, and then press ENTER:

vssadmin resize shadowstorage /for=c: /on=c: /maxsize=300Mb

6) Close the Command Prompt window.

ern815 · 20 Mar 2013

Here's the results!

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\windows\system32>vssadmin list shadowstorage /for=c:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Shadow Copy Storage association
For volume: (C:)\\?\Volume{181bf346-01dd-11e0-9253-806e6f6e6963}\
Shadow Copy Storage volume: (C:)\\?\Volume{181bf346-01dd-11e0-9253-806e6f6e69
63}\
Used Shadow Copy Storage space: 9.522 GB (1%)
Allocated Shadow Copy Storage space: 9.93 GB (1%)
Maximum Shadow Copy Storage space: 10 GB (1%)

```````````````````````````````````````````````````````````````````````````````````````````````````` `````````````````````````````````````````````
C:\windows\system32>vssadmin resize shadowstorage /for=c: /on=c: /maxsize=300Mb
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Error: Specified number is invalid
Resize ShadowStorage /For=ForVolumeSpec /On=OnVolumeSpec /MaxSize=MaxSizeSpec
- Resizes the maximum size for a shadow copy storage association between
ForVolumeSpec and OnVolumeSpec. Resizing the storage association may cause
shadow
copies to disappear. As certain shadow copies are deleted, the shadow copy
storage
space will then shrink. If MaxSizeSpec is set to the value UNBOUNDED, the s
hadow copy
storage space will be unlimited. MaxSizeSpec can be specified in bytes or a
s a
percentage of the ForVolumeSpec storage volume. For byte level specificatio
n,
MaxSizeSpec must be 300MB or greater and accepts the following suffixes: KB,
MB, GB, TB,
PB and EB. Also, B, K, M, G, T, P, and E are acceptable suffixes. To speci
fy MaxSizeSpec
as percentage, use the % character as the suffix to the numeric value. If a
suffix is not
supplied, MaxSizeSpec is in bytes.
Example Usage: vssadmin Resize ShadowStorage /For=C: /On=D: /MaxSize=900MB
vssadmin Resize ShadowStorage /For=C: /On=D: /MaxSize=UNBOUN
DED
vssadmin Resize ShadowStorage /For=C: /On=C: /MaxSize=20%
C:\windows\system32>
C:\windows\system32>

NoelDP · 20 Mar 2013

Heh! - the command was a direct crib from an MS techie's post... just goes to show that they get it wrong as well :)

Try this command instead

vssadmin Resize ShadowStorage /For=C: /On=C: /MaxSize=2GB

This will force a flush of the data, so let's see how much remains....

vssadmin list shadowstorage /for=c:

then bump it back up again

vssadmin Resize ShadowStorage /For=C: /On=C: /MaxSize=10GB

...and check that we've actually changed something

vssadmin list shadowstorage /for=c:

ern815 · 20 Mar 2013

I think the resize is successful! :)

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\windows\system32>vssadmin Resize ShadowStorage /For=C: /On=C: /MaxSize=2GB
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Successfully resized the shadow copy storage association
C:\windows\system32>vssadmin list shadowstorage /for=c:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Shadow Copy Storage association
For volume: (C:)\\?\Volume{181bf346-01dd-11e0-9253-806e6f6e6963}\
Shadow Copy Storage volume: (C:)\\?\Volume{181bf346-01dd-11e0-9253-806e6f6e69
63}\
Used Shadow Copy Storage space: 1.351 GB (0%)
Allocated Shadow Copy Storage space: 1.655 GB (0%)
Maximum Shadow Copy Storage space: 2 GB (0%)

C:\windows\system32>
C:\windows\system32>vssadmin Resize ShadowStorage /For=C: /On=C: /MaxSize=10GB
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Successfully resized the shadow copy storage association
C:\windows\system32>
C:\windows\system32>vssadmin list shadowstorage /for=c:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Shadow Copy Storage association
For volume: (C:)\\?\Volume{181bf346-01dd-11e0-9253-806e6f6e6963}\
Shadow Copy Storage volume: (C:)\\?\Volume{181bf346-01dd-11e0-9253-806e6f6e69
63}\
Used Shadow Copy Storage space: 1.353 GB (0%)
Allocated Shadow Copy Storage space: 1.655 GB (0%)
Maximum Shadow Copy Storage space: 10 GB (1%)

C:\windows\system32>

NoelDP · 20 Mar 2013

Great - try Windows Update again and we'll see if that's made any difference.

ern815 · 20 Mar 2013

I tried, but still facing the error code: 800700b7

NoelDP · 20 Mar 2013

Oh, b^gg€r!

Let's try this....

Open WindowsExplorer (Computer)

Navigate to the C:\Windows folder

Find the System32 sub-folder and right-click on it

select Properties

Clear the 'blob'from the 'Read-only (Only applies to files infolder)' box by clicking on it until it's plain white.

Click on Apply.

Make sure thatthe radio button for 'Apply changes to thisfolder, subfolders and files' is set, and click OK.

Accept theAdministrator prompt. After a couple of seconds, you'll be told there is anerror - click on the 'Ignore all' button.

Wait for it tofinish - it could take a couple of minutes.

OK out, and exitWindows Explorer.

Reboot twice

Now try WU again

ern815 · 20 Mar 2013

The same error still persists.

ern815 · 22 Mar 2013

Noel, anymore suggestions that we could solve the issues?

NoelDP · 22 Mar 2013

I'm thinking - it's a slow process :)
back later!