Incompatible version of the serializing package. (0x80070724)

System restore, System backup, Restore point, none of this stuff works. Its
always the same error: 'Incompatible version of the serializing package.
(0x80070724)'. Googled it every which way, but no joy! Anybody know if this
will ever be fixed? Not even a hint at Microsoft.com that this problem
exists. I figured this was the best way to to let them know. Anybody out
there heard anything about this error? Anything?
--
mitch

Hi,

This was my third google hit:
http://www.microsoft-tech.com/index.aspx?Content=32

Basically it looks like the error is caused by corruption in existing points
or the index. Disable this and clear the points, then restart it.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

"mitch707" <mitch707@discussions.microsoft.com> wrote in message
news:343226EB-FEC2-42AE-A539-84653788C0C1@microsoft.com...
> System restore, System backup, Restore point, none of this stuff works.
> Its
> always the same error: 'Incompatible version of the serializing package.
> (0x80070724)'. Googled it every which way, but no joy! Anybody know if
> this
> will ever be fixed? Not even a hint at Microsoft.com that this problem
> exists. I figured this was the best way to to let them know. Anybody out
> there heard anything about this error? Anything?
> --
> mitch

Yeah, I think that was my third Google hit as well. Actually there are less
than two dozen Google hits re this subject so it's easy to review them all.
And, like Dan, in his reply at the bottom of the page you refer to, it didn't
work for me either. When ever the 'System Properties Dialogue Box' opens and
it searches for drives, I get the error. In fact, no matter what I do with
any portion of this system, I get this error. Would you happen to know where
the 'system points' are stored and if access to them, other than through
'System Properties' is possible?

I really do appreciate your response, but in general I find that most
suggested solutions in most forums are a lot more difficult in their
execution than in their concept. Believe me, if it were this simple, I would
have never initiated my original post. Again, thanks for hearing me out.
--
mitch


"Rick Rogers" wrote:

> Hi,
>
> This was my third google hit:
> http://www.microsoft-tech.com/index.aspx?Content=32
>
> Basically it looks like the error is caused by corruption in existing points
> or the index. Disable this and clear the points, then restart it.
>
> --
> Best of Luck,
>
> Rick Rogers, aka "Nutcase" - Microsoft MVP
> http://mvp.support.microsoft.com/
> Windows help - www.rickrogers.org
> My thoughts http://rick-mvp.blogspot.com
>
> "mitch707" <mitch707@discussions.microsoft.com> wrote in message
> news:343226EB-FEC2-42AE-A539-84653788C0C1@microsoft.com...
> > System restore, System backup, Restore point, none of this stuff works.
> > Its
> > always the same error: 'Incompatible version of the serializing package.
> > (0x80070724)'. Googled it every which way, but no joy! Anybody know if
> > this
> > will ever be fixed? Not even a hint at Microsoft.com that this problem
> > exists. I figured this was the best way to to let them know. Anybody out
> > there heard anything about this error? Anything?
> > --
> > mitch
>
>

Hi,

It's the same location as in XP, the System Volume Information folder on the
root of each monitored volume. Perhaps this System Restore information from
MVP Bert Kinney will help: http://bertk.mvps.org/html/vista.html

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

