Windows 10: Is My Windows 10 Corrupt - Settings Not Being Saved And Possibly More

In the post there were many reports listed so that you could read the findings.
There is corruption of the drive file system.
There is corruption involving Avast.
On computers there should only be one always on antivirus product as the antivirus products can compete with each other making the computer vulnerable to malware.
All AV products use drivers.
Drivers misbehave and cause BSOD. The BSOD are to protect the computer and they need to be troubleshooted.
There was a BSOD just a day before the post and you may not be seeing them due to the computer settings.

If a car drives well for 5 years and then all of a sudden needs a new engine, chassis, transmission etc one may wonder what could have happened if there was better preventative maintenance?
In a similar fashion a friend could be hospitalized and one may wonder what could have been done if there was better preventative care.
Apply this to the computer.
You can continue to use this computer and disregard the findings or you could act upon them.
At some point there will be a decrease in performance and then there will be boot problems. Then there may be anxiety or distress until the problems are fixed.


The troubleshooting steps are organized to:
1) check the windows operating system
2) improve the computer performance
3) find the source(s) of the BSOD and fix the underlying problem
4) backup the files on the computer so that you have safety in case there is boot failure, operating system or registry corruption, malware, etc
5) improve the settings so you get a warning or earlier warning for some computer problems
6) prevent the loss of files that are needed for troubleshooting
7) evaluate the hardware that may be related to the current problems ( drive file system corruption and BSOD)



So it takes time and effort to perform the preventative steps. And you now know there are problems. The problems are likely to turn into bigger problems if they are not addressed in a timely fashion.

The steps were posted in a comprehensive fashion.
You can take your time to complete the steps.
Some of the steps can be done overnight.

These are the steps that can be done while sleeping:
1) chkdsk /x /f /r
2) HD Tune full error scan
3) Memtest86+ version 5.01

 

Ok, thanks. I'll get started tonight and do the best I can.

 

So I filled out the Computer specs as best I could for now. There were some things that I just couldn't get to at the moment. If you absolutely need some of these things I'll get 'em, but I just couldn't take apart the computer tonight.

As for the BIOS. What you wrote looks to be correct. I was informed about version 3.5.2 on February 6th by Dells support pop up. By the way, as of 5 minutes ago I couldn't even find half the things for my computer specs, and then I brought up Dell's Support Assist app - and damn if that thing doesn't have everything listed and handy! There's also something called a Chipset update where the BIOS info was (Intel AMT HECI ME Driver). Obviously, I'm not sure what that is. I can look it up tomorrow. It's getting late, and updating the BIOS and possibly driver scares me a little, so I don't want to tackle that one tonight.

Here are the logs from the first round:

C:\Users\CT\Desktop>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Users\CT\Desktop>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.16299.15

Image Version: 10.0.16299.125

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

C:\Users\CT\Desktop>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.16299.15

Image Version: 10.0.16299.125

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

C:\Users\CT\Desktop>

 

The above commands and results displayed that the operating system is ok and this was expected.

These are preventative maintenance commands that can be run as much as you want to check the integrity of and repair the operating system.

Once the drive file system is repaired there will be another command that you can use as much as you want to check the integrity of the drive file system.

 

Tonight I'll update the BIOS. It doesn't seem that by doing that you lose anything in terms of files, programs, music, etc - is that correct? It just says that things will be set back to factory default, but only if you've changed things in the BIOS, which I don't "think" I ever have. I mean, I know I've never entered the BIOS.

As far as #16 goes, I'm not really sure what that is. Does that have anything to do with the Chipset Update - Intel AMT HECI ME Driver? If so I can do that too. But if #16 is something different then I'm not to sure. The Chipset update was the other update, along with the BIOS update that the Dell System Update App was telling me to do. I looked at the detailed report about it, but it was a little too generic for me to understand what exactly it was, or did.

Continued thanks.

 

Step # 16 is for you to enter the product or serial number and display the drivers and BIOS.
This produces the reference for the computer. (URL or hyperlink)
All viewers will be able to see the computer manufacturer supported drivers and BIOS for the computer.

All drivers/firmware should be up to date and come directly from the computer manufacturer.

Resetting the BIOS will ensure that there are no improper settings.
There should be no loss of files.
Sometimes though there are unexpected results.
So for prevention you are to backup all files to another drive or to the cloud and to make a backup image using Macrium:
Macrium Software | Macrium Reflect Free

 

