The V2 Log collector is triggering my antivirus

Thanks.
Working on #6-12.
#6 sfc /scannow picked some corrupt files it couldn't fix. I have put the CBS log in the same Dropbox folder as the memory dump, Dropbox - memory dump 08-01-19 - Simplify your life

Please use copy and paste for step #12.
If there are any problems please use a camera or smartphone camera to take a picture an post an image into the thread.

Read the instructions, finally. I do get to that eventually.
Microsoft Windows [Version 10.0.18362.267]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning 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 at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.267

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is Windows.

Stage 1: Examining basic file system structure ...
718080 file records processed.
File verification completed.
8120 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
1308 reparse records processed.
899410 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
1308 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
90666 data files processed.
CHKDSK is verifying Usn Journal...
34303200 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

933698657 KB total disk space.
778603324 KB in 454768 files.
291296 KB in 90667 indexes.
0 KB in bad sectors.
853813 KB in use by the system.
65536 KB occupied by the log file.
153950224 KB available on disk.

4096 bytes in each allocation unit.
233424664 total allocation units on disk.
38487556 allocation units available on disk.

C:\WINDOWS\system32> wmic recoveros set autoreboot = false
Updating property(s) of '\\BRUCES-HP-SPECT\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.

C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\WINDOWS\system32>

1) Open administrative command prompt and type or copy and paste:
2) dism /online /cleanup-image /scanhealth
3) dism /online /cleanup-image /restorehealth
4) sfc /scannow
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

6) Were you able to run HP support assistant > update drivers, software, BIOS

Re 5)

Microsoft Windows [Version 10.0.18362.267]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.267

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.267

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow

Beginning 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 at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\WINDOWS\system32>

Re 6) Earlier, HP Support Assistant did not want to update anything. I updated the BIOS afterward, manually - for some reason HP SA did not pick that up. I will go through the drivers on the HP site one by one. Most date to 2015.

- - - Updated - - -

Put a copy of the most recent CBS log in the memory dump Dropbox folder, if that's of any interest.

The are problems with windows defender that are causing scannow problems.
There are multiple Ten Forums threads on the problem.
These are typically hash mismatch.
Sometimes running restorehealth has fixed the problems.
On the computer it was not fixed and is unlikely to be fixed until there are windows defender or windows updates.

sfc /scannow found corrupted file that could not be corrected.
SFC scan found corrupt files and was unable to fix some of them.
SFC Reports Corruption Issues on all 4 of my PCs (after recent update)
SFC /scannow - Defender corruption?

Okay. So, the only path forward is what - do a clean installation of Windows?

The problem may reoccur after clean install.

Scannow compares protected files to files in the component store.

If these don't match and cannot be altered scannow displays corruption.

There were unrelated problems.

One was something that many end users have had or are having and that is scannow hash mismatch for Windows defender. See links in the earlier post.

Open administrative command prompt and copy and paste:
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt

Look on the desktop for a new text file > post a share link into the thread

The other was BSOD.

To fix the hash mismatch you can try an in place upgrade repair:
Repair Install Windows 10 with an In-place Upgrade

Many end users have to wait until Microsoft fixes the problem with a windows defender or windows update.