"mitch707" <mitch707@discussions.microsoft.com> wrote in message
news:517275B9-C108-42C1-978E-FAEDC92520FC@microsoft.com...
> Yeah, I think that was my third Google hit as well. Actually there are
> less
> than two dozen Google hits re this subject so it's easy to review them
> all.
> And, like Dan, in his reply at the bottom of the page you refer to, it
> didn't
> work for me either. When ever the 'System Properties Dialogue Box' opens
> and
> it searches for drives, I get the error. In fact, no matter what I do with
> any portion of this system, I get this error. Would you happen to know
> where
> the 'system points' are stored and if access to them, other than through
> 'System Properties' is possible?
>
> I really do appreciate your response, but in general I find that most
> suggested solutions in most forums are a lot more difficult in their
> execution than in their concept. Believe me, if it were this simple, I
> would
> have never initiated my original post. Again, thanks for hearing me out.
> --
> mitch
>
>
> "Rick Rogers" wrote:
>
>> Hi,
>>
>> This was my third google hit:
>> http://www.microsoft-tech.com/index.aspx?Content=32
>>
>> Basically it looks like the error is caused by corruption in existing
>> points
>> or the index. Disable this and clear the points, then restart it.
>>
>> --
>> Best of Luck,
>>
>> Rick Rogers, aka "Nutcase" - Microsoft MVP
>> http://mvp.support.microsoft.com/
>> Windows help - www.rickrogers.org
>> My thoughts http://rick-mvp.blogspot.com
>>
>> "mitch707" <mitch707@discussions.microsoft.com> wrote in message
>> news:343226EB-FEC2-42AE-A539-84653788C0C1@microsoft.com...
>> > System restore, System backup, Restore point, none of this stuff works.
>> > Its
>> > always the same error: 'Incompatible version of the serializing
>> > package.
>> > (0x80070724)'. Googled it every which way, but no joy! Anybody know if
>> > this
>> > will ever be fixed? Not even a hint at Microsoft.com that this problem
>> > exists. I figured this was the best way to to let them know. Anybody
>> > out
>> > there heard anything about this error? Anything?
>> > --
>> > mitch
>>
>>

"It's in the same location as in XP..". That was a good one Rick! That one
really got to me. It's taken me almost twenty minutes to recompose myself.
O.K.,I don't have XP any more Rick. All I got is Vista and when I had XP, all
this stuff worked so I never had to go to that 'location'. Your buds article?
Nah, didn't help much.

Got the feeling I'm in the wrong forum here Rick. I think what I'll do is
use the Apple method for solving my computer problems.....I'll buy my way out
of it. Think I'll pick up Acronis True Image and burn my ISO's like Vista was
supposed to do but can't. Adios amigo, and thanks for playing.
--
mitch
"Condensing fact from the vapor of nuance."


"Rick Rogers" wrote:

> Hi,
>
> It's the same location as in XP, the System Volume Information folder on the
> root of each monitored volume. Perhaps this System Restore information from
> MVP Bert Kinney will help: http://bertk.mvps.org/html/vista.html
>
> --
> Best of Luck,
>
> Rick Rogers, aka "Nutcase" - Microsoft MVP
> http://mvp.support.microsoft.com/
> Windows help - www.rickrogers.org
> My thoughts http://rick-mvp.blogspot.com
>
> "mitch707" <mitch707@discussions.microsoft.com> wrote in message
> news:517275B9-C108-42C1-978E-FAEDC92520FC@microsoft.com...
> > Yeah, I think that was my third Google hit as well. Actually there are
> > less
> > than two dozen Google hits re this subject so it's easy to review them
> > all.
> > And, like Dan, in his reply at the bottom of the page you refer to, it
> > didn't
> > work for me either. When ever the 'System Properties Dialogue Box' opens
> > and
> > it searches for drives, I get the error. In fact, no matter what I do with
> > any portion of this system, I get this error. Would you happen to know
> > where
> > the 'system points' are stored and if access to them, other than through
> > 'System Properties' is possible?
> >
> > I really do appreciate your response, but in general I find that most
> > suggested solutions in most forums are a lot more difficult in their
> > execution than in their concept. Believe me, if it were this simple, I
> > would
> > have never initiated my original post. Again, thanks for hearing me out.
> > --
> > mitch
> >
> >
> > "Rick Rogers" wrote:
> >
> >> Hi,
> >>
> >> This was my third google hit:
> >> http://www.microsoft-tech.com/index.aspx?Content=32
> >>
> >> Basically it looks like the error is caused by corruption in existing
> >> points
> >> or the index. Disable this and clear the points, then restart it.
> >>
> >> --
> >> Best of Luck,
> >>
> >> Rick Rogers, aka "Nutcase" - Microsoft MVP
> >> http://mvp.support.microsoft.com/
> >> Windows help - www.rickrogers.org
> >> My thoughts http://rick-mvp.blogspot.com
> >>
> >> "mitch707" <mitch707@discussions.microsoft.com> wrote in message
> >> news:343226EB-FEC2-42AE-A539-84653788C0C1@microsoft.com...
> >> > System restore, System backup, Restore point, none of this stuff works.
> >> > Its
> >> > always the same error: 'Incompatible version of the serializing
> >> > package.
> >> > (0x80070724)'. Googled it every which way, but no joy! Anybody know if
> >> > this
> >> > will ever be fixed? Not even a hint at Microsoft.com that this problem
> >> > exists. I figured this was the best way to to let them know. Anybody
> >> > out
> >> > there heard anything about this error? Anything?
> >> > --
> >> > mitch
> >>
> >>
>
>