Ok, so I won't be able to do this tonight then, I'm gonna have to figure out what I need to back up first. It may take me through the weekend but I will do it.

 

These are the steps that can be done any evening/night:
1) chkdsk /x /f /r
2) HD Tune full error scan
3) Memtest86+ version 5.01

 

Oh ok, got it. Can I use Hard Drive Sentinel instead? I've never used it for a full error scan, but it's already on my computer because I use it to monitor the health of my HD's.

 

Yes.
1) Run HD Sentinel: (free or trial edition)
Hard Disk Sentinel - HDD health and temperature monitoring
Hard Disk Sentinel - HDD health and temperature monitoring
a) click disk > surface test > post image into the thread
(this may take several hours to complete)
b) Post images of each of these tabs into the thread:
Overview tab
Temperature
SMART
Disk performance


Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10 Windows 10 Tutorials

In case the edition of HD Sentinel does not have any of the tests available for the free or trial edition please use HD Tune to complete the tests. For HD Sentinel surface scan = HD Tune error scan

 

Cool, thanks. I'll do one of these steps tonight.

 

Not sure I did this one right - the date says it was created on March 6th for some reason?

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\Users\CT> get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} |
fl timecreated, message


TimeCreated : 3/6/2018 12:26:29 PM
Message :

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
The attribute of type 0x80 and instance tag 0x0 in file 0x1e6
has allocated length of 0x710000 instead of 0x990000.
The total allocated size 0x201000 of attribute of type 0x80 and instance
tag 0x0 in file 0x1e6 is incorrect. The expected value is 280000.
Correcting total allocated size in attribute record (80, "")
of file 30000000001E6.
Deleted corrupt attribute list entry
with type code 80 in file 1E6.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x290000000038fc. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x38FC.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x2000000005d85. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x5D85.
Deleted corrupt attribute list entry
with type code 80 in file 21A.
Unable to find child frs 0x184 with sequence number 0x70.
The attributes with same type code 0x80 but different instance tags
0x0 and 0x0 have non-contiguous VCN numbers 0xb020 and 0xf32b
respectively in file 0x21a.
Deleted corrupt attribute list entry
with type code 80 in file 21A.
Unable to locate attribute with instance tag 0x0 and segment
reference 0xbb0000000000f1. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0xF1.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x156000000000217. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x217.
Unable to locate attribute with instance tag 0x0 and segment
reference 0xfe2000000000237. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x237.
Deleted corrupt attribute list entry
with type code 80 in file 281.
Unable to find child frs 0x207 with sequence number 0x77.
Attribute record of type 0x80 and instance tag 0x0 is cross linked
starting at 0x1c963 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x0
in file 0x3c4 is already in use.
The attribute of type 0x80 and instance tag 0x0 in file 0x3c4
has allocated length of 0x43b36000 instead of 0x82a0000.
Deleted corrupt attribute list entry
with type code 80 in file 3C4.
Unable to locate attribute with instance tag 0x0 and segment
reference 0xa1000000000603. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x603.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x270000000000794. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x794.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x1750000000008e2. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x8E2.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x84000000004617. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x4617.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x3b0000000053f7. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x53F7.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x450000000066a9. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x66A9.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x170000000066b5. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x66B5.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x620000000066b6. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x66B6.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x180000000066b7. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x66B7.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x47000000006748. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x6748.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x4d000000006760. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x6760.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x92000000006763. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x6763.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x1d000000006765. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x6765.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x19000000006768. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x6768.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x8a8b9e for possibly 0x1a0 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0xf92 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0xF92.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x1d7656 for possibly 0x19 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x235e is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x235E.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x8a9bc3 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x8204 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x8204.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x8a9bc4 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x8207 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x8207.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x1a6ac for possibly 0xa clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0xb26f is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0xB26F.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x85 with sequence number 0x72.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x342 with sequence number 0x150.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x347 with sequence number 0xb0.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x349 with sequence number 0x58.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x34a with sequence number 0x1c.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x362 with sequence number 0x232.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x365 with sequence number 0xc0.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x368 with sequence number 0x66.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x369 with sequence number 0x4d.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x36c with sequence number 0xb9.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x370 with sequence number 0x3e.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x372 with sequence number 0x123.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x373 with sequence number 0x14f.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x378 with sequence number 0x18.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x38d with sequence number 0x3f.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x390 with sequence number 0x211.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x392 with sequence number 0x43.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x398 with sequence number 0x55.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3a1 with sequence number 0x65.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3a9 with sequence number 0x167.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3b8 with sequence number 0x158.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3ba with sequence number 0x9f.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3c3 with sequence number 0x1ba.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3c6 with sequence number 0xc8.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3d1 with sequence number 0x6.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3d3 with sequence number 0x5.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3d4 with sequence number 0x5.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3d6 with sequence number 0x5.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3d7 with sequence number 0x5.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3e6 with sequence number 0x128.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3eb with sequence number 0x35.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3ee with sequence number 0x1df.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3ef with sequence number 0x4c.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3f0 with sequence number 0x6bc.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3f1 with sequence number 0x142.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3f5 with sequence number 0xd4.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3f8 with sequence number 0x86.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3f9 with sequence number 0xd8.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3fa with sequence number 0x142.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x3fc with sequence number 0x141.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x40c with sequence number 0x11f.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x40d with sequence number 0x9c.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x40f with sequence number 0x5b.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x418 with sequence number 0x133.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x419 with sequence number 0x202.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x41a with sequence number 0x54.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x41f with sequence number 0x152.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x420 with sequence number 0x4b.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x422 with sequence number 0x58.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x423 with sequence number 0x38.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x425 with sequence number 0xd1.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x427 with sequence number 0x20f.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x428 with sequence number 0xfc.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x42a with sequence number 0x104.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x42b with sequence number 0xac.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x42f with sequence number 0x8a.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x431 with sequence number 0x116.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x433 with sequence number 0x58.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x434 with sequence number 0x29.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x448 with sequence number 0xc4.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x44d with sequence number 0x189.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x451 with sequence number 0x13e.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x453 with sequence number 0xfb.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x45a with sequence number 0x4b.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x45b with sequence number 0x8f.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x460 with sequence number 0x96.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x466 with sequence number 0x15c.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x467 with sequence number 0x129.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x472 with sequence number 0xbd.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x478 with sequence number 0x6a.
Deleted corrupt attribute list entry
with type code 80 in file D083.
Unable to find child frs 0x479 with sequence nu

