Error volsnap 36 all restore points deleted again!

G

glatzfront

Power User
All restore points are deleted when this occures!

Vista Ultimate 64, Volume size 40 GB, 13 GB free.

Error volsnap 36: The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit.

I just recently installed this OS and I haven't made any changes to the Shadow Copy settings.

Don't understand why all restore points are deleted when this happens?

Could someone please help?


Shadow Copy Storage association
For volume: (C:)\\?\Volume{ab704520-7dcd-11e0-8916-806e6f6e6963}\
Shadow Copy Storage volume: (C:)\\?\Volume{ab704520-7dcd-11e0-8916-806e6f6e6
63}\
Used Shadow Copy Storage space: 156.781 MB
Allocated Shadow Copy Storage space: 400 MB
Maximum Shadow Copy Storage space: 3.998 GB
 

My Computer

System One

You need a minimum amount of room for any points. Try my suggestion, if that does not work, we will try a clean boot to see if some software is deleting, this might be caused by other software, but I am ahead of myself.
 
Last edited:

My Computer

System One

  • Manufacturer/Model
    Dell XPS420
    Memory
    6 gig
    Graphics card(s)
    ATI Radeon HD3650 256 MB
    Sound Card
    Intergrated 7.1 Channel Audio
    Monitor(s) Displays
    Dell SP2009W 20 inch Flat Panel w Webcam
    Hard Drives
    640 gb
    Cooling
    Fan
    Mouse
    Dell USB 4 button optical
    Keyboard
    Dell USB
    Other Info
    DSL provided by ATT
Hello!

Your causes are explained here: Source: VolSnap Event ID: 36 (Windows Operating System 5.2.3790.1830) - Technet Events And Errors Message Center: Message Details

Microsoft said:
A disk I/O error occurred while performing the copy-on-write operation.
There is a bad block on the disk that contains the volume where the Diff Area is stored.
The Diff Area is not large enough to store the shadow copies.
The disk I/O or system load is so large that the Diff Area was not able increase in size fast enough.
Click to expand...
More specifically, and possibly easier to understand, from here: http://support.microsoft.com/kb/2528327

Microsoft said:
Event ID 36 on volsnap is being logged during the Service Pack upgrade because there was not enough disk space in the Diff Area for the Volume Shadow Service to take a snapshot. Due to the lack of disk space in the Diff area, the operating system automatically deleted the snapshot that was taken on Windows 7 RTM before the Service Pack finished installing to make room for the next snapshot that is attempted.

When installing a major servicing update such as a service pack, the operating system will attempt to create a snapshot of the current state for restore/rollback purposes. Due to the lack of disk space available in the Diff Area, the snapshot did not successfully complete and you will be unable to rollback to the RTM state.
Click to expand...
glatzfront said:
Maximum Shadow Copy Storage space: 3.998 GB
Click to expand...
This is so tiny that if there is a large change to the system, it will delete from the back, but it may actually have only space for one - the present one - which does not show up as a valid restore point until you have gone back in time and need a way to go forward again.

I don't know how big your hard disk is, but I will reiterate what @richc46 has said: http://www.vistax64.com/tutorials/76227-system-restore-disk-space.html

Richard
 

My Computer

System One

  • Manufacturer/Model
    Dell XPS 420
    CPU
    Intel Core 2 Quad Q9300 2.50GHz
    Motherboard
    Stock Dell 0TP406
    Memory
    4 gb (DDR2 800) 400MHz
    Graphics card(s)
    ATI Radeon HD 3870 (512 MBytes)
    Sound Card
    Onboard
    Monitor(s) Displays
    1 x Dell 2007FP and 1 x (old) Sonic flat screen
    Screen Resolution
    1600 x 1200 and 1280 x 1204
    Hard Drives
    1 x 640Gb (SATA 300) Western Digital: WDC WD6400AAKS-75A7B0 1 x 1Tb (SATA 600) Western Digital: Caviar Black, SATA 6GB/S, 64Mb cache, 8ms Western Digital: WDC WD1002FAEX-00Z3A0 ATA Device
    PSU
    Stock PSU - 375W
    Case
    Dell XPS 420
    Cooling
    Stock Fan
    Mouse
    Advent Optical ADE-WG01 (colour change light up)
    Keyboard
    Dell Bluetooth
    Internet Speed
    120 kb/s
    Other Info
    ASUS USB 3.0 5Gbps/SATA 6Gbps - PCI-Express Combo Controller Card (U3S6)