Give this a try--you'll need to do this on every volume and you might need
to repeat this a couple times.


Go to an elevated command prompt and type the following commands one at a
time:

Vssadmin list shadowstorage /for=c:
<note the shadow storage size for use later>

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

<install or uninstall something like FreeCell>

vssadmin resize shadowstorage /for=c: /on=c: /maxsize=<original value>


--
This posting is provided "AS IS" with no warranties, and confers no rights.

Want to learn more about Windows file and storage technologies? Visit our
team blog at http://blogs.technet.com/filecab/default.aspx.


"mitch707" <mitch707@discussions.microsoft.com> wrote in message
news:343226EB-FEC2-42AE-A539-84653788C0C1@microsoft.com...
> System restore, System backup, Restore point, none of this stuff works.
> Its
> always the same error: 'Incompatible version of the serializing package.
> (0x80070724)'. Googled it every which way, but no joy! Anybody know if
> this
> will ever be fixed? Not even a hint at Microsoft.com that this problem
> exists. I figured this was the best way to to let them know. Anybody out
> there heard anything about this error? Anything?
> --
> mitch

Jill, we ever meet, lunch is on me! and bring Rick with you! Worked like a
charm.

The only thing I would add would be, first command:

vssadmin list volumes

I have four drives, 2 SATA and 2 IDE

Thanks again, you folks are o.k. by me.
--
mitch



"Jill Zoeller [MSFT]" wrote:

> Give this a try--you'll need to do this on every volume and you might need
> to repeat this a couple times.
>
>
> Go to an elevated command prompt and type the following commands one at a
> time:
>
> Vssadmin list shadowstorage /for=c:
> <note the shadow storage size for use later>
>
> vssadmin resize shadowstorage /for=c: /on=c: /maxsize=300MB
>
> <install or uninstall something like FreeCell>
>
> vssadmin resize shadowstorage /for=c: /on=c: /maxsize=<original value>
>
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Want to learn more about Windows file and storage technologies? Visit our
> team blog at http://blogs.technet.com/filecab/default.aspx.
>
>
> "mitch707" <mitch707@discussions.microsoft.com> wrote in message
> news:343226EB-FEC2-42AE-A539-84653788C0C1@microsoft.com...
> > System restore, System backup, Restore point, none of this stuff works.
> > Its
> > always the same error: 'Incompatible version of the serializing package.
> > (0x80070724)'. Googled it every which way, but no joy! Anybody know if
> > this
> > will ever be fixed? Not even a hint at Microsoft.com that this problem
> > exists. I figured this was the best way to to let them know. Anybody out
> > there heard anything about this error? Anything?
> > --
> > mitch
>
>

Glad this worked! And thanks for the tip about adding the first command. We
had just helped another customer with a similar problem and this was the
workaround the dev team gave me. The problem is due to corrupt metadata on
the shadow copy (or something like that).



--
This posting is provided "AS IS" with no warranties, and confers no rights.

Want to learn more about Windows file and storage technologies? Visit our
team blog at http://blogs.technet.com/filecab/default.aspx.


