[SOLVED] cannot create system restore point after defragmentation

[carl a]

I used defraggler to defrag my hard drive and afterward notice that I could not create a new restore point , the message I am getting is restore point could not be created catastrophic failure 0x8000fff.this computer is windows vista 64 bit, high tech help will be greatly appreciated. Thanks

 

[xilolee]

Hi carl a. :)

Launch this command from an elevated command prompt:

echo. & dir c:\syste* /a /q |findstr /i /c:"<dir>" & echo. & icacls c:\syste*

I get:

[NO-PARSE]24/09/2016  22.41    <DIR>          BUILTIN\Administrators System Volume Information

c:\System Volume Information BUILTIN\Administrators:(OI)(CI)(F)
                             NT AUTHORITY\SYSTEM:(OI)(CI)(F)

Successfully processed 1 files; Failed processing 0 files[/NO-PARSE]

You should get something very similar (I think).


It could also possible the dirty bit was set, hence try to launch the following command (always from an elevated command prompt):

chkdsk c: /f

Windows usually wants to be rebooted to perform that command.

 

[carl a]

Hey Xilolee what's up . that is exactly what I got, I have also a thread open in the sfc /scannow cannot start repairs , Brian is working on that ,just to let you know the issues I am having with this machine at this time here is a picture from the cmd .

 

[xilolee]

It seems your "system volume information" folder doesn't grant permissions to the administrators (but it could be normal for windows vista, I'm not sure...).
By the way, I was editing the message and I added something at the end of it that you could try.

And I think it's better if you inform BrianDrab about this topic (maybe he could agree to launch the chkdsk and it could help you to add the administrators permissions with the sfcfix tool --- this is quite simple to do also through the windows GUI...).

 

[carl a]

Hello Xilolee you are right I tried to take permission to the system volume information folder but it would not allow me to gain access to change permission. I performed a chkdsk without errors and my cbs .log has ten errors it seems as though the sfc /scannow problem and my update problem is affecting other areas of my computer.I also notice in trouble shooting that the vss event is not registered. and I will inform BrianDrab about what you discovered.

 

[xilolee]

From an elevated command prompt copy/paste systempropertiesprotection and press enter.
Check if the checkbox near your system drive is ticked.
If it's unticked, tick it.
If it's ticked, untick it, press apply, tick it, press apply and ok.
Then re-try to create a new point.

If that won't work, try to increase the system restore folder size:

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

Then re-try to create a new point.