Changed to a maximum of 6 GB!


Used Shadow Copy Storage space: 1.005 GB
Allocated Shadow Copy Storage space: 1.481 GB
Maximum Shadow Copy Storage space: 6 GB
 

My Computer

System One

6/7/11 about 11PM, all restore points deleted again!

Error volsnap 36: The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit.

Vista has WMI errors and I wonder if this could be the problem? Errors etc. highlighted and spaced for easy read. Whole report available if needed.




27881 01:21:11 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 4 NAMESPACE(S)!
27882 01:21:11 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
27883 01:21:11 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTVOLUMEENCRYPTION.
27884 01:21:11 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
27885 01:21:11 (0) ** - ROOT/SERVICEMODEL.
27886 01:21:11 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
27887 01:21:11 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level.
27888 01:21:11 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
27889 01:21:11 (0) ** i.e. 'WMIC.EXE /NODE:"VISTULTP2-64" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
　
　
　
　
27893 01:21:11 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 10 ERROR(S)!
27894 01:21:11 (0) ** - Root/CIMV2, Win32_PerfFormattedData_NETCLRData_NETCLRData, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27895 01:21:11 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
27896 01:21:11 (0) ** - Root/CIMV2, Win32_PerfRawData_NETCLRData_NETCLRData, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27897 01:21:12 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
27898 01:21:12 (0) ** - Root/CIMV2, Win32_PerfFormattedData_NETCLRNetworking_NETCLRNetworking, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27899 01:21:12 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
27900 01:21:12 (0) ** - Root/CIMV2, Win32_PerfRawData_NETCLRNetworking_NETCLRNetworking, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27901 01:21:12 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
27902 01:21:12 (0) ** - Root/CIMV2, Win32_PerfFormattedData_NETDataProviderforOracle_NETDataProviderforOracle, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27903 01:21:12 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
27904 01:21:12 (0) ** - Root/CIMV2, Win32_PerfRawData_NETDataProviderforOracle_NETDataProviderforOracle, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27905 01:21:12 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
27906 01:21:12 (0) ** - Root/CIMV2, Win32_PerfFormattedData_NETDataProviderforSqlServer_NETDataProviderforSqlServer, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27907 01:21:12 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
27908 01:21:12 (0) ** - Root/CIMV2, Win32_PerfRawData_NETDataProviderforSqlServer_NETDataProviderforSqlServer, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27909 01:21:12 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
27910 01:21:12 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27911 01:21:12 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
27912 01:21:12 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
27913 01:21:12 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
27914 01:21:12 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
27915 01:21:12 (0) ** a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
27916 01:21:12 (0) ** You can refresh the WMI class provider buffer with the following command:
27917 01:21:12 (0) **
27918 01:21:12 (0) ** i.e. 'WINMGMT.EXE /SYNCPERF'
　
　
　
　
27942 01:21:12 (0) ** 10 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
27943 01:21:12 (0) ** => This error is typically a WMI error. This WMI error is due to:
27944 01:21:12 (0) ** - a missing WMI class definition or object.
27945 01:21:12 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
27946 01:21:12 (0) ** You can correct the missing class definitions by:
27947 01:21:12 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
27948 01:21:12 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
27949 01:21:12 (0) ** (This list can be built on a similar and working WMI Windows installation)
27950 01:21:12 (0) ** The following command line must be used:
27951 01:21:12 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
27952 01:21:12 (0) ** Note: When a WMI performance class is missing, you can manually resynchronize performance counters
27953 01:21:12 (0) ** with WMI by starting the ADAP process.
　
　
27954 01:21:12 (0) ** - a WMI repository corruption.
27955 01:21:12 (0) ** In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
27956 01:21:12 (0) ** to validate the WMI repository operations.
27957 01:21:12 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
27958 01:21:12 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use:
27959 01:21:12 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
27960 01:21:12 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
27961 01:21:12 (0) ** the WMI repository must be reconstructed.
27962 01:21:12 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
27963 01:21:12 (0) ** otherwise some applications may fail after the reconstruction.
27964 01:21:12 (0) ** This can be achieved with the following command:
27965 01:21:12 (0) ** i.e. 'WMIDiag ShowMOFErrors'
27966 01:21:12 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
27967 01:21:12 (0) ** ALL fixes previously mentioned.
27968 01:21:12 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
　
　
　
　
27976 01:21:12 (1) !! ERROR: Unable to locate MOF file(s) in the WBEM folder or in Auto-Recovery list for the
27977 01:21:12 (1) !! ERROR: following CIM registered WMI provider(s): .................................................................... 1 ERROR(S)!
27978 01:21:12 (0) ** - ROOT/SERVICEMODEL, SERVICEMODEL ()
27979 01:21:12 (0) ** => If the WMI repository is rebuilt, the listed provider(s) may not be available anymore
27980 01:21:12 (0) ** because the registration data is not located in the list of known MOF files. You can either:
27981 01:21:12 (0) ** - Locate the MOF file(s) and manually recompile the corresponding MOF file(s) with
27982 01:21:12 (0) ** the 'MOFCOMP.EXE <FileName.MOF>' command.
27983 01:21:12 (0) ** - Retrieve a copy of the missing MOF file(s) and make sure there are part of the Auto-Recovery.
27984 01:21:12 (0) ** registry key.
27985 01:21:12 (0) ** Note: If you want the MOF file to be part of the Auto-Recovery, make sure the
27986 01:21:12 (0) ** statement '#PRAGMA AUTORECOVER' is included.
27987 01:21:12 (0) ** - If the corresponding MOF file can't be located, the MOF file can be recreated with
27988 01:21:12 (0) ** WBEMTEST and/or CIM Studio available at
27989 01:21:12 (0) ** Download details: WMI Administrative Tools
27990 01:21:12 (0) ** - It is also possible that the application implemented its own recovery mechanism.
27991 01:21:12 (0) ** In that case, no action is required.
27992 01:21:12 (0) ** You must verify with the application vendor if the application has this capability (i.e. Microsoft SMS)
　
　

　
27995 01:21:12 (1) !! ERROR: MOF file(s) not containing the '#PRAGMA AUTORECOVER' statement: .............................................. 133 FILE(S)!
27996 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\TCPIP.MOF (*)
27997 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FUNDISC.MOF (*)
27998 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCSI.MOF (*)
27999 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NLASVC.MOF (*)
28000 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\L2GPSTORE.MOF (*)
28001 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\ONEX.MOF (*)
28002 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NETPROFM.MOF (*)
28003 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\LLTDIO.MOF (*)
28004 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\RSPNDR.MOF (*)
28005 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\DOT3.MOF (*)
28006 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\LLTDSVC.MOF (*)
28007 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NETWORKMAP.MOF (*)
28008 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NETWORKITEMFACTORY.MOF (*)
28009 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\MMC.MOF (*)
28010 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\MPSSVC.MOF (*)
28011 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\MPSDRV.MOF (*)
28012 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FIREWALLAPI.MOF (*)
28013 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WFAPIGP.MOF (*)
28014 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WININIT.MOF (*)
28015 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCHANNEL.MOF (*)
28016 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\RESTARTMANAGER.MOF (*)
28017 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\QMGR.MOF (*)
28018 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NEWDEV.MOF (*)
28019 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\BCD.MOF (*)
28020 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NTFS.MOF (*)
28021 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WDIGEST.MOF (*)
28022 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\DIMSJOB.MOF (*)
28023 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SERVICES.MOF (*)
28024 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SETUPAPI.MOF (*)
28025 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\DRVINST.MOF (*)
28026 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\UMPNPMGR.MOF (*)
28027 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WFP.MOF (*)
28028 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\IPSECSVC.MOF (*)
28029 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLSTORE.MOF (*)
28030 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WINIPSEC.MOF (*)
28031 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLFS.MOF (*)
28032 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\XWIZARDS.MOF (*)
28033 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\PRINTFILTERPIPELINESVC.MOF (*)
28034 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\MICROSOFT-WINDOWS-REMOTE-FILESYSTEM.MOF (*)
28035 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WHQLPROV.MOF (*)
28036 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WINLOGON.MOF (*)
28037 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WSCMISETUP.MOF (*)
28038 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\PNPSETUP.MOF (*)
28039 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMITIMEP.MOF (*)
28040 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CBSCORE.MOF (*)
28041 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SAPI.MOF (*)
28042 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\EAIMEAPI.MOF (*)
28043 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FILETRACE.MOF (*)
28044 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\IRDA.MOF (*)
28045 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\IRMON.MOF (*)
28046 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FDPHOST.MOF (*)
28047 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FDRESPUB.MOF (*)
28048 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\IPBUSENUM.MOF (*)
28049 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\UMB.MOF (*)
28050 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\UMBUS.MOF (*)
28051 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\UMPASS.MOF (*)
28052 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\PNPXASSOC.MOF (*)
28053 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\AUDIOCORE.MOF (*)
28054 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WINDOWSMOBILETRACING.MOF (*)
28055 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FWCFG.MOF (*)
28056 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\AUTHFWCFG.MOF (*)
28057 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FIREWALL.MOF (*)
28058 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\TSPKG.MOF (*)
28059 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\STORTRACE.MOF (*)
28060 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SDBUS.MOF (*)
28061 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WPD_CI.MOF (*)
28062 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\MSISCSI.MOF (*)
28063 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\MSFEEDS.MOF (*)
28064 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\MSFEEDSBS.MOF (*)
28065 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\DIMSROAM.MOF (*)
28066 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\RDPENCOM.MOF (*)
28067 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\IMAPIV2-BASE.MOF (*)
28068 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\IMAPIV2-FILESYSTEMSUPPORT.MOF (*)
28069 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\IMAPIV2-LEGACYSHIM.MOF (*)
28070 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WSMAUTO.MOF (*)
28071 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\AUXILIARYDISPLAYAPI.MOF (*)
28072 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FDWNET.MOF (*)
28073 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FDWSD.MOF (*)
28074 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FDSSDP.MOF (*)
28075 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NSHIPSEC.MOF (*)
28076 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\MICROSOFT-WINDOWS-OFFLINEFILES.MOF (*)
28077 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\INKOBJ.MOF (*)
28078 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\JOURNAL.MOF (*)
28079 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMP.MOF (*)
28080 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WFS.MOF (*)
28081 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WPC.MOF (*)
28082 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WINSAT.MOF (*)
28083 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\P2P-MESH.MOF (*)
28084 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\P2P-PNRP.MOF (*)
28085 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\P2P-COLLAB.MOF (*)
28086 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WZCDLG.MOF (*)
28087 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\AUXILIARYDISPLAYCPL.MOF (*)
28088 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\AUXILIARYDISPLAYSERVICES.MOF (*)
28089 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\P2P-CRP.MOF (*)
28090 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMPNETWK.MOF (*)
28091 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WCNWIZ.MOF (*)
28092 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WLAN.MOF (*)
28093 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WPDWCN.MOF (*)
28094 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SPEECHUX.MOF (*)
28095 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SPTIP.MOF (*)
28096 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\AUXILIARYDISPLAYDRIVERLIB.MOF (*)
28097 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WPDBUSENUM.MOF (*)
28098 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WPDFS.MOF (*)
28099 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\MBLCTR.MOF (*)
28100 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WCNCSVC.MOF (*)
28101 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FDWCN.MOF (*)
28102 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\P2P-MEETINGS.MOF (*)
28103 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\PORTABLEDEVICEWMDRM.MOF (*)
28104 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\TABSVC.MOF (*)
28105 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WPDSHEXT.MOF (*)
28106 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WPDSHSERVICEOBJ.MOF (*)
28107 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\PORTABLEDEVICEWIACOMPAT.MOF (*)
28108 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WPDSP.MOF (*)
28109 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WPDMTP.MOF (*)
28110 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\PORTABLEDEVICEAPI.MOF (*)
28111 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\PORTABLEDEVICETYPES.MOF (*)
28112 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\PORTABLEDEVICECLASSEXTENSION.MOF (*)
28113 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\MSWMDM.MOF (*)
28114 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\EN-US\SCRCONS.MFL (*)
28115 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\EN-US\SMTPCONS.MFL (*)
28116 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\EN-US\WBEMCONS.MFL (*)
28117 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\EN-US\WMITIMEP.MFL (*)
28118 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\EN-US\WHQLPROV.MFL (*)
28119 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SAMSRV.MOF (*)
28120 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\LSASRV.MOF (*)
28121 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SSTPSVC.MOF (*)
28122 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WCNWIZ2.MOF (*)
28123 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WSCEAPPR.MOF (*)
28124 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLFSUNINSTALL.MOF (DELETE) (*)
28125 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\ISCSIREM.MOF (DELETE) (*)
28126 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\RESTARTMANAGERUNINSTALL.MOF (DELETE) (*)
28127 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WIN32_ENCRYPTABLEVOLUMEUNINSTALL.MOF (DELETE) (*)
28128 01:21:12 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WINSATUNINSTALL.MOF (DELETE) (*)
28129 01:21:12 (0) ** => MOF file(s) marked with (*) are INCLUDED in the AUTO-RECOVERY LIST even if they do NOT contain the '#PRAGMA AUTORECOVER' statement.
28130 01:21:12 (0) ** If the WMI repository is rebuilt, the listed MOF files not included in the AUTO-RECOVERY LIST and
28131 01:21:12 (0) ** missing the '#PRAGMA AUTORECOVERY' statement when they are compiled the first time will NOT
28132 01:21:12 (0) ** be recompiled during the repository reconstruction.
28133 01:21:12 (0) ** Note: If you want the MOF file to be part of the AUTO-RECOVERY LIST, make sure the statement '#PRAGMA AUTORECOVER'
28134 01:21:12 (0) ** is included and recompile the MOF/MFL with the following command:
28135 01:21:12 (0) ** i.e. 'MOFCOMP.EXE <FileName.MOF>'
28136 01:21:12 (0) **
28137 01:21:12 (0) ** => MOF file(s) marked with (DELETE) contains class and instance DELETE statements.
28138 01:21:12 (0) ** Usually, MOF with DELETE statements are used to UNinstall components and they should NOT be listed in the AUTORECOVERY LIST
28139 01:21:12 (0) ** and therefore they should NOT specify the '#PRAGMA AUTORECOVER' statement.
28140 01:21:12 (0) ** Note: It happens that some MOF files do contain DELETE statements for installation purposes to delete
28141 01:21:12 (0) ** existing information before it is recreated.
28142 01:21:12 (0) **
28143 01:21:12 (0) ** Note: It is also possible that the application implemented its own recovery mechanism.
28144 01:21:12 (0) ** In that case, no action is required. You must verify with the application vendor
28145 01:21:12 (0) ** if the application has this capability (i.e. Microsoft SMS)
 

My Computer

System One

You must log in or register to reply here.
Back
Top