get-winevent : The event log file is corrupted
At line:1 char:1
+ get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (*Smile [Get-WinEvent], EventLogException
+ FullyQualifiedErrorId : The event log file is corrupted,Microsoft.PowerShell.Commands.GetWinEventCommand

get-winevent : The event log file is corrupted
At line:1 char:1
+ get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (*Smile [Get-WinEvent], EventLogException
+ FullyQualifiedErrorId : The event log file is corrupted,Microsoft.PowerShell.Commands.GetWinEventCommand

get-winevent : The event log file is corrupted
At line:1 char:1
+ get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (*Smile [Get-WinEvent], EventLogException
+ FullyQualifiedErrorId : The event log file is corrupted,Microsoft.PowerShell.Commands.GetWinEventCommand

 

The event logs had reported drive file system corruption.
There were many repairs within the event logs and there were so many that the windows operating system blocked repairs.
The corruption was confirmed in the chkdsk report.
Please repeat the command:

Open administrative command prompt and type or copy and paste: chkdsk /x /f /r
This may take many hours.

C:\Windows\system32>chkdsk /x /f /r
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot

Find the chkdsk report in the event viewer using the information in this link. Copy > paste notepad > save to desktop > post into the thread.
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Tutorials

 

As mentioned HDsentinal for HDD health report. SSDLife for SSD health report.
----------------------------------------------------------------------------------------------------------

Sounds like a registry or permission issue which is not allowing you to save settings.

Enable the internal administrator account:

CMD> Net user Administrator /active:yes


Logout, and log in to the new account and see if you can replicate the error.

If error persists, then the issue is OS wide. If not, its localised to the User Profile.

-----------------------------------------------------------------------------------------------------------

I would do this in the exact order:

sfc /verfifyonly (will take some time and verify files for corruption etc)
sfc /scannow (will attempt to fix any corruptioption) (If SFC find but can not repair files then move to the DISM steps, these will find and usually fix Component Store Corruption, which SFC relies on to compare and replace files)

DISM /online /cleanup-image /scanhealth (will scan OS health etc)

DISM /online /cleanup-image /checkhealth (should return same end messages as /scanhealth, if there were any messages)

DISM /online /cleanup-image /repairhealth

 

Here's HD Tune so far:









I'll do the full error scan overnight.