"mitch707" <mitch707@discussions.microsoft.com> wrote in message
news:788F9917-D2A8-4A6D-802F-6C743F64D036@microsoft.com...
> Jill, we ever meet, lunch is on me! and bring Rick with you! Worked like a
> charm.
>
> The only thing I would add would be, first command:
>
> vssadmin list volumes
>
> I have four drives, 2 SATA and 2 IDE
>
> Thanks again, you folks are o.k. by me.
> --
> mitch
>
>
>
> "Jill Zoeller [MSFT]" wrote:
>
>> Give this a try--you'll need to do this on every volume and you might
>> need
>> to repeat this a couple times.
>>
>>
>> Go to an elevated command prompt and type the following commands one at a
>> time:
>>
>> Vssadmin list shadowstorage /for=c:
>> <note the shadow storage size for use later>
>>
>> vssadmin resize shadowstorage /for=c: /on=c: /maxsize=300MB
>>
>> <install or uninstall something like FreeCell>
>>
>> vssadmin resize shadowstorage /for=c: /on=c: /maxsize=<original value>
>>
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> Want to learn more about Windows file and storage technologies? Visit our
>> team blog at http://blogs.technet.com/filecab/default.aspx.
>>
>>
>> "mitch707" <mitch707@discussions.microsoft.com> wrote in message
>> news:343226EB-FEC2-42AE-A539-84653788C0C1@microsoft.com...
>> > System restore, System backup, Restore point, none of this stuff works.
>> > Its
>> > always the same error: 'Incompatible version of the serializing
>> > package.
>> > (0x80070724)'. Googled it every which way, but no joy! Anybody know if
>> > this
>> > will ever be fixed? Not even a hint at Microsoft.com that this problem
>> > exists. I figured this was the best way to to let them know. Anybody
>> > out
>> > there heard anything about this error? Anything?
>> > --
>> > mitch
>>
>>

"Jill Zoeller [MSFT]" wrote:

> Glad this worked! And thanks for the tip about adding the first command. We
> had just helped another customer with a similar problem and this was the
> workaround the dev team gave me. The problem is due to corrupt metadata on
> the shadow copy (or something like that).
>
>
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Want to learn more about Windows file and storage technologies? Visit our
> team blog at http://blogs.technet.com/filecab/default.aspx.
>
>
> "mitch707" <mitch707@discussions.microsoft.com> wrote in message
> news:788F9917-D2A8-4A6D-802F-6C743F64D036@microsoft.com...
> > Jill, we ever meet, lunch is on me! and bring Rick with you! Worked like a
> > charm.
> >
> > The only thing I would add would be, first command:
> >
> > vssadmin list volumes
> >
> > I have four drives, 2 SATA and 2 IDE
> >
> > Thanks again, you folks are o.k. by me.
> > --
> > mitch
> >
> >
> >
> > "Jill Zoeller [MSFT]" wrote:
> >
> >> Give this a try--you'll need to do this on every volume and you might
> >> need
> >> to repeat this a couple times.
> >>
> >>
> >> Go to an elevated command prompt and type the following commands one at a
> >> time:
> >>
> >> Vssadmin list shadowstorage /for=c:
> >> <note the shadow storage size for use later>
> >>
> >> vssadmin resize shadowstorage /for=c: /on=c: /maxsize=300MB
> >>
> >> <install or uninstall something like FreeCell>
> >>
> >> vssadmin resize shadowstorage /for=c: /on=c: /maxsize=<original value>
> >>
> >>
> >> --
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> Want to learn more about Windows file and storage technologies? Visit our
> >> team blog at http://blogs.technet.com/filecab/default.aspx.
> >>
> >>
> >> "mitch707" <mitch707@discussions.microsoft.com> wrote in message
> >> news:343226EB-FEC2-42AE-A539-84653788C0C1@microsoft.com...
> >> > System restore, System backup, Restore point, none of this stuff works.
> >> > Its
> >> > always the same error: 'Incompatible version of the serializing
> >> > package.
> >> > (0x80070724)'. Googled it every which way, but no joy! Anybody know if
> >> > this
> >> > will ever be fixed? Not even a hint at Microsoft.com that this problem
> >> > exists. I figured this was the best way to to let them know. Anybody
> >> > out
> >> > there heard anything about this error? Anything?
> >> > --
> >> > mitch
> >>
> >>
>
>

Ops, I truely no nothing about PCs!, So how does a luddite get rid of this
problem, no idea what your on about, is there just an easy fix for this or
will i be plagued not ever to turn my system restore on. I know where the on
and off switch is but that probably doesnt help, so please is there any
layperson way of getting rid of this fault!!!!!!! without doing techy
stuff....sorry i know its lame but God gave us all different gifts, and if
its what wrong with a human, then I am your person, but computers, wheres the
PC medics who can do it for me.....no one at any other technical support
seems to recognise this affliction....PLEASE HELP!

"The luddite" wrote:

>
>
> "Jill Zoeller [MSFT]" wrote:
>
> > Glad this worked! And thanks for the tip about adding the first command. We
> > had just helped another customer with a similar problem and this was the
> > workaround the dev team gave me. The problem is due to corrupt metadata on
> > the shadow copy (or something like that).
> >
> >
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> > Want to learn more about Windows file and storage technologies? Visit our
> > team blog at http://blogs.technet.com/filecab/default.aspx.
> >
> >
> > "mitch707" <mitch707@discussions.microsoft.com> wrote in message
> > news:788F9917-D2A8-4A6D-802F-6C743F64D036@microsoft.com...
> > > Jill, we ever meet, lunch is on me! and bring Rick with you! Worked like a
> > > charm.
> > >
> > > The only thing I would add would be, first command:
> > >
> > > vssadmin list volumes
> > >
> > > I have four drives, 2 SATA and 2 IDE
> > >
> > > Thanks again, you folks are o.k. by me.
> > > --
> > > mitch
> > >
> > >
> > >
> > > "Jill Zoeller [MSFT]" wrote:
> > >
> > >> Give this a try--you'll need to do this on every volume and you might
> > >> need
> > >> to repeat this a couple times.
> > >>
> > >>
> > >> Go to an elevated command prompt and type the following commands one at a
> > >> time:
> > >>
> > >> Vssadmin list shadowstorage /for=c:
> > >> <note the shadow storage size for use later>
> > >>
> > >> vssadmin resize shadowstorage /for=c: /on=c: /maxsize=300MB
> > >>
> > >> <install or uninstall something like FreeCell>
> > >>
> > >> vssadmin resize shadowstorage /for=c: /on=c: /maxsize=<original value>
> > >>
> > >>
> > >> --
> > >> This posting is provided "AS IS" with no warranties, and confers no
> > >> rights.
> > >>
> > >> Want to learn more about Windows file and storage technologies? Visit our
> > >> team blog at http://blogs.technet.com/filecab/default.aspx.
> > >>
> > >>
> > >> "mitch707" <mitch707@discussions.microsoft.com> wrote in message
> > >> news:343226EB-FEC2-42AE-A539-84653788C0C1@microsoft.com...
> > >> > System restore, System backup, Restore point, none of this stuff works.
> > >> > Its
> > >> > always the same error: 'Incompatible version of the serializing
> > >> > package.
> > >> > (0x80070724)'. Googled it every which way, but no joy! Anybody know if
> > >> > this
> > >> > will ever be fixed? Not even a hint at Microsoft.com that this problem
> > >> > exists. I figured this was the best way to to let them know. Anybody
> > >> > out
> > >> > there heard anything about this error? Anything?
> > >> > --
> > >> > mitch
> > >>
> > >>
> >
> >

[johnbevington]

Incompatible version of the serializing package. (0x80070724)

Thanks for the info. it worked great.

(First I type ‘cd\’ to get to the root directory)

C:\Windows\system32>cd\

(Then this is what appeared on the screen)

C:\>

(Now I know I did not need to cd to the root directory but I did it never the less Then at the command prompt I types what you said to.)

C:\>Vssadmin list shadowstorage /for=c:

(Then this is what appeared on the screen)

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{adfa6909-8d40-11dc-a78f-806e6f6e6963}\
Shadow Copy Storage volume: (C:)\\?\Volume{adfa6909-8d40-11dc-a78f-806e6f6e69
63}\
Used Shadow Copy Storage space: 28.742 GB
Allocated Shadow Copy Storage space: 30.084 GB
Maximum Shadow Copy Storage space: 33.419 GB

(I was surprised to see that the Shadow Copy Storage space & etc. was in the GB’s. I was a bit afraid to continue with what you said, but knowing that I made a copy of all my all my files & etc. on a external hard drive, I continued, as you said by.)

C:\>vssadmin resize shadowstorage /for=c: /on=c: /maxsize=300MB

(Then this is what appeared on the screen)

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Successfully resized the shadow copy storage association

(Then I typed what I really did not think you meant for us to type at the command prompt but I really did not know, & thought it would not matter for I was sure it would not do anything, & I was right. Don’t think I’m nuts. I just wanted to be sure.)

C:\><install or uninstall something like FreeCell>

