Advertisement
Guest User

Command Prompt Log

a guest
Jun 17th, 2020
120
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.26 KB | None | 0 0
  1. Microsoft Windows [Version 10.0.18362.900]
  2. (c) 2019 Microsoft Corporation. All rights reserved.
  3.  
  4. C:\Windows\system32>sfc /scannow
  5.  
  6. Beginning system scan. This process will take some time.
  7.  
  8. Beginning verification phase of system scan.
  9. Verification 100% complete.
  10.  
  11. Windows Resource Protection found corrupt files and successfully repaired them.
  12. For online repairs, details are included in the CBS log file located at
  13. windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
  14. repairs, details are included in the log file provided by the /OFFLOGFILE flag.
  15.  
  16. C:\Windows\system32>dism /online /cleanup-image /scanhealth
  17.  
  18. Deployment Image Servicing and Management tool
  19. Version: 10.0.18362.900
  20.  
  21. Image Version: 10.0.18362.900
  22.  
  23. [==========================100.0%==========================] No component store corruption detected.
  24. The operation completed successfully.
  25.  
  26. C:\Windows\system32>dism /online /cleanup-image /restorehealth
  27.  
  28. Deployment Image Servicing and Management tool
  29. Version: 10.0.18362.900
  30.  
  31. Image Version: 10.0.18362.900
  32.  
  33. [==========================100.0%==========================] The restore operation completed successfully.
  34. The operation completed successfully.
  35.  
  36. C:\Windows\system32>sfc /scannow
  37.  
  38. Beginning system scan. This process will take some time.
  39.  
  40. Beginning verification phase of system scan.
  41. Verification 100% complete.
  42.  
  43. Windows Resource Protection did not find any integrity violations.
  44.  
  45. C:\Windows\system32>chkdsk /scan
  46. The type of the file system is NTFS.
  47. Volume label is Windows.
  48.  
  49. Stage 1: Examining basic file system structure ...
  50. 1504768 file records processed.
  51. File verification completed.
  52. 11207 large file records processed.
  53. 0 bad file records processed.
  54.  
  55. Stage 2: Examining file name linkage ...
  56. 9832 reparse records processed.
  57. 1853604 index entries processed.
  58. Index verification completed.
  59. 0 unindexed files scanned.
  60. 0 unindexed files recovered to lost and found.
  61. 9832 reparse records processed.
  62.  
  63. Stage 3: Examining security descriptors ...
  64. Security descriptor verification completed.
  65. 174419 data files processed.
  66. CHKDSK is verifying Usn Journal...
  67. 40109480 USN bytes processed.
  68. Usn Journal verification completed.
  69.  
  70. Windows has scanned the file system and found no problems.
  71. No further action is required.
  72.  
  73. 975668662 KB total disk space.
  74. 664534216 KB in 1243576 files.
  75. 465384 KB in 174420 indexes.
  76. 0 KB in bad sectors.
  77. 1646266 KB in use by the system.
  78. 65536 KB occupied by the log file.
  79. 309022796 KB available on disk.
  80.  
  81. 4096 bytes in each allocation unit.
  82. 243917165 total allocation units on disk.
  83. 77255699 allocation units available on disk.
  84.  
  85. C:\Windows\system32>bcdedit /enum all
  86. The boot configuration data store could not be opened.
  87. The requested system device cannot be found.
  88.  
  89. C:\Windows\system32>reagentc /info
  90. Windows Recovery Environment (Windows RE) and system reset configuration
  91. Information:
  92.  
  93. Windows RE status: Disabled
  94. Windows RE location:
  95. Boot Configuration Data (BCD) identifier: bd74a0c4-38d0-11ea-83c9-d0b38434667f
  96. Recovery image location:
  97. Recovery image index: 0
  98. Custom image location:
  99. Custom image index: 0
  100.  
  101. REAGENTC.EXE: Operation Successful.
  102.  
  103.  
  104. C:\Windows\system32>
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement