Microsoft Office 16 Regid.1991-06.com Errors with the Click-to-Run Licensing Component.swidtag file is most common during the startup phase of Microsoft Project Professional 2016 (64-Bit). However, they can also happen while the application is running.
This error occurs when Microsoft Project Professional 2016 (64-Bit) is operating, these SWIDTAG issues are also known as “runtime errors.”
If you are facing the same error on your computer, then don’t worry, we have provided some of the best solutions to fix this error in this article. So, follow this guide till the end carefully to fix the issue on your computer.
Reasons Why the Regid 1991 06 Com Microsoft Error Occur
There are various regid.1991-06.com.microsoft Office errors that can occur due to different reasons.
Here are the most common reasons why the most typical runtime problems in regid.1991-06.com.microsoft Office 16 Click-to-Run Licensing Component.swidtag:
- If the Component.swidtag file is corrupted.
- If the Component.swidtag file is removed by mistake or erased by malware.
- If the regid.1991 is failed to register.
- If the Component.swidtag file failed to load.
- If A power outage or a system crash occurs when loading Microsoft Project Professional 2016 (64-Bit) or saving Component.swidtag file.
- Malware infestation or damaged sectors on your storage medium (typically your primary hard drive) can also trigger this error.
- If the Windows Operating System is out dated.
How to Troubleshoot ‘Regid 1991 06 Com Microsoft’ Issue
The troubleshooting methods are described in the order in which they should be performed. This means you need to start with Method 1 and apply the methods one by one in order to fix the Microsoft Office 16 91-06.com.microsoft.com error.
Method 1: Perform System Restore
First, restore your computer to the most recent restore point, “snapshot,” or backup image that was taken before the issue.
To start the System Restore process, follow these steps below:
Step 1: Press the Windows Start button. When the search box appears, type “System Restore” and select “Recovery”.
Step 2: Find and click Open System Restore in the following window. Please provide the administrator password (if asked) if one is required.
Step 3: To pick an appropriate restore point, go through the procedures in the System Restore Wizard.
Step 4: Use that backup image to restore your machine.
Method 2: Reinstall Microsoft Project Professional 2016 (64-Bit) Software
Uninstall Microsoft Project Professional 2016 (64-Bit) (or similar software) if it was recently installed, and then reinstall Microsoft Project Professional 2016 (64-Bit) software.
Follow these steps to remove Microsoft Project Professional 2016 (64-Bit) program (Windows XP, Vista, 7, 8, and 10):
Step 1: Right-click on the Windows icon and select “Apps and Features” in the WinX menu.
Step 2: Find the ‘Microsoft Project Professional 2016’ in the list of installed app and click on it.
Step 3: Click “Uninstall” underneath the Microsoft Project Professional 2016 (64-Bit) 2016 and uninstall it by following the on-screen instructions.
Step 4: Restart your PC and reinstall Microsoft Project Professional 2016 (64-Bit) program when the software has been completely removed.
Method 3: Update Windows
If the previous two methods haven’t resolved your problem, you might want to try running Windows Update. Please follow these simple instructions to launch Windows Update:
Step 1: Press the Windows Start button and click ‘Settings’ (Gear icon).
Step 2: Click “Update & Security”.
Step 3: Click “Check for Updates” in the Windows Update dialog box (or similar button depending on your Windows version).
Step 4: Click “Install Updates” if updates are available for download.
Step 5: Restart your computer after the update is complete.
Frequently Asked Questions
What Is a swidtag File?
Swidtag file contains data about a specific release of a software product. This file is necessary while the installation or uninstall process of that software. If this file is missing, you may face error messages.
How to Uninstall Office 16 Click to Run Extensibility Component in Windows 11?
To uninstall Office 16 Click-to-Run Extensibility Component 64-bit Registration, open the Run window by pressing Win + R, type “installer” and click OK. Then add the column “Subject”. Right-click the column headers, then click More and select Subject. Sort on the Subject column and scroll down until you locate the name “Office 16 Click-to-Run Extensibility Component 64-bit Registration”. Right-click the MSI file and choose to uninstall.
How to Uninstall Office 2016 Using Command Prompt or PowerShell?
To uninstall Office 2016 using PowerShell, right-click Start. and select Windows PowerShell (Admin). In the Windows PowerShell window, type the command below–
Get-AppxPackage -name “Microsoft.Office.Desktop” | Remove-AppxPackage
Finally, press Enter to uninstall the software.
Do I Have to Uninstall Office 2016 Before Installing 2021?
Yes, you have to uninstall office 2016 before installing 2021. The fact is you have to uninstall any previous versions of Microsoft Office if you are upgrading it to the latest version. If you don’t uninstall the previous version, then both software will remain on your computer, will conflict with each other and end up facing several errors.
Conclusion
It provides details on the “Microsoft Office 16 Regid.1991-06.com” error as well as troubleshooting advice for attempting to fix them. I hope you find this information helpful on fixing this issue after reading this guide. Do you have any particular issues right now? Don’t hesitate to tell us in the comment section below.
Last Updated: 11/26/2024
[Time to Read: ~3-5 minutes]
regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag, also known as a SWID Tag Data file, was created by Microsoft for the development of Windows 10. SWIDTAG files fall under under the XML (SWID Tag Data) file type category.
The first version of regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag was released for the Windows 10 Operating System on 07/29/2015 inside Windows 10.
According to our records, this is the primary and most recent file release from Microsoft.
Continue reading below to discover detailed file information, SWIDTAG file troubleshooting, and free downloads of several versions of regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag.
What are regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag Error Messages?
General regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag Runtime Errors
regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag file errors often occur during the startup phase of Windows, but can also occur while the program is running.
These types SWIDTAG errors are also known as “runtime errors” because they occur while Windows is running. Here are some of the most common regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag runtime errors:
- regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag could not be found.
- regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag error.
- regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag failed to load.
- Error loading regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag.
- Failed to register regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag / Cannot register regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag.
- Runtime Error — regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag.
- The file regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag is missing or corrupt.
Microsoft Visual C++ Runtime Library
Runtime Error!
Program: C:\ProgramData\regid.1991-06.com.microsoft\regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application’s support team for more information.
Most SWIDTAG errors are due to missing or corrupt files. Your regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag file could be missing due to accidental deletion, uninstalled as a shared file of another program (shared with Windows), or deleted by a malware infection. Furthermore, regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag file corruption could be caused from a power outage when loading Windows, system crash while loading or saving regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag, bad sectors on your storage media (usually your primary hard drive), or malware infection. Thus, it’s critical to make sure your anti-virus is kept up-to-date and scanning regularly.
How to Fix regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag Errors in 3 Steps (Time to complete: ~5-15 minutes)
If you’re encountering one of the error messages above, follow these troubleshooting steps to resolve your regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag issue. These troubleshooting steps are listed in the recommended order of execution.
Step 1: Restore your PC back to the latest restore point, «snapshot», or backup image before error occurred.
To begin System Restore (Windows XP, Vista, 7, 8, and 10):
- Hit the Windows Start button
- When you see the search box, type «System Restore» and press «ENTER«.
- In the search results, find and click System Restore.
- Please enter the administrator password (if applicable / prompted).
- Follow the steps in the System Restore Wizard to choose a relevant restore point.
- Restore your computer to that backup image.
If the Step 1 fails to resolve the regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag error, please proceed to the Step 2 below.
Step 2: Run SFC (System File Checker) to restore the corrupt or missing regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag file.
System File Checker is a utility included with every Windows version that allows you scan and restore corrupted system files. Use the SFC tool to fix missing or corrupt regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag files (Windows XP, Vista, 7, 8, and 10):
- Hit the Windows Start button
- In the search box, type «cmd» but DO NOT PRESS «ENTER».
- Press and hold «CTRL-Shift» on your keyboard while pressing «ENTER«.
- You’ll be prompted with a permission dialog box.
- In the box, click «YES«.
- You should have a black screen with a blinking cursor.
- In that black screen, type «sfc /scannow» and hit «ENTER«.
- SFC will begin scanning for regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag issues and any other system file problems.
- Follow any on-screen commands to complete the process.
Please be aware that this scan might take a while, so please be patient while it is working.
If this Step 2 fails as well, please proceed to the Step 3 below.
Step 3: Perform a Windows Update.
When the first two steps haven’t solved your issue, it might be a good idea to run Windows Update. Many regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag error messages that are encountered can be contributed to an outdated Windows Operating System. To run Windows Update, please follow these easy steps:
- Hit the Windows Start button
- In the search box, type «Update» and press «ENTER«.
- In the Windows Update dialog box, click «Check for Updates» (or similar button depending on your Windows version)
- If updates are available for download, click «Install Updates«.
- After the update is completed, restart your PC.
If Windows Update failed to resolve the regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag error message, please proceed to next step. Please note that this final step is recommended for advanced PC users only.
If Those Steps Fail: Download and Replace Your regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag File (Caution: Advanced)
If none of the previous three troubleshooting steps have resolved your issue, you can try a more aggressive approach (Note: Not recommended for amateur PC users) by downloading and replacing your appropriate regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag file version. We maintain a comprehensive database of 100% malware-free regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag files for every applicable version of Windows. Please follow the steps below to download and properly replace you file:
- Locate your Windows operating system version in the list of below «Download regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag Files».
- Click the appropriate «Download Now» button and download your Windows file version.
- Copy the file into the appropriate directory for your Windows version:
- Restart your computer.
Windows 10: C:\ProgramData\regid.1991-06.com.microsoft\
If this final step has failed and you’re still encountering the error, you’re only remaining option is to do a clean installation of Windows 10.
GEEK TIP : We must emphasize that reinstalling Windows will be a very time-consuming and advanced task to resolve regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag problems. To avoid data loss, you must be sure that you have backed-up all of your important documents, pictures, software installers, and other personal data before beginning the process. If you are not currently backing up your data, you need to do so immediately.
Download regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag Files (Malware-Tested 100% Clean)
CAUTION : We strongly advise against downloading and copying regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag to your appropriate Windows system directory. Microsoft typically does not release Windows SWIDTAG files for download because they are bundled together inside of a software installer. The installer’s task is to ensure that all correct verifications have been made before installing and placing regid.1991-06.com.microsoft_Windows-10-Enterprise.swidtag and all other SWIDTAG files for Windows. An incorrectly installed SWIDTAG file may create system instability and could cause your program or operating system to stop functioning altogether. Proceed with caution.
You are downloading trial software. The purchase of a one-year software subscription at the price of $29.97 USD is required to unlock all software features. Subscription auto-renews at the end of the term (Learn more). By clicking the «Start Download» button above and installing «Software», I acknowledge I have read and agree to the Solvusoft End User License Agreement and Privacy Policy.
Regid.1991-06.Com.Microsoft .
Windows 10 Pro offers more advanced security and business networking features, including: BitLocker Drive Encryption. Remote Desktop. The ability to join a domain or Azure Active Directory. If you#39;re running Windows 10 Home, select Get Windows 10 Pro to upgrade your device. Get Windows 10 Pro. May 24, 2014 Hallo, habe jetzt Windows 8.1 auf meinem Spiel Rechner installiert. Unter C:#92;ProgramData befindet sich folgender Ordner: In dem Ordner enthalten ist diese Datei: regid.
How to Download and Repair R.
SWIDTAG files are used by a variety of programs including the Microsoft Office and Adobe Creative Cloud applications. The SWIDTAG files are created after installation and placed in a registration id folder such as quot;; for Adobe CC and quot;; for MS Office, that is located in the application data. Donaldysmith Created on November 22, 2022 How to delete in Windows.Old folder? My pc was upgraded from Windows 10 to. ? C:#92;ProgramData 3 Office 15 Click-to-Run Extensibility Component.swidtag Office 15 Click-to-Run Licensing Component.swidtag.
What Is Regid.1991-06.Com.Microsoft and Can You.
Jan 15, 2020 How to Add #39;Empty Recycle Bin Context Menu#39; in Windows 10 amp; 11 How to Enable Enhanced Protection in Google Chrome… What Is Regid.1991-06.Com.Microsoft and Can. It was titled #39;;, and it contained a file named #39; Windows-10-Home-Single-Language.swidtag#39;. When I googled the file extension, I receive mixed results. Some websites are calling it a virus while others are claiming that it#39;s completely safe. I almost removed it from my computer until a forum. Microsoft . Microsoft Windows , Microsoft Visual Studio Community . 4KB . Microsoft .
How to delete in.
. What Is ‘Regid.1991-06.Com.Microsoft’ and Can You Delete It? Share Watch on There’s a good bit of vague information about this folder out.
Windows 10 C Diskinde ProgramData Dosyas Nedir? — Technopat Sosyal.
Regid 1991 06 com microsoft windows 10. , , Windows, . . 1 Windows-10-Enterprise.swidtag , 2 2:SFC Windows-10-Enterprise.swidtag Windows , SFC Windows-10-Enterprise.swidtag Windows XPVista7810: Windows . MSOCache ise Microsoft Office kurulum dosyalarn barndryor. Office#x27;i offline olarak onarmak istediginizde Office kendini siliyor ve bu klasoru kullanarak tekrar kuruyor. Eger Office bozulursa silerim tekrar kurarm derseniz silmenizin bir sakncas yok.
Czy moge usunac folder Windows 10.
Hallo zusammen habe bei meinen pc im Programm Order Program Data das gesehen ist das gefahrlich? Ein virus vielleicht wunsche euch ein schones Wochenende.
What Is Regid.1991-06.Com.Microsoft and Can You Delete It?.
Apr 21, 2021 Pliki znajdujace sie w folderze to tak zwane tagi oprogramowania. Tagowanie oprogramowania to proces utrzymywania zestawu plikow, tagow .swidtag na komputerze klienckim w celu okreslenia stanu instalacji i licencji roznych produktow oprogramowania. Pliki te nadpisuja sie podczas ponownego uruchomienia. Dr.Windows-tik UpdatePack 1. ISO produktua instalatu da! C azpian: #92; ProgramData kokatzen da Karpetean sartuta fitxategi hau da: Windows-8.1.swidtag. Hori etortzen zait softwarearen identifikazio-etiketa fitxategia! Bertan honako karpeta hau aurki dezakezu. R — Meilleures reponses. #06# ecoute telephonique — Forum Mobile. R — Forum Virus / Securite. Faux numero de telephone 06 — Forum Mobile. 00 00 00 06 facture free — Forum Mobile. Code pour mettre un numero sur ecoute — Forum Android.
Win8regid.1991 ? — .
Folder today I noticed this file appear randomly or at least I think because that I can remember, I’ve never seen this folder before and its the. , : Microsoft Visual Studio Community 2015.swidtag , Microsoft Visual Studio Community.
[gelost] — | Dr. Windows.
What Is ‘Regid.1991-06.Com.Microsoft’ and Can You Delete It? majorgeeks 36.6K subscribers Subscribe 13K views 2 years ago Recently while cleaning house on. ? : :C:ProgramD,Office,Office, C,C, Win8.1tdx.sys? : Win8.1,,tdx.sys tdx.sys?. Oct 30, 2019 Rich, I have Windows 10 Home. I have the folder C:#92;ProgramData#92; and it contains. Windows-10-Home.swidtag. I think this is the most reliable method given that people are known to manually add C:#92;Windows#92;System32#92; to the Home Edition. Of course, somebody could also add/substitute.
YuRiEm.
Es este archivo: Windows-8.1.swidtag. Lo que me viene es el archivo de etiqueta de identificacion del software! Alli puede encontrar la siguiente carpeta:… Durante aproximadamente 3 semanas puede estar en mi Surface 2 con Win Parece que la conexion del servidor o 8.1 pro, los. In some rare cases you might need to contact Microsoft directly for the correct file version you need. Once the file is successfully placed in the right location on you hard drive, these Windows-10-Enterprise.swidtag issues should disappear. Running a quick verification test is highly recommend. Empfohlene Losung: Ich empfehle ASR herunterzuladen. Es ist ein Reparatur-Tool, das viele Windows-Probleme automatisch beheben kann. Sie konnen es von hier herunterladen Download ASR. Dieser Link startet einen Download von ASR. Aktualitat 25.83.
-
What means this item in the folder program data ?
regid.1991-06.com.microsoft_Windows-8-Pro-with-Media-Center.swidtag
Can i delete this or just leave alone ? just curious.
Best Regards
-
The folder is protected by TrustedInstaller and isn’t good to delete it…
I can’t say exactly what’s the function of it, but for me, have 2 files that contains XML text for Windows 8 with Media Center and Visual Studio 2012..
Microsoft Stuff…
Stop hovering to collapse…
Click to collapse…
Hover to expand…
Click to expand…
-
-
Microsoft Support & Malware Removal
-
Windows Update
You should upgrade or use an alternative browser.
Win10 1909 (18363.720) Corrupt Components Hive
-
Thread starter
Thread starterfront360
-
Start date
Start date
- Joined
- Nov 23, 2015
- Posts
- 24
- Location
-
USA
-
-
#1
Thanks in advance,
Don
COMPONENTS.zip
SleepyDude
Windows Update Moderator, Security Analyst
- Joined
- Dec 20, 2013
- Posts
- 3,062
- Location
-
Portugal
-
-
#2
Replace Components Hive Manually
!!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems…
- Download COMPONENTS2.ZIP and save it to the Desktop.
- Right-click on it and select Extract all…. Make sure the «Show extracted files when complete» is checked and click Extract.
- Now you have the COMPONENTS file that we will be using to replace your current one.
- Navigate to C:\Windows\System32\config
- Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad.
Note: If you get an error that the file is in use, reboot your computer and then try again. - Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config
Yep this is a trade secret
- Joined
- Nov 23, 2015
- Posts
- 24
- Location
-
USA
-
-
#3
9.25.2019_12.41.54-AM.zip
I just noticed that the one you fixed is the same size as the corrupt one. Was it just fragmented or was there a «bit» on or off in there?(I dunno what I’m talking about here, that’s why I need to be learned from you) Thanks in advance.
- Joined
- Nov 23, 2015
- Posts
- 24
- Location
-
USA
-
-
#4
The file you gave me, cleared up that corruption error. SFC /scannow finishes without any problems. Now, I do have issues with DISM /RestoreHealth. It stays at around 86.7% for a long time, then shows an error that says I need to run it again with «/OFFLINE». I’m on WIn10 v1909, so I think I know where to get the ISO, in order to mount it and run DISM /OFFLINE. If you could just make sure I’m on the correct path first and tell me what logs you need, then I could continue trying to fix this thing. Thanks in advance.
SleepyDude
Windows Update Moderator, Security Analyst
- Joined
- Dec 20, 2013
- Posts
- 3,062
- Location
-
Portugal
-
-
#5
Sorry for the delay! I am working from home and these days the workload has been immense…
Replacing the COMPONENTS hive must be done using the most recent version available, 9/25/2019 is very old! don’t forget that at least every month Microsoft releases new updates and the system changes the COMPONENTS hive with several information’s about the updates installed…
To repair the registry hive we use an internal tool developed by a Staff member.
Please run DISM /RestoreHealth again and then collect the CBS.log.
Locate the log c:\Windows\logs\cbs\CBS.log copy the file to the Desktop, Zip it and attach to your post.
Note: If the file is too big to attach please upload it to a service like Dropbox, Google Drive, OneDrive or upload to SendSpace and just provide the link for the file here.
- Joined
- Nov 23, 2015
- Posts
- 24
- Location
-
USA
-
-
#6
Do you know if the method written here would have worked to fix the hive?
«Error: 0x800f081f The source files could not be found.»
Here’s the CBS.log
Thanks in advance.
SleepyDude
Windows Update Moderator, Security Analyst
- Joined
- Dec 20, 2013
- Posts
- 3,062
- Location
-
Portugal
-
-
#7
SFCFix Script
!!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems…
Attachments
-
SFCFIX.zip
- Joined
- Nov 23, 2015
- Posts
- 24
- Location
-
USA
-
-
#8
I’m perty computer literate, so if it’s not a hassle, and you want to, you can leave me a few things to do each post. It’ll hopefully get this fixed faster, and get the wifey off my back, j/k. The laptop has been acting so weird, an hour after turning it on, all websites take way too long to load(pics actually load a few lines at a time from top to bottom, like the old 56k modem days, lol) and any DL’s just stop or fail from inactivity. I then reboot and get what I can done, before it grinds to a halt, and I have to reboot again.
Start time: 2020-04-27 23:33:56.608
Microsoft Windows 10 Build 18363 — amd64
Using .zip script file at C:\Users\Donald\Desktop\SFCFIX.zip [0]
PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\x86_microsoft-windows-s..ck-mof-onecoreadmin_31bf3856ad364e35_10.0.18362.590_none_134041a2087f339f\wbemcore.dll
Successfully copied file C:\Users\Donald\AppData\Local\niemiro\Archive\WinSxS\x86_microsoft-windows-s..ck-mof-onecoreadmin_31bf3856ad364e35_10.0.18362.590_none_134041a2087f339f\wbemcore.dll to C:\WINDOWS\WinSxS\x86_microsoft-windows-s..ck-mof-onecoreadmin_31bf3856ad364e35_10.0.18362.590_none_134041a2087f339f\wbemcore.dll.
Successfully restored ownership for C:\WINDOWS\WinSxS\x86_microsoft-windows-s..ck-mof-onecoreadmin_31bf3856ad364e35_10.0.18362.590_none_134041a2087f339f\wbemcore.dll
Successfully restored permissions on C:\WINDOWS\WinSxS\x86_microsoft-windows-s..ck-mof-onecoreadmin_31bf3856ad364e35_10.0.18362.590_none_134041a2087f339f\wbemcore.dll
PowerCopy:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2020-04-27 23:33:57.822
Script hash: wrLau6WGumKJ1WeXHarS6mcCJgHhOOszSllOIbjZCu8=
———————-EOF————————
- Joined
- Nov 23, 2015
- Posts
- 24
- Location
-
USA
-
-
#9
I forgot to add above that when I had the hive corruption, WU kept failing when trying to install this month’s Patch Tuesday update. Then just a few hours ago when shutting down, it was successfully updating, so that part is fixed. Also, DISM /RestoreHealth now finishes at 100%, which is better, but still has the same Source error.
Thanks in advance.
- Joined
- Nov 23, 2015
- Posts
- 24
- Location
-
USA
-
-
#10
edit PS- I just ran DISM again(after a reboot), and this time it told me:
«The restore operation completed successfully.
The operation completed successfully.»
So lemme know what, if anything, you need from me or for me to do. Thanks.
SleepyDude
Windows Update Moderator, Security Analyst
- Joined
- Dec 20, 2013
- Posts
- 3,062
- Location
-
Portugal
-
-
#11
Thank you for the update, sounds good.
Just to confirm please run SFC also
SFC scan
- Please open up a Command Prompt Window as a Administrator, instructions for Windows 10.
- Inside the command prompt window type or Copy & Paste the following command:
sfc /scannow
Note: This may take some time to finish. If the result is not «No integrity violations found» or equivalent please post the new CBS.log.
- Joined
- Nov 23, 2015
- Posts
- 24
- Location
-
USA
-
-
#12
This slow internet after approximately two hours of PC uptime, until reboot, is still going on. I really thought this stuff was going to fix that, because it only started happening when this hive corruption and DISM issues started.
- Joined
- Nov 23, 2015
- Posts
- 24
- Location
-
USA
-
-
#13
Are the Warning and Error items in the log unimportant?
Something has to off and affecting the fact that I can only DL and view pages with speed, for a couple hours, before needing to reboot.
Thanks in advance,
Don
SleepyDude
Windows Update Moderator, Security Analyst
- Joined
- Dec 20, 2013
- Posts
- 3,062
- Location
-
Portugal
-
-
#14
The CBS log is cumulative, I don’t see any recent error.
To get a better picture of the system please provide the following logs.
Farbar Recovery Scan Tool (FRST)
Note: If FRST interface isn’t in English please close it and rename the file to EnglishFRST.exe or EnglishFRST64.exe before doing the scan, to get logs in English.
- Joined
- Nov 23, 2015
- Posts
- 24
- Location
-
USA
SleepyDude
Windows Update Moderator, Security Analyst
- Joined
- Dec 20, 2013
- Posts
- 3,062
- Location
-
Portugal
-
-
#16
Run a disk check…
» Check the Disk for Errors
- open the Command Prompt as Administrator (Tutorial)
- type the command:
Note: When it ask if you want to checked the volume next time the system restarts answer Yes
- Restart the Computer and let the check run during boot, it will take some time depending on the HDD size…
Next,
- download ListChkdskResult
- execute the file and accept all the windows prompts to authorize the program to run
- Notepad will open with a report showing the chkdsk result
- copy & paste the log to your reply
Edit: The log show two antivirus installed! Webroot SecureAnywhere and ESET Security you should have only one security program active at the same time.
- Joined
- Nov 23, 2015
- Posts
- 24
- Location
-
USA
-
-
#17
Here’s one of the missing things I found in CBS.log, maybe others too.
2020-05-07 18:15:55, Info CBS Repr: Could not find missing package manifest/cat for packageackage_1_for_KB4521863~31bf3856ad364e35~amd64~~18362.411.1.3 in the sandbox
2020-05-07 18:15:55, Info CBS Repr: After UUP download, some manifests are still missing
2020-05-07 18:15:55, Info CBS Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f081f — CBS_E_SOURCE_MISSING]
2020-05-07 18:15:55, Info CBS Failed to repair store. [HRESULT = 0x800f081f — CBS_E_SOURCE_MISSING]
2020-05-07 18:15:55, Info CBS
2020-05-07 18:15:55, Info CBS =================================
2020-05-07 18:15:55, Info CBS Checking System Update Readiness.
2020-05-07 18:15:55, Info CBS
2020-05-07 18:15:55, Info CBS (p) CBS MUM Missing Package_1_for_KB4521863~31bf3856ad364e35~amd64~~18362.411.1.3
2020-05-07 18:15:55, Info CBS Repair failed: Missing replacement mum/cat pair.
2020-05-07 18:15:55, Info CBS
2020-05-07 18:15:55, Info CBS Summary:
2020-05-07 18:15:55, Info CBS Operation: Detect and Repair
2020-05-07 18:15:55, Info CBS Operation result: 0x800f081f
2020-05-07 18:15:55, Info CBS Last Successful Step: Entire operation completes.
2020-05-07 18:15:55, Info CBS Total Detected Corruption: 1
2020-05-07 18:15:55, Info CBS CBS Manifest Corruption: 1
2020-05-07 18:15:55, Info CBS CBS Metadata Corruption: 0
2020-05-07 18:15:55, Info CBS CSI Manifest Corruption: 0
2020-05-07 18:15:55, Info CBS CSI Metadata Corruption: 0
2020-05-07 18:15:55, Info CBS CSI Payload Corruption: 0
2020-05-07 18:15:55, Info CBS Total Repaired Corruption: 0
2020-05-07 18:15:55, Info CBS CBS Manifest Repaired: 0
2020-05-07 18:15:55, Info CBS CSI Manifest Repaired: 0
2020-05-07 18:15:55, Info CBS CSI Payload Repaired: 0
2020-05-07 18:15:55, Info CBS CSI Store Metadata refreshed: True
- Joined
- Nov 23, 2015
- Posts
- 24
- Location
-
USA
-
-
#18
- Joined
- Nov 23, 2015
- Posts
- 24
- Location
-
USA
-
-
#19
——< Log generate on 5/8/2020 1:16:08 AM >——
Category: 0
Computer Name: Laptop
Event Code: 26226
Record Number: 128344
Source Name: Chkdsk
Time Written: 05-07-2020 @ 19:01:04
Event Type: Information
User:
Message: Chkdsk was executed in scan mode on a volume snapshot.
Checking file system on C:
Volume label is Windows 10 Pro x64.
Stage 1: Examining basic file system structure …
756480 file records processed.
File verification completed.
8352 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage …
14134 reparse records processed.
978690 index entries processed.
Index verification completed.
14134 reparse records processed.
Stage 3: Examining security descriptors …
Security descriptor verification completed.
111105 data files processed.
CHKDSK is verifying Usn Journal…
40631544 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
218250064 KB total disk space.
160160052 KB in 477113 files.
229564 KB in 111107 indexes.
874400 KB in use by the system.
65536 KB occupied by the log file.
56986048 KB available on disk.
4096 bytes in each allocation unit.
54562516 total allocation units on disk.
14246512 allocation units available on disk.
———————————————————————-
Stage 1: Examining basic file system structure …
Stage 2: Examining file name linkage …
Stage 3: Examining security descriptors …
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26226
Record Number: 127601
Source Name: Chkdsk
Time Written: 05-05-2020 @ 11:05:39
Event Type: Information
User:
Message: Chkdsk was executed in scan mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Stage 1: Examining basic file system structure …
756480 file records processed.
File verification completed.
8335 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage …
14122 reparse records processed.
Found corruption in index «$I30» of directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\ConstraintIndex\Apps_{823d4f8b-f830-4b7e-8cc3-a6d4fdeeb701} <0x31b,0x1c5f>»
… queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 …………….
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ?? ÿÿÿÿÿÿÿÿ……..
Found a mis-ordered index «$I30» from directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\ConstraintIndex\Apps_{823d4f8b-f830-4b7e-8cc3-a6d4fdeeb701} <0x31b,0x1c5f>»
… queued for offline repair.
Found corruption in index «$I30» of directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\ConstraintIndex\Apps_{2e51a73e-b5ef-4992-bdf6-f49536724832} <0x2af,0x2048>»
… queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 …………….
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ?? ÿÿÿÿÿÿÿÿ……..
Found a mis-ordered index «$I30» from directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\ConstraintIndex\Apps_{2e51a73e-b5ef-4992-bdf6-f49536724832} <0x2af,0x2048>»
… queued for offline repair.
Found a bad index «$I30» in directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\AC\AppCache\MAV1OMQD\329 <0x1a8,0xeb0b>»
… queued for offline repair.
Found corruption in index «$I30» of directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\AC\AppCache\MAV1OMQD\329 <0x1a8,0xeb0b>»
… queued for offline repair.
The down pointer of current index entry with length 0xa0 is invalid.
b9 70 03 00 00 00 13 01 a0 00 84 00 01 00 00 00 .p…… ……
0b eb 00 00 00 00 a8 01 22 41 66 72 aa 21 d6 01 .ë….¨.»Afrª!..
22 41 66 72 aa 21 d6 01 22 41 66 72 aa 21 d6 01 «Afrª!..»Afrª!..
22 41 66 72 aa 21 d6 01 00 60 00 00 00 00 00 00 «Afrª!…`……
49 52 00 00 00 00 00 00 20 20 00 00 00 00 00 00 IR…… ……
21 00 4e 00 79 00 77 00 6c 00 33 00 59 00 32 00 !.N.y.w.l.3.Y.2.
49 00 54 00 68 00 59 00 79 00 69 00 62 00 58 00 I.T.h.Y.y.i.b.X.
64 00 47 00 4d 00 35 00 53 00 4d 00 45 00 5f 00 d.G.M.5.S.M.E._.
47 00 53 00 62 00 49 00 5b 00 31 00 5d 00 2e 00 G.S.b.I.[.1.]…
6a 00 73 00 00 00 00 00 ff ff ff ff ff ff ff ff j.s…..ÿÿÿÿÿÿÿÿ
Found a mis-ordered index «$I30» from directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\AC\AppCache\MAV1OMQD\329 <0x1a8,0xeb0b>»
… queued for offline repair.
979012 index entries processed.
Index verification completed.
Found 30 missing entries (\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\AC\AppCache\MAV1OMQD\329\container.dat <0x204,0x1b0b5>, …) in index «$I30» of directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\AC\AppCache\MAV1OMQD\329 <0x1a8,0xeb0b>»
… queued for offline repair.
Found 5 missing entries (\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\ConstraintIndex\Apps_{2e51a73e-b5ef-4992-bdf6-f49536724832}\Apps.index <0x2a5,0x20ed>, …) in index «$I30» of directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\ConstraintIndex\Apps_{2e51a73e-b5ef-4992-bdf6-f49536724832} <0x2af,0x2048>»
… queued for offline repair.
Found 5 missing entries (\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\ConstraintIndex\Apps_{823d4f8b-f830-4b7e-8cc3-a6d4fdeeb701}\Apps.index <0x28d,0x8bf3>, …) in index «$I30» of directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\ConstraintIndex\Apps_{823d4f8b-f830-4b7e-8cc3-a6d4fdeeb701} <0x31b,0x1c5f>»
… queued for offline repair.
14122 reparse records processed.
Stage 3: Examining security descriptors …
Security descriptor verification completed.
111266 data files processed.
CHKDSK is verifying Usn Journal…
Usn Journal verification completed.
Windows has found problems that must be fixed offline.
Please run «chkdsk /spotfix» to fix the issues.
218250064 KB total disk space.
158507356 KB in 473098 files.
228704 KB in 111268 indexes.
834128 KB in use by the system.
65536 KB occupied by the log file.
58679876 KB available on disk.
4096 bytes in each allocation unit.
54562516 total allocation units on disk.
14669969 allocation units available on disk.
———————————————————————-
Stage 1: Examining basic file system structure …
Stage 2: Examining file name linkage …
The multi-sector header signature for VCN 0x0 of index $I30
in file 0x1c5f is incorrect.
00 00 00 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ?? …………….
Correcting error in index $I30 for file 1C5F.
The index bitmap $I30 in file 0x1c5f is incorrect.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 1C5F.
Sorting index $I30 in file 1C5F.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0x2048 is incorrect.
00 00 00 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ?? …………….
Correcting error in index $I30 for file 2048.
The index bitmap $I30 in file 0x2048 is incorrect.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 2048.
Sorting index $I30 in file 2048.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xeb0b is incorrect.
00 00 00 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ?? …………….
The multi-sector header signature for VCN 0x1 of index $I30
in file 0xeb0b is incorrect.
00 00 00 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ?? …………….
Correcting error in index $I30 for file EB0B.
The index bitmap $I30 in file 0xeb0b is incorrect.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file EB0B.
Sorting index $I30 in file EB0B.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file Apps.index (20ED) into directory file 2048.
Recovering orphaned file Apps.index (20ED) into directory file 2048.
Recovering orphaned file 0.0.filtertrie.intermediate.txt (27C2) into directory file 2048.
Recovering orphaned file 0.0.filtertrie.intermediate.txt (27C2) into directory file 2048.
Recovering orphaned file 0.1.filtertrie.intermediate.txt (3213) into directory file 2048.
Recovering orphaned file 0.1.filtertrie.intermediate.txt (3213) into directory file 2048.
Recovering orphaned file Apps.index (8BF3) into directory file 1C5F.
Recovering orphaned file Apps.index (8BF3) into directory file 1C5F.
Recovering orphaned file 0.0.filtertrie.intermediate.txt (AD56) into directory file 1C5F.
Recovering orphaned file 0.0.filtertrie.intermediate.txt (AD56) into directory file 1C5F.
Skipping further messages about recovering orphans.
40 unindexed files recovered to original directory.
Stage 3: Examining security descriptors …
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 127587
Source Name: Chkdsk
Time Written: 05-05-2020 @ 10:59:31
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 1 corruption record …
Record 1 of 1: Corruption in index «$I30» of directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\AC\AppCache\MAV1OMQD\329 <0x1a8,0xeb0b>» … The multi-sector header signature for VCN 0x1 of index $I30
in file 0xeb0b is incorrect.
00 00 00 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ?? …………….
The index entry offset, 0x0, of index $I30
in file 0xeb0b is incorrect.
corruption found.
1 corruption record processed in 0.1 seconds.
Windows has examined the list of previously identified potential issues and found problems.
Please run chkdsk /scan to fully analyze the problems and queue them for repair.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 127557
Source Name: Chkdsk
Time Written: 05-05-2020 @ 10:53:28
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 2 corruption records …
Record 1 of 2: Bad index «$I30» in directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\ConstraintIndex\Apps_{823d4f8b-f830-4b7e-8cc3-a6d4fdeeb701} <0x31b,0x1c5f>» … The multi-sector header signature for VCN 0x0 of index $I30
in file 0x1c5f is incorrect.
00 00 00 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ?? …………….
corruption found.
Record 2 of 2: Bad index «$I30» in directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\ConstraintIndex\Apps_{2e51a73e-b5ef-4992-bdf6-f49536724832} <0x2af,0x2048>» … The multi-sector header signature for VCN 0x0 of index $I30
in file 0x2048 is incorrect.
00 00 00 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ?? …………….
corruption found.
2 corruption records processed in 0.1 seconds.
Windows has examined the list of previously identified potential issues and found problems.
Please run chkdsk /scan to fully analyze the problems and queue them for repair.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 127556
Source Name: Chkdsk
Time Written: 05-05-2020 @ 10:53:17
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 1 corruption record …
Record 1 of 1: Bad subtree in index «$I30» of directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\AC\AppCache\MAV1OMQD\329 <0x1a8,0xeb0b>» … The multi-sector header signature for VCN 0x0 of index $I30
in file 0xeb0b is incorrect.
00 00 00 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ?? …………….
The index entry offset, 0x0, of index $I30
in file 0xeb0b is incorrect.
corruption found.
1 corruption record processed in 0.1 seconds.
Windows has examined the list of previously identified potential issues and found problems.
Please run chkdsk /scan to fully analyze the problems and queue them for repair.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26226
Record Number: 126978
Source Name: Chkdsk
Time Written: 05-03-2020 @ 05:18:37
Event Type: Information
User:
Message: Chkdsk was executed in scan mode on a volume snapshot.
Checking file system on C:
Volume label is Windows 10 Pro x64.
Stage 1: Examining basic file system structure …
756480 file records processed.
File verification completed.
8312 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage …
14120 reparse records processed.
979050 index entries processed.
Index verification completed.
14120 reparse records processed.
Stage 3: Examining security descriptors …
Security descriptor verification completed.
111285 data files processed.
CHKDSK is verifying Usn Journal…
3711856 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
218250064 KB total disk space.
159855168 KB in 475344 files.
228972 KB in 111287 indexes.
838176 KB in use by the system.
65536 KB occupied by the log file.
57327748 KB available on disk.
4096 bytes in each allocation unit.
54562516 total allocation units on disk.
14331937 allocation units available on disk.
———————————————————————-
Stage 1: Examining basic file system structure …
Stage 2: Examining file name linkage …
Stage 3: Examining security descriptors …
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 1001
Record Number: 126949
Source Name: Microsoft-Windows-Wininit
Time Written: 05-03-2020 @ 05:05:16
Event Type: Information
User:
Message:
Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows 10 Pro x64.
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 …
756480 file records processed.
File verification completed.
8311 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage …
14120 reparse records processed.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0x252 is incorrect.
00 00 00 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ?? …………….
Correcting error in index $I30 for file 252.
The index bitmap $I30 in file 0x252 is incorrect.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 252.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 …………….
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ?? …………….
Sorting index $I30 in file 252.
Unable to locate the file name attribute of index entry DiagTrack_aot
of index $I30 with parent 0x59c in file 0xd756.
Deleting index entry DiagTrack_aot in index $I30 of file 59C.
Unable to locate the file name attribute of index entry 73ce1317-4192-2dd7-a00a-d9171030d9eb.xml
of index $I30 with parent 0xa3c in file 0x45d.
Deleting index entry 73ce1317-4192-2dd7-a00a-d9171030d9eb.xml in index $I30 of file A3C.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xf72 is incorrect.
8a 3e fe 08 0c 00 01 ee ?? ?? ?? ?? ?? ?? ?? ?? .>…………..
The multi-sector header signature for VCN 0x1 of index $I30
in file 0xf72 is incorrect.
30 5c 72 a7 1b 6d fb fc ?? ?? ?? ?? ?? ?? ?? ?? 0\r..m……….
Correcting error in index $I30 for file F72.
The index bitmap $I30 in file 0xf72 is incorrect.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file F72.
The down pointer of current index entry with length 0xa0 is invalid.
1c e0 00 00 00 00 94 04 a0 00 84 00 01 00 00 00 …………….
72 0f 00 00 00 00 67 08 2b 80 bd 8f bc 20 d6 01 r…..g.+…. ..
2b 80 bd 8f bc 20 d6 01 2b 80 bd 8f bc 20 d6 01 +…. ..+…. ..
2b 80 bd 8f bc 20 d6 01 00 60 00 00 00 00 00 00 +…. …`……
49 52 00 00 00 00 00 00 20 20 00 00 00 00 00 00 IR…… ……
21 00 4e 00 79 00 77 00 6c 00 33 00 59 00 32 00 !.N.y.w.l.3.Y.2.
49 00 54 00 68 00 59 00 79 00 69 00 62 00 58 00 I.T.h.Y.y.i.b.X.
64 00 47 00 4d 00 35 00 53 00 4d 00 45 00 5f 00 d.G.M.5.S.M.E._.
47 00 53 00 62 00 49 00 5b 00 31 00 5d 00 2e 00 G.S.b.I.[.1.]…
6a 00 73 00 00 00 00 00 ff ff ff ff ff ff ff ff j.s………….
Sorting index $I30 in file F72.
The file reference 0x49400000000e01c of index entry Nywl3Y2IThYyibXdGM5SME_GSbI[1].js of index $I30
with parent 0xf72 is not the same as 0x49d00000000e01c.
Deleting index entry Nywl3Y2IThYyibXdGM5SME_GSbI[1].js in index $I30 of file F72.
The file reference 0x7800000000105e of index entry filehippo[2].xml of index $I30
with parent 0x13b5d is not the same as 0x7a00000000105e.
Deleting index entry filehippo[2].xml in index $I30 of file 13B5D.
The file reference 0x7800000000105e of index entry FILEHI~2.XML of index $I30
with parent 0x13b5d is not the same as 0x7a00000000105e.
Deleting index entry FILEHI~2.XML in index $I30 of file 13B5D.
Unable to locate the file name attribute of index entry 0-ReviewList-https∺∯∯next-services.apps.microsoft.com∯4R∯6.3.9600-0∯788∯en-US∯m∯US∯Apps∯64a79953-cf0b-44f9-b5c4-ee5df3a15c63∯Reviews∯all∯s∯helpful∯1∯pn∯1∯ri∯0815063d-cf74-4911-9120-5ed8812eebe8∯vf∯mix.dat
of index $I30 with parent 0x4508e in file 0x1079.
Deleting index entry 0-ReviewList-https∺∯∯next-services.apps.microsoft.com∯4R∯6.3.9600-0∯788∯en-US∯m∯US∯Apps∯64a79953-cf0b-44f9-b5c4-ee5df3a15c63∯Reviews∯all∯s∯helpful∯1∯pn∯1∯ri∯0815063d-cf74-4911-9120-5ed8812eebe8∯vf∯mix.dat in index $I30 of file 4508E.
979040 index entries processed.
Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file Apps_{4cd6847c-f894-4eff-b19f-53f922b8c278} (252) into directory file 1D4DE.
Recovering orphaned file 0-ReviewList-https∺∯∯next-services.apps.microsoft.com∯4R∯6.3.9600-0∯788∯en-US∯m∯US∯Apps∯64a79953-cf0b-44f9-b5c4-ee5df3a15c63∯eviews∯all∯s∯helpful∯1∯pn∯1∯ri∯0815063d-cf74-4911-9120-5ed8812eebe8∯vf∯mix.dat (1079) into directory file 4508E.
Recovering orphaned file GURA1FC.tmp (508A) into directory file E78.
Recovering orphaned file 320 (77DA) into directory file DB.
11 unindexed files scanned.
4 unindexed files recovered to original directory.
CHKDSK is recovering remaining unindexed files.
8 unindexed files recovered to lost and found.
Lost and found is located at \found.014
14120 reparse records processed.
Stage 3: Examining security descriptors …
Cleaning up 51 unused index entries from index $SII of file 0x9.
Cleaning up 51 unused index entries from index $SDH of file 0x9.
Cleaning up 51 unused security descriptors.
Security descriptor verification completed.
111280 data files processed.
CHKDSK is verifying Usn Journal…
Usn Journal verification completed.
The MFT mirror is different from the MFT.
Correcting errors in the Master File Table (MFT) mirror.
Correcting errors in the master file table’s (MFT) BITMAP attribute.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.
No further action is required.
218250064 KB total disk space.
159575976 KB in 475060 files.
228980 KB in 111284 indexes.
0 KB in bad sectors.
834060 KB in use by the system.
65536 KB occupied by the log file.
57611048 KB available on disk.
4096 bytes in each allocation unit.
54562516 total allocation units on disk.
14402762 allocation units available on disk.
Internal Info:
00 8b 0b 00 1a f2 08 00 f6 55 0b 00 00 00 00 00 ………U……
98 30 00 00 90 06 00 00 00 00 00 00 00 00 00 00 .0…………..
Windows has finished checking your disk.
Please wait while your computer restarts.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26226
Record Number: 126897
Source Name: Chkdsk
Time Written: 05-03-2020 @ 05:01:43
Event Type: Information
User:
Message: Chkdsk was executed in scan mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Stage 1: Examining basic file system structure …
Found 0x1 clusters allocated to file «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\ConstraintIndex\Apps_{4cd6847c-f894-4eff-b19f-53f922b8c278} <0xaf9,0x252>» at offset «0» marked as free
… repaired online.
Found corrupt basic file structure for «<0xb5,0x45d>»
… queued for offline repair.
Found 0x4 clusters allocated to file «\Users\Donald\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\HxCommAlwaysOnLog.etl <0xcce,0x81a>» at offset «0xa» marked as free
… repaired online.
Found 0x1 clusters allocated to file «\ProgramData\regid.1991-06.com.microsoft\regid.1991-06.com.microsoft_Windows-10-Pro.swidtag <0x231,0xbe6>» at offset «0» marked as free
… repaired online.
Found 0x1 clusters allocated to file «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\AC\AppCache\MAV1OMQD\323 <0x867,0xf72>» at offset «0» marked as free
… repaired online.
Found 0x1 clusters allocated to file «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\AC\AppCache\MAV1OMQD\323 <0x867,0xf72>» at offset «0x1» marked as free
… repaired online.
The USA check value, 0x9dc, at block 0x1 is incorrect.
The expected value is 0x9d8.
Found corrupt basic file structure for «<0x78,0x105e>»
… repaired online.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x88af8e for possibly 0x2 clusters.
Found corrupt basic file structure for «\ProgramData\Razer\Razer Central\Logs\Razer Central Service.log <0x191,0x5076>»
… queued for offline repair.
Found 0x12 clusters allocated to file «\Windows\Minidump\050220-19953-01.dmp <0x39c,0xda26>» at offset «0xbf» marked as free
… repaired online.
Attribute record of type 0x80 and instance tag 0x0 is cross linked
starting at 0x11a4d9c for possibly 0x1e clusters.
Found corrupt basic file structure for «\ProgramData\Microsoft\Windows\WER\LocalReportArchive\9e7e3b3f-565d-4f7a-8d7e-7c76d680c9c4.zip <0x17c,0x13d18>»
… queued for offline repair.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x11a4692 for possibly 0x10 clusters.
Found corrupt basic file structure for «\Users\Donald\AppData\Local\Microsoft\Windows Live Mail\Optonline ( 2fb\Deleted Items\7B56100C-00000344.eml <0x10a,0x1967e>»
… queued for offline repair.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x11a46a2 for possibly 0x5 clusters.
Found corrupt basic file structure for «\Users\Donald\AppData\Local\Microsoft\Windows\INetCache\IE\2B4RGAKW\wbk1A13.tmp <0x488,0x1b852>»
… queued for offline repair.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x88af80 for possibly 0xa clusters.
Found corrupt basic file structure for «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\AppIconCache\100\{6D809377-6AF0-444B-8957-A3773F02200E}_VideoLAN_VLC_NEWS_txt <0x20a,0x34bff>»
… queued for offline repair.
File «\Users\Donald\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\HxCommAlwaysOnLog.etl <0xcce,0x81a>» and file «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\AppIconCache\100\{6D809377-6AF0-444B-8957-A3773F02200E}_VideoLAN_VLC_NEWS_txt <0x20a,0x34bff>» both own logical clusters [0x88af80, 0x88af8a)
… queued for offline repair.
File «\Users\Donald\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\HxCommAlwaysOnLog.etl <0xcce,0x81a>» and file «\ProgramData\Razer\Razer Central\Logs\Razer Central Service.log <0x191,0x5076>» both own logical clusters [0x88af8e, 0x88af90)
… queued for offline repair.
File «\Users\Donald\AppData\Local\Packages\828B5831.JewelsofRomeMatchgemstorestorethecity_ytsefhwckbdv6\LocalCache\pgp_webcache\c7568fb2e8c24298093399662e3a9691738aa236_152x152_jpg-85@2x <0x39a,0x1e4b>» and file «\ProgramData\Microsoft\Windows\WER\LocalReportArchive\9e7e3b3f-565d-4f7a-8d7e-7c76d680c9c4.zip <0x17c,0x13d18>» both own logical cluster 0x11a4db9
… queued for offline repair.
File «\Users\Donald\AppData\Roaming\Amazon Cloud Drive\Logs\AmazonCloudDrive-2020-05-02-06-35-10-289.log <0xdd,0x11d77>» and file «\Users\Donald\AppData\Local\Microsoft\Windows Live Mail\Optonline ( 2fb\Deleted Items\7B56100C-00000344.eml <0x10a,0x1967e>» both own logical clusters [0x11a4694, 0x11a46a2)
… queued for offline repair.
File «\Users\Donald\AppData\Roaming\Amazon Cloud Drive\Logs\AmazonCloudDrive-2020-05-02-06-35-10-289.log <0xdd,0x11d77>» and file «\Users\Donald\AppData\Local\Microsoft\Windows\INetCache\IE\2B4RGAKW\wbk1A13.tmp <0x488,0x1b852>» both own logical clusters [0x11a46a2, 0x11a46a7)
… queued for offline repair.
756480 file records processed.
File verification completed.
«Chkdsk /scan» has found and repaired critical volume bitmap corruption online and must restart the scan.
———————————————————————-
Stage 1: Examining basic file system structure …
The instance tag 0x1902 of attribute of type 0x30 in file 0x45d
is too large. The instance tag should be less than 0x6.
Deleting corrupt attribute record (0x30, «»)
from file record segment 0x45D.
The multi-sector header signature in file 0x105e is incorrect.
42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0………..
Deleting corrupt file record segment 105E.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x5076 is already in use.
Deleting corrupt attribute record (0x80, «»)
from file record segment 0x5076.
Some clusters occupied by attribute of type 0x80 and instance tag 0x0
in file 0x13d18 is already in use.
The attribute of type 0x80 and instance tag 0x0 in file 0x13d18
has allocated length of 0xe308000 instead of 0x6f30000.
Deleted corrupt attribute list entry
with type code 80 in file 13D18.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x13d000000010a13. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, «»)
from file record segment 0x10A13.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x2c9000000017464. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, «»)
from file record segment 0x17464.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x3b000000001917a. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, «»)
from file record segment 0x1917A.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x3b6000000019ceb. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, «»)
from file record segment 0x19CEB.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1967e is already in use.
Deleting corrupt attribute record (0x80, «»)
from file record segment 0x1967E.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1b852 is already in use.
Deleting corrupt attribute record (0x80, «»)
from file record segment 0x1B852.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x34bff is already in use.
Deleting corrupt attribute record (0x80, «»)
from file record segment 0x34BFF.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 126513
Source Name: Chkdsk
Time Written: 05-02-2020 @ 20:09:12
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 2 corruption records …
Record 1 of 2: Corrupt File «<0x202,0x13ca1>» … no corruption found.
Record 2 of 2: Corrupt File «<0x214,0xc7c7>» … no corruption found.
2 corruption records processed in 14.2 seconds.
Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 126510
Source Name: Chkdsk
Time Written: 05-02-2020 @ 20:08:20
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 2 corruption records …
Record 1 of 2: Corrupt File «<0xccd,0x81a>» … no corruption found.
Record 2 of 2: Corrupt File «\Users\Donald\AppData\Local\Microsoft\OneDrive\logs\Personal\TraceArchive.1124.0012-1030.etl <0xb0b,0x68>» … no corruption found.
2 corruption records processed in 0.1 seconds.
Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 126509
Source Name: Chkdsk
Time Written: 05-02-2020 @ 20:08:12
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 2 corruption records …
Record 1 of 2: Corrupt File «<0x44f,0xec3>» … no corruption found.
Record 2 of 2: Corrupt File «<0x762,0x385>» … no corruption found.
2 corruption records processed in 0.3 seconds.
Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 126508
Source Name: Chkdsk
Time Written: 05-02-2020 @ 20:08:04
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 1 corruption record …
Record 1 of 1: Bad subtree in index «$I30» of directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\AC\AppCache\MAV1OMQD\323 <0x867,0xf72>» … The multi-sector header signature for VCN 0x0 of index $I30
in file 0xf72 is incorrect.
8a 3e fe 08 0c 00 01 ee ?? ?? ?? ?? ?? ?? ?? ?? >…..î……..
The first index entry offset, 0xe3ee0101, for index $I30 in file 0xf72
points beyond the length, 0xfe8, of the index. VCN is unknown.
corruption found.
1 corruption record processed in 0.1 seconds.
Windows has examined the list of previously identified potential issues and found problems.
Please run chkdsk /scan to fully analyze the problems and queue them for repair.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 126505
Source Name: Chkdsk
Time Written: 05-02-2020 @ 20:07:57
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 2 corruption records …
Record 1 of 2: Corrupt File «<0x1d0,0xbdb6>» … no corruption found.
Record 2 of 2: Corrupt File «<0x2db,0x508a>» … no corruption found.
2 corruption records processed in 0.2 seconds.
Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 126504
Source Name: Chkdsk
Time Written: 05-02-2020 @ 20:07:49
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 1 corruption record …
Record 1 of 1: Corrupt File «<0x230,0xbe6>» … no corruption found.
1 corruption record processed in 0.1 seconds.
Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 126493
Source Name: Chkdsk
Time Written: 05-02-2020 @ 20:07:40
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 5 corruption records …
Record 1 of 5: Corrupt File «<0x866,0xf72>» … no corruption found.
Record 2 of 5: Corrupt File «\Windows\System32\LogFiles\WMI\AutoLogger-Diagtrack-Listener.etl <0x200,0xd5ae>» … no corruption found.
Record 3 of 5: Corrupt File «<0xaf8,0x252>» … no corruption found.
Record 4 of 5: Corrupt File «\Windows\System32\SleepStudy\UserNotPresentSession.etl <0x459,0xdae4>» … no corruption found.
Record 5 of 5: Corrupt File «\Windows\Minidump\050220-19953-01.dmp <0x39c,0xda26>» … no corruption found.
5 corruption records processed in 0.1 seconds.
Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 1001
Record Number: 126279
Source Name: Microsoft-Windows-Wininit
Time Written: 05-01-2020 @ 22:14:49
Event Type: Information
User:
Message:
Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows 10 Pro x64.
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 …
756480 file records processed.
File verification completed.
8339 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage …
14123 reparse records processed.
979222 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
14123 reparse records processed.
Stage 3: Examining security descriptors …
Security descriptor verification completed.
111371 data files processed.
CHKDSK is verifying Usn Journal…
The USN Journal length 0x6e0 in file 0x12fa1 is less the
largest USN encountered, 0x135b1fe18, plus eight in file 0x29.
Usn Journal verification completed.
The MFT mirror is different from the MFT.
Correcting errors in the Master File Table (MFT) mirror.
Correcting errors in the master file table’s (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
No further action is required.
218250064 KB total disk space.
165674852 KB in 476495 files.
229388 KB in 111373 indexes.
0 KB in bad sectors.
834032 KB in use by the system.
65536 KB occupied by the log file.
51511792 KB available on disk.
4096 bytes in each allocation unit.
54562516 total allocation units on disk.
12877948 allocation units available on disk.
Internal Info:
00 8b 0b 00 10 f8 08 00 5b 5c 0b 00 00 00 00 00 ……..[\……
9b 30 00 00 90 06 00 00 00 00 00 00 00 00 00 00 .0…………..
Windows has finished checking your disk.
Please wait while your computer restarts.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26226
Record Number: 124042
Source Name: Chkdsk
Time Written: 04-29-2020 @ 03:24:35
Event Type: Information
User:
Message: Chkdsk was executed in scan mode on a volume snapshot.
Checking file system on C:
Volume label is Windows 10 Pro x64.
Stage 1: Examining basic file system structure …
756480 file records processed.
File verification completed.
8456 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage …
14117 reparse records processed.
978560 index entries processed.
Index verification completed.
14117 reparse records processed.
Stage 3: Examining security descriptors …
Security descriptor verification completed.
111040 data files processed.
CHKDSK is verifying Usn Journal…
36241808 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
218250064 KB total disk space.
161549596 KB in 472874 files.
228424 KB in 111042 indexes.
876712 KB in use by the system.
65536 KB occupied by the log file.
55595332 KB available on disk.
4096 bytes in each allocation unit.
54562516 total allocation units on disk.
13898833 allocation units available on disk.
———————————————————————-
Stage 1: Examining basic file system structure …
Stage 2: Examining file name linkage …
Stage 3: Examining security descriptors …
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26226
Record Number: 124036
Source Name: Chkdsk
Time Written: 04-29-2020 @ 03:21:31
Event Type: Information
User:
Message: Chkdsk was executed in scan mode on a volume snapshot.
Checking file system on E:
Stage 1: Examining basic file system structure …
2304 file records processed.
File verification completed.
0 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage …
1 reparse records processed.
2344 index entries processed.
Index verification completed.
1 reparse records processed.
Stage 3: Examining security descriptors …
Security descriptor verification completed.
21 data files processed.
CHKDSK is verifying Usn Journal…
368544 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
761919 KB total disk space.
5252 KB in 12 files.
80 KB in 22 indexes.
7803 KB in use by the system.
4544 KB occupied by the log file.
748784 KB available on disk.
4096 bytes in each allocation unit.
190479 total allocation units on disk.
187196 allocation units available on disk.
———————————————————————-
Stage 1: Examining basic file system structure …
Stage 2: Examining file name linkage …
Stage 3: Examining security descriptors …
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26226
Record Number: 124035
Source Name: Chkdsk
Time Written: 04-29-2020 @ 03:20:22
Event Type: Information
User:
Message: Chkdsk was executed in scan mode on a volume snapshot.
Checking file system on D:
Stage 1: Examining basic file system structure …
2304 file records processed.
File verification completed.
0 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage …
1 reparse records processed.
2350 index entries processed.
Index verification completed.
1 reparse records processed.
Stage 3: Examining security descriptors …
Security descriptor verification completed.
24 data files processed.
CHKDSK is verifying Usn Journal…
368544 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
835030 KB total disk space.
458408 KB in 16 files.
80 KB in 25 indexes.
7886 KB in use by the system.
4624 KB occupied by the log file.
368656 KB available on disk.
4096 bytes in each allocation unit.
208757 total allocation units on disk.
92164 allocation units available on disk.
———————————————————————-
Stage 1: Examining basic file system structure …
Stage 2: Examining file name linkage …
Stage 3: Examining security descriptors …
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26226
Record Number: 123888
Source Name: Chkdsk
Time Written: 04-29-2020 @ 02:03:15
Event Type: Information
User:
Message: Chkdsk was executed in scan mode on a volume snapshot.
Checking file system on C:
Volume label is Windows 10 Pro x64.
Stage 1: Examining basic file system structure …
756480 file records processed.
File verification completed.
8455 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage …
14120 reparse records processed.
978828 index entries processed.
Index verification completed.
Found 16 lost files (…\nvspinfo.exe <0x40,0x4d5b8>, …\nvspinfo.exe <0x64,0x4d5b9>, …); requesting reconnection to index «$I30» of directory «\??\C:\found.004»
… repaired online.
Found 2 lost files (…\mstscax.dll.mun <0x3a,0x4e852>, …\mstscax.dll <0xa0,0x4e855>); requesting reconnection to index «$I30» of directory «\??\C:\found.005»
… repaired online.
Found 2 lost files (…\mstsc.exe.mun <0x3c,0x4e863>, …\mstsc.exe <0x23,0x4e86b>); requesting reconnection to index «$I30» of directory «\??\C:\found.006»
… repaired online.
Found 3 lost files (…\nmscrub.exe <0x3f,0x4d7cd>, …\nmbind.exe <0x4e,0x4d7cf>, …); requesting reconnection to index «$I30» of directory «\??\C:\found.007»
… repaired online.
Found 2 lost files (…\mshtml.dll.mun <0x5d,0x4ea4f>, …\mshtml.dll <0x3a,0x4ea59>); requesting reconnection to index «$I30» of directory «\??\C:\found.008»
… repaired online.
Found 2 lost files (…\mshtml.dll.mun <0x67,0x4ea52>, …\mshtml.dll <0x67,0x4ea60>); requesting reconnection to index «$I30» of directory «\??\C:\found.010»
… repaired online.
Found 2 lost files (…\mstscax.dll.mun <0x28,0x4e853>, …\mstscax.dll <0x51,0x4e858>); requesting reconnection to index «$I30» of directory «\??\C:\found.011»
… repaired online.
Found 2 lost files (…\mstsc.exe.mun <0xcb,0x4e867>, …\mstsc.exe <0x24,0x4e86e>); requesting reconnection to index «$I30» of directory «\??\C:\found.012»
… repaired online.
Found 3 lost files (…\nmscrub.exe <0x51,0x4d7cb>, …\nmbind.exe <0x36,0x4d7ce>, …); requesting reconnection to index «$I30» of directory «\??\C:\found.013»
… repaired online.
14120 reparse records processed.
Stage 3: Examining security descriptors …
Security descriptor verification completed.
111174 data files processed.
CHKDSK is verifying Usn Journal…
Usn Journal verification completed.
Windows has found problems and they were all fixed online.
No further action is required.
218250064 KB total disk space.
162167000 KB in 474352 files.
228724 KB in 111185 indexes.
841252 KB in use by the system.
65536 KB occupied by the log file.
55013088 KB available on disk.
4096 bytes in each allocation unit.
54562516 total allocation units on disk.
13753272 allocation units available on disk.
———————————————————————-
Stage 1: Examining basic file system structure …
Stage 2: Examining file name linkage …
CHKDSK is scanning unindexed files for reconnect to their original directory.
0 unindexed files recovered to original directory.
CHKDSK is recovering remaining unindexed files.
Lost and found is located at \found.004
Stage 3: Examining security descriptors …
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 123740
Source Name: Chkdsk
Time Written: 04-28-2020 @ 22:30:25
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 34 corruption records …
Record 1 of 34: Corrupt File «…\nltest.exe <0x52,0x4d7d5>» … no corruption found.
Record 2 of 34: Corrupt File «…\mstscax.dll <0x51,0x4e858>» … no corruption found.
Record 3 of 34: Corrupt File «…\mstsc.exe <0x24,0x4e86e>» … no corruption found.
Record 4 of 34: Corrupt File «…\mstsc.exe <0x23,0x4e86b>» … no corruption found.
Record 5 of 34: Corrupt File «…\mstsc.exe.mun <0xcb,0x4e867>» … no corruption found.
Record 6 of 34: Corrupt File «…\mstsc.exe.mun <0x3c,0x4e863>» … no corruption found.
Record 7 of 34: Corrupt File «…\mshtml.dll <0x5c,0x4ea5d>» … no corruption found.
Record 8 of 34: Corrupt File «…\mshtml.dll <0x12d,0x4ea58>» … no corruption found.
Record 9 of 34: Corrupt File «…\MXEAgent.dll <0x81,0x4e457>» … no corruption found.
Record 10 of 34: Corrupt File «…\MXEAgent.dll <0x74,0x4e453>» … no corruption found.
Record 11 of 34: Corrupt File «\Windows\WinSxS\x86_microsoft-windows-m..-components-jet2x3x_31bf3856ad364e35_10.0.18362.778_none_e13b2bcf93c1ed29\r\msrd3x40.dll <0x48,0x4e978>» … no corruption found.
Record 12 of 34: Corrupt File «…\msltus40.dll <0x14,0x4e9d8>» … no corruption found.
Record 13 of 34: Corrupt File «…\msimsg.dll <0x13,0x4ea13>» … no corruption found.
Record 14 of 34: Corrupt File «…\msimsg.dll <0x93,0x4ea0f>» … no corruption found.
Record 15 of 34: Corrupt File «…\msltus40.dll <0x61,0x4e9d4>» … no corruption found.
Record 16 of 34: Corrupt File «…\nltest.exe <0xcd,0x4d7df>» … no corruption found.
Record 17 of 34: Corrupt File «…\mshtml.dll.mun <0x67,0x4ea52>» … no corruption found.
Record 18 of 34: Corrupt File «…\mshtml.dll.mun <0x5d,0x4ea4f>» … no corruption found.
Record 19 of 34: Corrupt File «…\mstscax.dll <0xa0,0x4e855>» … no corruption found.
Record 20 of 34: Corrupt File «…\mstscax.dll.mun <0x28,0x4e853>» … no corruption found.
Record 21 of 34: Corrupt File «…\mstscax.dll.mun <0x3a,0x4e852>» … no corruption found.
Record 22 of 34: Corrupt File «…\msjet40.dll <0x7c,0x4e9e5>» … no corruption found.
Record 23 of 34: Corrupt File «…\msjet40.dll <0x4a,0x4e9e3>» … no corruption found.
Record 24 of 34: Corrupt File «\Windows\WinSxS\x86_microsoft-windows-m..-components-jet2x3x_31bf3856ad364e35_10.0.18362.778_none_e13b2bcf93c1ed29\f\msrd3x40.dll <0x91,0x4e97b>» … no corruption found.
Record 25 of 34: Corrupt File «…\nmscrub.exe <0x3f,0x4d7cd>» … no corruption found.
Record 26 of 34: Corrupt File «…\nmscrub.exe <0x51,0x4d7cb>» … no corruption found.
Record 27 of 34: Corrupt File «…\nmbind.exe <0x4e,0x4d7cf>» … no corruption found.
Record 28 of 34: Corrupt File «…\nmbind.exe <0x36,0x4d7ce>» … no corruption found.
Record 29 of 34: Corrupt File «…\nvspinfo.exe <0x64,0x4d5b9>» … no corruption found.
Record 30 of 34: Corrupt File «…\nvspinfo.exe <0x40,0x4d5b8>» … no corruption found.
Record 31 of 34: Corrupt File «…\NetMgmtIF.dll <0x44,0x4deb3>» … no corruption found.
Record 32 of 34: Corrupt File «…\NetMgmtIF.dll <0x34,0x4deb2>» … no corruption found.
Record 33 of 34: Corrupt File «…\mshtml.dll <0x67,0x4ea60>» … no corruption found.
Record 34 of 34: Corrupt File «…\mshtml.dll <0x3a,0x4ea59>» … no corruption found.
34 corruption records processed in 0.1 seconds.
Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 1001
Record Number: 114223
Source Name: Microsoft-Windows-Wininit
Time Written: 04-18-2020 @ 08:13:00
Event Type: Information
User:
Message:
Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows 10 Pro x64.
A disk check has been scheduled.
Windows will now check the disk.
Stage 1: Examining basic file system structure …
756480 file records processed.
File verification completed.
7989 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage …
14085 reparse records processed.
946744 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
14085 reparse records processed.
Stage 3: Examining security descriptors …
Cleaning up 655 unused index entries from index $SII of file 0x9.
Cleaning up 655 unused index entries from index $SDH of file 0x9.
Cleaning up 655 unused security descriptors.
Security descriptor verification completed.
95132 data files processed.
CHKDSK is verifying Usn Journal…
40738816 USN bytes processed.
Usn Journal verification completed.
Stage 4: Looking for bad clusters in user file data …
756464 files processed.
File data verification completed.
Stage 5: Looking for bad, free clusters …
14181079 free clusters processed.
Free space verification is complete.
Windows has scanned the file system and found no problems.
No further action is required.
218250064 KB total disk space.
160446124 KB in 412170 files.
201588 KB in 95134 indexes.
0 KB in bad sectors.
878036 KB in use by the system.
65536 KB occupied by the log file.
56724316 KB available on disk.
4096 bytes in each allocation unit.
54562516 total allocation units on disk.
14181079 allocation units available on disk.
Internal Info:
00 8b 0b 00 5c bd 07 00 11 17 0a 00 00 00 00 00 ….\………..
85 30 00 00 80 06 00 00 00 00 00 00 00 00 00 00 .0…………..
Windows has finished checking your disk.
Please wait while your computer restarts.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26226
Record Number: 113982
Source Name: Chkdsk
Time Written: 04-18-2020 @ 05:14:38
Event Type: Information
User:
Message: Chkdsk was executed in scan mode on a volume snapshot.
Checking file system on C:
Volume label is Windows 10 Pro x64.
Stage 1: Examining basic file system structure …
756480 file records processed.
File verification completed.
7975 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage …
14080 reparse records processed.
949194 index entries processed.
Index verification completed.
14080 reparse records processed.
Stage 3: Examining security descriptors …
Security descriptor verification completed.
96357 data files processed.
CHKDSK is verifying Usn Journal…
34062232 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
218250064 KB total disk space.
160755912 KB in 412758 files.
201512 KB in 96359 indexes.
871352 KB in use by the system.
65536 KB occupied by the log file.
56421288 KB available on disk.
4096 bytes in each allocation unit.
54562516 total allocation units on disk.
14105322 allocation units available on disk.
———————————————————————-
Stage 1: Examining basic file system structure …
Stage 2: Examining file name linkage …
Stage 3: Examining security descriptors …
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 1001
Record Number: 97066
Source Name: Microsoft-Windows-Wininit
Time Written: 03-17-2020 @ 06:39:33
Event Type: Information
User:
Message:
Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows 10 Pro x64.
The volume is dirty.
Stage 1: Examining basic file system structure …
Deleted corrupt attribute list entry
with type code 80 in file 36C2.
Unable to find child frs 0x10919 with sequence number 0x36f.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x2d8640 for possibly 0x10 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x48bb9 is already in use.
Deleting corrupt attribute record (0x80, «»)
from file record segment 0x48BB9.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x2a6f60 for possibly 0x20 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x48c11 is already in use.
Deleting corrupt attribute record (0x80, «»)
from file record segment 0x48C11.
756480 file records processed.
File verification completed.
8016 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage …
Unable to locate the file name attribute of index entry $Deleted
of index $I30 with parent 0xb in file 0x13c.
Deleting index entry $Deleted in index $I30 of file B.
14053 reparse records processed.
The index bitmap $I30 is missing in file 0x144.
Correcting error in index $I30 for file 144.
The index bitmap $I30 in file 0xc16 is incorrect.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file C16.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0x2ffc is incorrect.
00 00 00 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ?? …………….
Correcting error in index $I30 for file 2FFC.
The index bitmap $I30 in file 0x2ffc is incorrect.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 2FFC.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 …………….
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ?? …………….
Sorting index $I30 in file 2FFC.
989186 index entries processed.
Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file Apps_{28a4b038-a7bc-43a4-a015-29eb3f15ba81} (2FFC) into directory file 1D4DE.
68 unindexed files scanned.
1 unindexed files recovered to original directory.
CHKDSK is recovering remaining unindexed files.
67 unindexed files recovered to lost and found.
Lost and found is located at \found.009
14053 reparse records processed.
Stage 3: Examining security descriptors …
Cleaning up 231 unused index entries from index $SII of file 0x9.
Cleaning up 231 unused index entries from index $SDH of file 0x9.
Cleaning up 231 unused security descriptors.
CHKDSK is compacting the security descriptor stream
Security descriptor verification completed.
Inserting data attribute into file 48BB9.
Inserting data attribute into file 48C11.
116355 data files processed.
CHKDSK is verifying Usn Journal…
Usn Journal verification completed.
Correcting errors in the master file table’s (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
No further action is required.
218250064 KB total disk space.
154017992 KB in 505200 files.
239000 KB in 116362 indexes.
0 KB in bad sectors.
834068 KB in use by the system.
65536 KB occupied by the log file.
63159004 KB available on disk.
4096 bytes in each allocation unit.
54562516 total allocation units on disk.
15789751 allocation units available on disk.
Internal Info:
00 8b 0b 00 a8 7b 09 00 13 3f 0c 00 00 00 00 00 …..{…?……
65 30 00 00 80 06 00 00 00 00 00 00 00 00 00 00 e0…………..
Windows has finished checking your disk.
Please wait while your computer restarts.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26226
Record Number: 97008
Source Name: Chkdsk
Time Written: 03-17-2020 @ 05:49:40
Event Type: Information
User:
Message: Chkdsk was executed in scan mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Stage 1: Examining basic file system structure …
Found corrupt basic file structure for «\Users\Donald\AppData\Roaming\ProcessLasso\logs\prolasso.log <0x1f9,0x36c2>»
… queued for offline repair.
Attribute record of type 0x80 and instance tag 0x0 is cross linked
starting at 0x2e6cc8 for possibly 0x6 clusters.
Found corrupt basic file structure for «\Users\Donald\AppData\Local\ConnectedDevicesPlatform\d3e1bdf5a9b69853\ActivitiesCache.db-wal <0xab,0x1ccc7>»
… queued for offline repair.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x2d8640 for possibly 0x10 clusters.
Found corrupt basic file structure for «\Windows\System32\LogFiles\WMI\Microsoft-Windows-Rdp-Graphics-RdpIdd-Trace.etl <0x78,0x48bb9>»
… queued for offline repair.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x2a6f60 for possibly 0x20 clusters.
Found corrupt basic file structure for «\Windows\System32\LogFiles\WMI\NetCore.etl <0x117,0x48c11>»
… queued for offline repair.
File «\Program Files (x86)\Adguard\langs\Adguard.UI.resources.uk.dll <0x317,0x3003>» and file «\Windows\System32\LogFiles\WMI\NetCore.etl <0x117,0x48c11>» both own logical clusters [0x2a6f60, 0x2a6f80)
… queued for offline repair.
File «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\DeviceSearchCache\AppCache132288954853345172.txt <0x299,0x3aac>» and file «\Windows\System32\LogFiles\WMI\Microsoft-Windows-Rdp-Graphics-RdpIdd-Trace.etl <0x78,0x48bb9>» both own logical clusters [0x2d8640, 0x2d864d)
… queued for offline repair.
756480 file records processed.
File verification completed.
8016 large file records processed.
Found unused file metadata marked as used
… queued for offline repair.
0 bad file records processed.
Stage 2: Examining file name linkage …
Found an unneeded link ($FILE_NAME: «$Deleted») in index «$I30» of directory «\$Extend <0xb,0xb>»
… repaired online.
14053 reparse records processed.
Found an unneeded link ($FILE_NAME: «19.232.1124[1].json») in index «$I30» of directory «\Users\Donald\AppData\Local\Microsoft\Windows\INetCache\IE\U3D3RAUQ <0x35b,0x999>»
… repaired online.
Found corruption in index «$I30» of directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\ConstraintIndex\Apps_{28a4b038-a7bc-43a4-a015-29eb3f15ba81} <0x194,0x2ffc>»
… queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 …………….
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ?? ÿÿÿÿÿÿÿÿ……..
Found a mis-ordered index «$I30» from directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\ConstraintIndex\Apps_{28a4b038-a7bc-43a4-a015-29eb3f15ba81} <0x194,0x2ffc>»
… queued for offline repair.
Found corruption in index «$I30» of directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\ConstraintIndex\Apps_{40abc29e-38b9-405a-9c6c-81678231b32c} <0x456,0x13f95>»
… queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 …………….
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ?? ÿÿÿÿÿÿÿÿ……..
Found a mis-ordered index «$I30» from directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\ConstraintIndex\Apps_{40abc29e-38b9-405a-9c6c-81678231b32c} <0x456,0x13f95>»
… queued for offline repair.
Found an unneeded link ($FILE_NAME: «prolasso.log.102») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.106») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.107») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.109») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.112») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.113») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.117») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.126») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.13») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.132») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.154») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.158») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.186») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.190») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.200») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.202») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.205») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.210») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.235») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.253») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.273») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.278») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.285») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.308») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.325») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.339») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.341») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.344») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.345») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.349») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.352») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.362») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.368») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.370») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.389») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.392») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.400») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.414») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.416») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.430») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.433») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.472») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.476») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.481») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.493») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.494») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.506») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.510») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.516») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.534») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.545») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.57») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.76») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.78») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.79») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.82») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.88») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.9») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «prolasso.log.93») in index «$I30» of directory «\Users\Donald\AppData\Roaming\ProcessLasso\logs <0x3a,0x14155>»
… repaired online.
Found an unneeded link ($FILE_NAME: «Apps_{6bd9172b-55e7-49c1-b538-19c2a0fb17e4}») in index «$I30» of directory «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\ConstraintIndex <0x3e,0x1d4de>»
… repaired online.
989174 index entries processed.
Index verification completed.
Found 5 lost files (\Users\Donald\AppData\Local\Microsoft\OneDrive\logs\Personal\TraceCurrent.1124.0008.etl <0x81d,0x134>, …); requesting reconnection to index «$I30» of directory «\Device\HarddiskVolume2\found.005»
… repaired online.
Found lost file «\Users\Donald\AppData\Local\Microsoft\OneDrive\logs\Personal\TraceArchive.1124.0008-846.etl <0xadd,0x68>»; requesting reconnection to index «$I30» of directory «\Users\Donald\AppData\Local\Microsoft\OneDrive\logs\Personal <0x3,0x65e94>»
… repaired online.
Found lost file «\Windows\SysWOW64\config\systemprofile\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\setup-7.4.3148.0.exe.log <0x1eb,0x36ab>»; requesting reconnection to index «$I30» of directory «\Windows\SysWOW64\config\systemprofile\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs <0x5,0x911d8>»
… repaired online.
Found 59 missing entries (\Users\Donald\AppData\Roaming\ProcessLasso\logs\prolasso.log.546 <0x559,0x13>, …) in index «$I30» of directory «\Users\Donald\AppData\Roaming\Proce
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26226
Record Number: 97006
Source Name: Chkdsk
Time Written: 03-17-2020 @ 05:48:46
Event Type: Information
User:
Message: Chkdsk was executed in scan mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Stage 1: Examining basic file system structure …
Found 0x19 clusters allocated to file «\Program Files (x86)\Adguard\langs\Adguard.UI.resources.pt-PT.dll <0x4dd,0xcb>» at offset «0» marked as free
… repaired online.
Found 0x1 clusters allocated to file «\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log <0xc87,0xd3>» at offset «0xce» marked as free
… repaired online.
Found 0x1 clusters allocated to file «\Users\Donald\AppData\Local\Microsoft\OneDrive\logs\Personal\TraceCurrent.1124.0008.etl <0x81d,0x134>» at offset «0» marked as free
… repaired online.
Found 0x1a clusters allocated to file «\Program Files (x86)\Adguard\langs\Adguard.UI.resources.ro.dll <0x233,0x1f6>» at offset «0» marked as free
… repaired online.
Found 0x19 clusters allocated to file «\Program Files (x86)\Adguard\langs\Adguard.UI.resources.pt.dll <0x12cd,0x2fa>» at offset «0» marked as free
… repaired online.
Found 0xa clusters allocated to file «\ProgramData\Connectify\logs\daemon.log <0x630,0x3b9>» at offset «0x56» marked as free
… repaired online.
Found 0x21 clusters allocated to file «\Program Files (x86)\Adguard\langs\Adguard.UI.resources.ru.dll <0x2f6,0x861>» at offset «0» marked as free
… repaired online.
Found 0x1b clusters allocated to file «\Program Files (x86)\Adguard\langs\Adguard.UI.resources.sk.dll <0x331,0xa83>» at offset «0» marked as free
… repaired online.
Found 0x1a clusters allocated to file «\Program Files (x86)\Adguard\langs\Adguard.UI.resources.sl.dll <0x30a,0xbdf>» at offset «0» marked as free
… repaired online.
Found 0x20 clusters allocated to file «\ProgramData\ESET\ESET Security\ScanCache\1183 <0x322,0xc16>» at offset «0x80» marked as free
… repaired online.
Found 0x1 clusters allocated to file «\ProgramData\regid.1991-06.com.microsoft\regid.1991-06.com.microsoft_Windows-10-Pro.swidtag <0x8fb,0xc3f>» at offset «0» marked as free
… repaired online.
Found 0x2 clusters allocated to file «\ProgramData\Connectify\settings\daemon.xml <0x1aa,0x1261>» at offset «0» marked as free
… repaired online.
Found 0x3 clusters allocated to file «\Users\Donald\AppData\Local\Microsoft\TokenBroker\Cache\5cf5be166e067049a447461d479ff8c6daa63a0f.tbres <0x3c6,0x12dc>» at offset «0» marked as free
… repaired online.
Found 0x3 clusters allocated to file «\Users\Donald\AppData\Local\Microsoft\TokenBroker\Cache\c645ac7329617bebf33ba7370a9247194ceb3131.tbres <0x3d7,0x1f12>» at offset «0» marked as free
… repaired online.
Found 0x19 clusters allocated to file «\Program Files (x86)\Adguard\langs\Adguard.UI.resources.sr.dll <0x3f1,0x271c>» at offset «0» marked as free
… repaired online.
Found 0x17 clusters allocated to file «\Program Files (x86)\Adguard\langs\Adguard.UI.resources.sv.dll <0x251,0x2f20>» at offset «0» marked as free
… repaired online.
Found 0x1a clusters allocated to file «\Program Files (x86)\Adguard\langs\Adguard.UI.resources.tr.dll <0x133,0x2f5b>» at offset «0» marked as free
… repaired online.
Found 0x1 clusters allocated to file «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\ConstraintIndex\Apps_{28a4b038-a7bc-43a4-a015-29eb3f15ba81} <0x194,0x2ffc>» at offset «0» marked as free
… repaired online.
Found 0x1 clusters allocated to file «\Windows\SysWOW64\config\systemprofile\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\setup-7.4.3148.0.exe.log <0x1eb,0x36ab>» at offset «0» marked as free
… repaired online.
Found corrupt basic file structure for «\Users\Donald\AppData\Roaming\ProcessLasso\logs\prolasso.log <0x1f9,0x36c2>»
… queued for offline repair.
Found 0xb clusters allocated to file «\Windows\Prefetch\ONEDRIVE.EXE-4F5C60FF.pf <0x12b,0x3968>» at offset «0» marked as free
… repaired online.
Found 0x1 clusters allocated to file «\ProgramData\Adguard\Logs\service\service_17-03-2020-1_08_14.841-2020-03-17.log <0x3ec,0x3975>» at offset «0x1» marked as free
… repaired online.
Found 0x1 clusters allocated to file «\ProgramData\Adguard\Logs\service\service_17-03-2020-1_08_14.841-2020-03-17.log <0x3ec,0x3975>» at offset «0x2» marked as free
… repaired online.
Found 0x10 clusters allocated to file «\Windows\System32\WDI\LogFiles\WdiContextLog.etl.003 <0x118,0xd38b>» at offset «0xc» marked as free
… repaired online.
Found 0x1 clusters allocated to file «\Windows\Panther\UnattendGC\diagerr.xml <0xaa,0x10a53>» at offset «0xef» marked as free
… repaired online.
Found 0x1 clusters allocated to file «\Users\Donald\AppData\Local\ConnectedDevicesPlatform\d3e1bdf5a9b69853\ActivitiesCache.db-wal <0xab,0x1ccc7>» at offset «0» marked as free
… repaired online.
Found 0x3 clusters allocated to file «\Users\Donald\AppData\Local\ConnectedDevicesPlatform\d3e1bdf5a9b69853\ActivitiesCache.db-wal <0xab,0x1ccc7>» at offset «0x1» marked as free
… repaired online.
Found 0x4 clusters allocated to file «\Users\Donald\AppData\Local\ConnectedDevicesPlatform\d3e1bdf5a9b69853\ActivitiesCache.db-wal <0xab,0x1ccc7>» at offset «0x4» marked as free
… repaired online.
Attribute record of type 0x80 and instance tag 0x0 is cross linked
starting at 0x2e6cc8 for possibly 0x6 clusters.
Found corrupt basic file structure for «\Users\Donald\AppData\Local\ConnectedDevicesPlatform\d3e1bdf5a9b69853\ActivitiesCache.db-wal <0xab,0x1ccc7>»
… queued for offline repair.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x2d8640 for possibly 0x10 clusters.
Found corrupt basic file structure for «\Windows\System32\LogFiles\WMI\Microsoft-Windows-Rdp-Graphics-RdpIdd-Trace.etl <0x78,0x48bb9>»
… queued for offline repair.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x2a6f60 for possibly 0x20 clusters.
Found corrupt basic file structure for «\Windows\System32\LogFiles\WMI\NetCore.etl <0x117,0x48c11>»
… queued for offline repair.
File «\Program Files (x86)\Adguard\langs\Adguard.UI.resources.uk.dll <0x317,0x3003>» and file «\Windows\System32\LogFiles\WMI\NetCore.etl <0x117,0x48c11>» both own logical clusters [0x2a6f60, 0x2a6f80)
… queued for offline repair.
File «\Users\Donald\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\DeviceSearchCache\AppCache132288954853345172.txt <0x299,0x3aac>» and file «\Windows\System32\LogFiles\WMI\Microsoft-Windows-Rdp-Graphics-RdpIdd-Trace.etl <0x78,0x48bb9>» both own logical clusters [0x2d8640, 0x2d864d)
… queued for offline repair.
756480 file records processed.
File verification completed.
«Chkdsk /scan» has found and repaired critical volume bitmap corruption online and must restart the scan.
———————————————————————-
Stage 1: Examining basic file system structure …
Deleted corrupt attribute list entry
with type code 80 in file 36C2.
Unable to find child frs 0x10919 with sequence number 0x36f.
Some clusters occupied by attribute of type 0x80 and instance tag 0x0
in file 0x1ccc7 is already in use.
Deleted corrupt attribute list entry
with type code 80 in file 1CCC7.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x32f000000000fe3. The expected attribute type is 0x80.
Deleting corrupt attribute record (0x80, «»)
from file record segment 0xFE3.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x48bb9 is already in use.
Deleting corrupt attribute record (0x80, «»)
from file record segment 0x48BB9.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x48c11 is already in use.
Deleting corrupt attribute record (0x80, «»)
from file record segment 0x48C11.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 96981
Source Name: Chkdsk
Time Written: 03-17-2020 @ 05:11:47
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 3 corruption records …
Record 1 of 3: Corrupt File «\Users\Donald\AppData\Local\Microsoft\OneDrive\logs\Personal\TraceArchive.1124.0008-846.etl <0xadd,0x68>» … no corruption found.
Record 2 of 3: Unneeded index entry in index «$I30» of directory «\Users\Donald\AppData\Local\Microsoft\OneDrive\logs\Personal <0x3,0x65e94>» … no corruption found.
Record 3 of 3: Corrupt File «<0x81c,0x134>» … no corruption found.
3 corruption records processed in 0.1 seconds.
Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 96980
Source Name: Chkdsk
Time Written: 03-17-2020 @ 05:11:42
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 2 corruption records …
Record 1 of 2: Corrupt File «<0x385,0x1fe0b>» … no corruption found.
Record 2 of 2: Corrupt File «<0x32a,0x2369f>» … no corruption found.
2 corruption records processed in 0.1 seconds.
Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 96979
Source Name: Chkdsk
Time Written: 03-17-2020 @ 05:11:37
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 1 corruption record …
Record 1 of 1: Corrupt File «<0x3b1,0x36f>» … no corruption found.
1 corruption record processed in 0.1 seconds.
Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 96978
Source Name: Chkdsk
Time Written: 03-17-2020 @ 05:11:32
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 1 corruption record …
Record 1 of 1: Corrupt File «<0x4dc,0xcb>» … no corruption found.
1 corruption record processed in 0.1 seconds.
Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 96977
Source Name: Chkdsk
Time Written: 03-17-2020 @ 05:11:26
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 2 corruption records …
Record 1 of 2: Corrupt File «<0x8fa,0xc3f>» … no corruption found.
Record 2 of 2: Corrupt File «<0x3c5,0x12dc>» … no corruption found.
2 corruption records processed in 0.1 seconds.
Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 96975
Source Name: Chkdsk
Time Written: 03-17-2020 @ 05:11:20
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 2 corruption records …
Record 1 of 2: Corrupt File «<0x2d0,0x586c>» … no corruption found.
Record 2 of 2: Corrupt File «<0x52e,0x5907>» … no corruption found.
2 corruption records processed in 0.1 seconds.
Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 96963
Source Name: Chkdsk
Time Written: 03-17-2020 @ 05:11:14
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 2 corruption records …
Record 1 of 2: Corrupt File «<0x1e3,0x36ab>» … no corruption found.
Record 2 of 2: Corrupt File «<0x129,0x3968>» … no corruption found.
2 corruption records processed in 0.1 seconds.
Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.
————————————————————————
Category: 0
Computer Name: Laptop
Event Code: 26228
Record Number: 96959
Source Name: Chkdsk
Time Written: 03-17-2020 @ 05:11:08
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.
Checking file system on \Device\HarddiskVolume2
Volume label is Windows 10 Pro x64.
Examining 4 corruption records …
Record 1 of 4: Corrupt File «<0x3d6,0x1f12>» … no corruption found.
Record 2 of 4: Corrupt File «<0x206,0x7f83>» … no corruption found.
Record 3 of 4: Corrupt File «<0x14b,0x21ca2>» … no corruption found.
Record 4 of 4: Corrupt File «\Users\Donald\AppData\Roaming\ProcessLasso\logs\prolasso.log <0x1f9,0x36c2>» … Attribute list entry with type code 80 in file 36C2 is corrupt.
Unable to find child frs 0x10919 with sequence number 0x36f.
corruption found.
4 corruption records processed in 0.1 seconds.
Windows has examined the list of previously identified potential issues and found problems.
Please run chkdsk /scan to fully analyze the problems and queue them for repair.
————————————————————————
SleepyDude
Windows Update Moderator, Security Analyst
- Joined
- Dec 20, 2013
- Posts
- 3,062
- Location
-
Portugal
-
-
#20
I think before doing more repairs you should do some more tests to find out why there are those errors!
Is the SSD old? what is the brand and mode of the SSD?
Running a memory test is also a good idea…
Create a bootable flash drive to test the RAM.
- Create a folder named MemTest86 on the Desktop or in another place you choose
- Download MemTest86 and save to the folder MemTest86
- Extract the ZIP file, right-click memtest86-usb.zip and click Extract All follow the prompts
- Connect the flash drive and make sure its empty because all the contents *will be deleted*
- From the extracted files execute imageUSB.exe
- In Step 1 make sure you select your flash drive
- In Step 2 click Write to UFD
- In Step 3 should be filled automatically with the full path to the memtest86-usb.img file
- In Step 4 click the button Write to UFD
- Restart the computer and make sure it boot from the flash drive
Some computers for example from Dell have built-in diagnostic test on the BIOS/UEFI that you can run.
Has Sysnative Forums helped you? Please consider donating to help us support the site!
-
Microsoft Support & Malware Removal
-
Windows Update