(Then this is what appeared on the screen)

The syntax of the command is incorrect.

(Don’t laugh but I just wanted to be sure, I have not worked in dos much for years. Then I did as you said & typed at the command prompt this.)

C:\>vssadmin resize shadowstorage /for=c: /on=c: /maxsize=<original value>

(Then this is what appeared on the screen)

The syntax of the command is incorrect.

(I repeated it two more times with the same results.)’

(Now I’m starting to think that I should have put in the original value of the Maximum Shadow Copy Storage space (in my case 33.419 GB), instead of the word ‘original Value’ as well as leaving out the ‘< >’.’ Now as of yet I have only made a back up file of my C: drive & all seems well, but do you think I should go back & set the original value of C: & D: drive? I did have to do this process to my D: drive (a partition of the main hard drive) to get my systems to quite giving me the ‘Incompatible version of the serializing package. (0x80070724)’when trying to make a back up or system restore.)

(Now for some reason I tried it without the ‘=<original value> at the end next. (I‘m including this because I thought you might find it useful or at least interesting.))

C:\>vssadmin resize shadowstorage /for=c: /on=c: /maxsize

(Then this is what appeared on the screen)

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Error: Invalid option value.

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. If MaxSizeSpec is not
specified, there no limit to the amount of space it may use. As certain
shadow copies are deleted, the shadow copy storage space will then
shrink. 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. If a suffix is not supplied, MaxSizeSpec is in
bytes.

Example Usage: vssadmin Resize ShadowStorage /For=C: /On=D: /MaxSize=900MB

(Then I wanted to see what it would say about my Shadow Copy Storage space so I repeated the command you gave us.)

C:\>Vssadmin list shadowstorage /for=c:

(Then this is what appeared on the screen)

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{adfa6909-8d40-11dc-a78f-806e6f6e6963}\
Shadow Copy Storage volume: (C:)\\?\Volume{adfa6909-8d40-11dc-a78f-806e6f6e69
63}\
Used Shadow Copy Storage space: 0 B
Allocated Shadow Copy Storage space: 0 B
Maximum Shadow Copy Storage space: 300 MB

(Now after I did this process to the C: drive it still was not working right so I tried it for my D: drive that is named ‘Recovery’ & is only 10 GB in size of the 222 GB hard drive that is used for C: & D:.)

(Then I did as you said aging at the elevated command prompt but used ‘D’: instead of ‘C’:)

C:\>Vssadmin list shadowstorage /for=D:

(Then this is what appeared on the screen)

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Shadow Copy Storage association
For volume: (D:)\\?\Volume{adfa6908-8d40-11dc-a78f-806e6f6e6963}\
Shadow Copy Storage volume: (D:)\\?\Volume{adfa6908-8d40-11dc-a78f-806e6f6e69
63}\
Used Shadow Copy Storage space: 1.226 GB
Allocated Shadow Copy Storage space: 1.487 GB
Maximum Shadow Copy Storage space: 1.5 GB

(Then I did as you said aging at the elevated command prompt but used ‘D’: instead of ‘C’:)

C:\>vssadmin resize shadowstorage /for=D: /on=D: /maxsize=300MB

(Then this is what appeared on the screen)

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Successfully resized the shadow copy storage association

(Then I did as you said aging at the elevated command prompt but used ‘D’: instead of ‘C’ just to see what it would say.)

C:\>Vssadmin list shadowstorage /for=D:

(Then this is what appeared on the screen)

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Shadow Copy Storage association
For volume: (D:)\\?\Volume{adfa6908-8d40-11dc-a78f-806e6f6e6963}\
Shadow Copy Storage volume: (D:)\\?\Volume{adfa6908-8d40-11dc-a78f-806e6f6e69
63}\
Used Shadow Copy Storage space: 32.359 MB
Allocated Shadow Copy Storage space: 300 MB
Maximum Shadow Copy Storage space: 300 MB

(I think I’ll go ahead & change the Maximum Shadow Copy Storage space to the original sizes of the D: & C: partitions of my internal hard drive. The phrase ‘elevated’ in your wording ‘elevated command prompt’, was new to me but now I know what you mean, in that it is a command prompt run with administrative privileges. Thanks ever so much.)