If that won't work, let's get some logs (with the hope they'll help...):

(echo. & vssadmin list providers & echo. & vssadmin list shadows & echo. & vssadmin list shadowstorage & echo. & vssadmin list volumes & echo. & vssadmin list writers) > "%userprofile%\desktop\VSSadmin results.txt"

After the command you should find "vssadmin results.txt" on your desktop: zip it and upload it here.

 

[carl a]

okay I am back with you performed all the steps the log txt is needed.

 

[xilolee]

Did you wait the end of the command? (Maybe the vssadmin WinVista version is different from Win10 version)

Now I'll show you the differences between your results and mine.

The only difference in "List providers" is "Copyright 2001-2013".
The ID is the same only for this entry, hence it seems this command didn't change through all these years (from WinVista to Win10).
All of the other IDs must be different from mine.

Read More:

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7

Your "list shadows" is EMPTY (following is mine):

Read More:

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Contents of shadow copy set ID: {7d1ff21e-7c57-45e5-993e-3e4ca047fd22}
Contained 1 shadow copies at creation time: 03/10/2016 01.35.04
Shadow Copy ID: {03bb4044-9872-47b2-9cba-d0cf4c3fae87}
Original Volume: (C:)\\?\Volume{58bbe694-d631-4812-8ab7-05460b5e31b1}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
Originating Machine: XILO
Service Machine: XILO
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered

You get two results about "list shadowstorage", I only get one (similar to your second entry, that it seems the one generated with the "resize shadowstorage" at sixth post):

Read More:

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Shadow Copy Storage association
For volume: (\\?\Volume{e36db24f-3b20-11e6-bac9-806e6f6e6963}\)\\?\Volume{e36db24f-3b20-11e6-bac9-806e6f6e6963}\
Shadow Copy Storage volume: (\\?\Volume{e36db24f-3b20-11e6-bac9-806e6f6e6963}\)\\?\Volume{e36db24f-3b20-11e6-bac9-806e6f6e6963}\
Used Shadow Copy Storage space: 0 B
Allocated Shadow Copy Storage space: 0 B
Maximum Shadow Copy Storage space: 300 MB


Shadow Copy Storage association
For volume: (C:)\\?\Volume{e36db250-3b20-11e6-bac9-806e6f6e6963}\
Shadow Copy Storage volume: (C:)\\?\Volume{e36db250-3b20-11e6-bac9-806e6f6e6963}\
Used Shadow Copy Storage space: 0 B
Allocated Shadow Copy Storage space: 0 B
Maximum Shadow Copy Storage space: 10 GB

You get (again) two values about "list volumes", for your C: drive (it seems); I get one for each of my partitions.

Read More:

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

Volume path: \\?\Volume{e36db24f-3b20-11e6-bac9-806e6f6e6963}\
Volume name: \\?\Volume{e36db24f-3b20-11e6-bac9-806e6f6e6963}\

Volume path: C:\
Volume name: \\?\Volume{e36db250-3b20-11e6-bac9-806e6f6e6963}\

I get the "list writers" result, you don't have that result (hence my first question at the start of this post: did you wait until the command finished/ended?):

Read More:

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Waiting for responses.
These may be delayed if a shadow copy is being prepared.
Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error
Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error
Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {a89581ef-376a-4c01-b981-5896dbfe8391}
State: [1] Stable
Last error: No error
Writer name: 'MSSearch Service Writer'
Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Writer Instance Id: {f14d88d4-9282-48a6-ba4a-ac6f892cc502}
State: [5] Waiting for completion
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {3866d058-f487-4941-a5b7-c1670f8a3d73}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {58eed8fe-0c40-4ae2-82a7-52d0a3c5b49d}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {aa56ed28-6fbe-43c9-ae2e-887057a7c1da}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {4413e12c-c4c2-4176-a555-c36735ae0a32}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {fcb5cb0e-e0b6-4a54-8364-f667c0739243}
State: [5] Waiting for completion
Last error: No error

Therefore we must find the commands to change the main differences between your results and mine.

 

[xilolee]

(All the commands should be run from an elevated command prompt)

Could you try this command (I get error on windows 10, but it seems it's supported from vista to 8)?

vssadmin create shadow /for=c:

If it fails, run vssadmin /? (and show its result).
If instead it works, launch vssadmin list shadows (and show its result).

 

[carl a]

yes I did wait for the command to finish/end and that was the results I gotten. I ran the same command and got the same results. The vssadmin create shadow /for=c came back as invalid command here is a view of all the commands resuts

 

[carl a]

The last command vssadmin list shadow was miss spelled in the command line. after correcting the spelling the result said no item found that satisfy the query

 

[xilolee]

Try these commands (from an elevated command prompt), try to create a new restore point and post the commands results here:

(sc query sens & sc qc sens & sc query vss & sc qc vss & sc query comsysapp & sc qc comsysapp & sc query swprv & sc qc swprv & sc query eventsystem & sc qc eventsystem)|findstr /i /c:"y_n" /c:"t_t" /c:"e_n" /c:"ate"

vssadmin delete shadows /all

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

 

[carl a]

The resize worked the other command vssadmin is an invalid command the the first elevated command information produce it's log so here is a picture of the reports

 

[xilolee]

Try:

vssadmin delete shadows /for=c: /all 
vssadmin delete shadows /for=c: /oldest

Read More:

C:\>vssadmin delete shadows /for=c: /all

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Do you really want to delete 1 shadow copies (Y/N): [N]? y
Successfully deleted 1 shadow copies.

C:\>vssadmin delete shadows /for=c: /all

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
No items found that satisfy the query.

C:\>vssadmin delete shadows /for=c: /oldest

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
No items found that satisfy the query.

 

[carl a]

the command reply is invalid invalid command for both commands

 

[xilolee]

Ok... Let's see what (vss) files are present on your system:

dir es.dll /b & dir eventc*.dll /b & dir msx*.dll /b  & dir ole3*.dll /b & dir stdpr*.dll /b & dir /b swpr*.dll & dir vss*.dll /b

I get:

es.dll
eventcls.dll
msxml3.dll
msxml3r.dll
msxml6.dll
msxml6r.dll
ole32.dll
File Not Found
swprv.dll
vssapi.dll
vsstrace.dll
vss_ps.dll

 

[carl a]

I got the same thing you got.

 

[BrianDrab]

It looks like two of us are working on this issue. Carl, this isn't good as xilolee and myself could have been causing each other issues while trying to resolve. I'll let you work with xiolee to get the restore point issue resolved. Once that is resolved and if you are still having issues with sfc, then come back to your other post and we will continue.

https://www.sysnative.com/forums/wi...ld-not-start-repair-service-3.html#post168165

 

[xilolee]

Open notepad, copy/paste the following text in it, save the file as RegisterVSS.BAT (RegisterVSS.bat.txt won't work), right click the file and run it as an administrator.
Reboot windows and re-try to create a system restore point.

cd /d c:\windows\system32
regsvr32 /s atl.dll
regsvr32 /s blb_ps.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml6.dll
regsvr32 /s ole32.dll
regsvr32 /s spp.dll
regsvr32 /s srcore.dll
regsvr32 /s srwmi.dll
regsvr32 /s vds_ps.dll
regsvr32 /s vss_ps.dll
cd /d c:\windows\syswow64
regsvr32 /s atl.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml6.dll
regsvr32 /s ole32.dll
regsvr32 /s spp.dll
regsvr32 /s vds_ps.dll
regsvr32 /s vss_ps.dll
pause

 

[carl a]

I did it but I still cannot create a restore point