Code:
Windows PowerShellCopyright (C) Microsoft Corporation. All rights reserved.PS C:\WINDOWS\system32> sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection found corrupt files but was unable to fix some of them.For online repairs, details are included in the CBS log file located atwindir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offlinerepairs, details are included in the log file provided by the /OFFLOGFILE flag.PS C:\WINDOWS\system32> dism /online /cleanup-image /scanhealthDeployment Image Servicing and Management toolVersion: 10.0.17763.771Image Version: 10.0.17763.914[==========================100.0%==========================] The component store is repairable.The operation completed successfully.PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.17763.771Image Version: 10.0.17763.914[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.PS C:\WINDOWS\system32> sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection found corrupt files and successfully repaired them.For online repairs, details are included in the CBS log file located atwindir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offlinerepairs, details are included in the log file provided by the /OFFLOGFILE flag.PS C:\WINDOWS\system32> chkdsk /scanThe type of the file system is NTFS.Volume label is Windows 10 (New).Stage 1: Examining basic file system structure ... 731392 file records processed.File verification completed. 17541 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 974 reparse records processed. 947082 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 974 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 107846 data files processed.CHKDSK is verifying Usn Journal... 36670632 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 494836735 KB total disk space. 246421420 KB in 557382 files. 225920 KB in 107847 indexes. 0 KB in bad sectors. 860003 KB in use by the system. 65536 KB occupied by the log file. 247329392 KB available on disk. 4096 bytes in each allocation unit. 123709183 total allocation units on disk. 61832348 allocation units available on disk.PS C:\WINDOWS\system32> wmic recoveros set autoreboot = falseUpdating property(s) of '\\DESKTOP-4U75PB9\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'Property(s) update successful.PS C:\WINDOWS\system32> wmic recoveros set DebuginfoType = 7Updating property(s) of '\\DESKTOP-4U75PB9\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'Property(s) update successful.PS C:\WINDOWS\system32> bcedit /enum {badmemory}bcedit : The term 'bcedit' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spellingof the name, or if a path was included, verify that the path is correct and try again.At line:1 char:1+ bcedit /enum {badmemory}+ ~~~~~~ + CategoryInfo : ObjectNotFound: (bcedit:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundExceptionPS C:\WINDOWS\system32> bcdedit /enum {badmemory}Invalid command line switch: /encodedCommandRun "bcdedit /?" for command line assistance.The parameter is incorrect.PS C:\WINDOWS\system32> bcdedit /?BCDEDIT - Boot Configuration Data Store EditorThe Bcdedit.exe command-line tool modifies the boot configuration data store.The boot configuration data store contains boot configuration parameters andcontrols how the operating system is booted. These parameters were previouslyin the Boot.ini file (in BIOS-based operating systems) or in the nonvolatileRAM entries (in Extensible Firmware Interface-based operating systems). You canuse Bcdedit.exe to add, delete, edit, and append entries in the bootconfiguration data store.For detailed command and option information, type bcdedit.exe /? <command>. Forexample, to display detailed information about the /createstore command, type: bcdedit.exe /? /createstoreFor an alphabetical list of topics in this help file, run "bcdedit /? TOPICS".Commands that operate on a store================================/store Used to specify a BCD store other than the current system default./createstore Creates a new and empty boot configuration data store./export Exports the contents of the system store to a file. This file can be used later to restore the state of the system store./import Restores the state of the system store using a backup file created with the /export command./sysstore Sets the system store device (only affects EFI systems, does not persist across reboots, and is only used in cases where the system store device is ambiguous).Commands that operate on entries in a store===========================================/copy Makes copies of entries in the store./create Creates new entries in the store./delete Deletes entries from the store./mirror Creates mirror of entries in the store.Run bcdedit /? ID for information about identifiers used by these commands.Commands that operate on entry options======================================/deletevalue Deletes entry options from the store./set Sets entry option values in the store.Run bcdedit /? TYPES for a list of datatypes used by these commands.Run bcdedit /? FORMATS for a list of valid data formats.Commands that control output============================/enum Lists entries in the store./v Command-line option that displays entry identifiers in full, rather than using names for well-known identifiers. Use /v by itself as a command to display entry identifiers in full for the ACTIVE type.Running "bcdedit" by itself is equivalent to running "bcdedit /enum ACTIVE".Commands that control the boot manager======================================/bootsequence Sets the one-time boot sequence for the boot manager./default Sets the default entry that the boot manager will use./displayorder Sets the order in which the boot manager displays the multiboot menu./timeout Sets the boot manager time-out value./toolsdisplayorder Sets the order in which the boot manager displays the tools menu.Commands that control Emergency Management Services for a boot application==========================================================================/bootems Enables or disables Emergency Management Services for a boot application./ems Enables or disables Emergency Management Services for an operating system entry./emssettings Sets the global Emergency Management Services parameters.Command that control debugging==============================/bootdebug Enables or disables boot debugging for a boot application./dbgsettings Sets the global debugger parameters./debug Enables or disables kernel debugging for an operating system entry./hypervisorsettings Sets the hypervisor parameters.Command that control remote event logging=========================================/eventsettings Sets the global remote event logging parameters./event Enables or disables remote event logging for an operating system entry.PS C:\WINDOWS\system32> bcdedit /enumWindows Boot Manager--------------------identifier {bootmgr}device partition=\Device\HarddiskVolume1description Windows Boot Managerlocale en-USinherit {globalsettings}default {current}resumeobject {955e0ea8-4df1-11e9-b18b-d368b3f0aba4}displayorder {current} {bf40ef42-2734-11e8-ab4c-5cf370816163} {b2ce5c0a-e12a-11e7-ab00-5cf370816163}toolsdisplayorder {memdiag}timeout 10Windows Boot Loader-------------------identifier {current}device partition=C:path \WINDOWS\system32\winload.exedescription Windows 10locale en-USinherit {bootloadersettings}recoverysequence {226512ab-4dd0-11e9-ba98-a5ee2ac7ac9b}displaymessageoverride Recoveryrecoveryenabled Yesallowedinmemorysettings 0x15000075osdevice partition=C:systemroot \WINDOWSresumeobject {955e0ea8-4df1-11e9-b18b-d368b3f0aba4}nx OptInbootmenupolicy StandardWindows Boot Loader-------------------identifier {bf40ef42-2734-11e8-ab4c-5cf370816163}device partition=G:path \WINDOWS\system32\winload.exedescription Windows 10 Pro Oldlocale en-USinherit {bootloadersettings}recoverysequence {4999b38e-2757-11e8-a500-deb0a618abd2}displaymessageoverride Recoveryrecoveryenabled Yesallowedinmemorysettings 0x15000075osdevice partition=G:systemroot \WINDOWSresumeobject {bf40ef41-2734-11e8-ab4c-5cf370816163}nx OptInbootmenupolicy StandardWindows Boot Loader-------------------identifier {b2ce5c0a-e12a-11e7-ab00-5cf370816163}device ramdisk=[G:]\boot\macrium\WA10KFiles\media\sources\boot.wim,{ramdiskoptions}path \windows\system32\boot\winload.exedescription Macrium Reflect System Recoveryosdevice ramdisk=[G:]\boot\macrium\WA10KFiles\media\sources\boot.wim,{ramdiskoptions}systemroot \Windowsbootmenupolicy Standarddetecthal Yeswinpe YesPS C:\WINDOWS\system32>
- - - Updated - - -
Not clear on the below response - but I think we can get back to that later. Guess I need specific instructions on what to do at each of the three sites you list in this attachment. Thank you.
There are multiple forum rooms in TF.
The BSOD forum room uses log collectors.
Files are then scanned so significant problems can be troubleshooted.
Quote