Служба Windows Error Reporting (WER) служит для сбора и отправки отладочной информации о падении системных и сторонних приложений в Windows на сервера Microsoft. По задумке Microsoft, эта информация должна анализироваться и при наличии решения, вариант исправления проблемы должен отправляется пользователю через Windows Error Reporting Response. Но по факту мало кто пользуется этим функционалом, хотя Microsoft настойчиво оставляет службу сбора ошибок WER включенной по умолчанию во всех последних версиях Windows. В большинстве случае о службе WER вспоминают, когда каталог C:\ProgramData\Microsoft\Windows\WER\ReportQueue\ начинает занимать много места на системном диске (вплоть до нескольких десятков Гб), даже не смотря на то что на этом каталоге по умолчанию включена NTFS компрессия.
Содержание:
- Служба Windows Error Reporting
- Очистка папки WER\ReportQueue в Windows
- Отключение Window Error Reporting в Windows Server
- Отключаем сбор и отправки отчетов об ошибках в Windows 10
- Отключение Windows Error Reporting через GPO
Служба Windows Error Reporting
Служба Windows Error Reporting при появлении ошибки показывает диалоговое окно, предлагающее отправить отчет об ошибке в корпорацию Microsoft. Когда в Windows вы видите сообщение об ошибке
YourApp has stop working
, в это время в служба Windows Error Reporting запускает утилиту WerFault.exe для сбора отладочных данных (могут включать в себя дамп памяти).
Данные пользователя сохраняются в профиль пользователя:
%USERPROFILE%\AppData\Local\Microsoft\Windows\wer
Системные данные – в системный каталог:
%ALLUSERSPROFILE%\Microsoft\Windows\WER\
Служба Windows Error Reporting представляет собой отдельный сервис Windows. Вы можете проверить состояние службы командой PowerShell:
Get-Service WerSvc
Внутри каталога WER\ReportQueue\ содержится множество каталогов, с именами в формате:
- Critical_6.3.9600.18384_{ID}_00000000_cab_3222bf78
- Critical_powershell.exe_{ID}_cab_271e13c0
- Critical_sqlservr.exe__{ID}_cab_b3a19651
- NonCritical_7.9.9600.18235__{ID}_0bfcb07a
- AppCrash_cmd.exe_{ID}_bda769bf_37d3b403
Как вы видите, имя каталога содержит степень критичности события и имя конкретного exe файла, который завершился аварийно. Во всех каталогах обязательно имеется файл Report.wer, который содержит описание ошибок и несколько файлов с дополнительной информацией.
Очистка папки WER\ReportQueue в Windows
Как правило, размер каждой папки в WER незначителен, но в некоторых случаях для проблемного процесса генерируется дамп памяти, который занимает довольно много места. На скриншоте ниже видно, что размер файла дампа memory.hdmp составляет около 610 Мб. Парочка таким дампов – и на диске исчезло несколько свободных гигибайт.
Чтобы очистить все эти ошибки и журналы штатными средствами, откройте панель управления и перейдите в раздел ControlPanel -> System and Security -> Security and Maintenance -> Maintenance -> View reliability history -> View all problem reports (Control Panel\System and Security\Security and Maintenance\Problem Reports) и нажмите на кнопку Clear all problem reports.
Для быстрого освобождения места на диске от файлов отладки, сгенерированных службой WER, содержимое следующих каталогов можно безболезненно очистить вручную.
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive\
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue\
Следующие команды PowerShell удалят из каталога каталогов WER все файлы, старше 15 дней:
Get-ChildItem -Path 'C:\ProgramData\Microsoft\Windows\WER\ReportArchive' -Recurse | Where-Object CreationTime -lt (Get-Date).AddDays(-15) | Remove-Item -force -Recurse
Get-ChildItem -Path 'C:\ProgramData\Microsoft\Windows\WER\ReportQueue' -Recurse | Where-Object CreationTime -lt (Get-Date).AddDays(-15) | Remove-Item -force –Recurse
Для очистки каталогов WER в пользовательских профилях используйте такой скрипт:
$users = Get-ChildItem c:\users|where{$_.name -notmatch 'Public|default'}
foreach ($user in $users){
Get-ChildItem "C:\Users\$User\AppData\Local\Microsoft\Windows\WER\ " –Recurse -ErrorAction SilentlyContinue | Remove-Item –force –Recurse
}
Отключение Window Error Reporting в Windows Server
В Windows Server 2019/2016/2012R2 вы можете управлять состоянием WER с помощью PowerShell. Вы можете отключить службу Windows Error Reporting:
Get-Service WerSvc| stop-service –passthru -force
Set-Service WerSvc –startuptype manual –passthru
Но есть более корректные способы отключения WER в Windows. В версии PowerShell 4.0 добавлен отдельный модуль WindowsErrorReporting из трех командлетов:
Get-Command -Module WindowsErrorReporting
Проверить состояние службы Windows Error Reporting можно командой:
Get-WindowsErrorReporting
Для отключения WER, выполните:
Disable-WindowsErrorReporting
В Windows Server 2012 R2 можно отключить запись информации об ошибках Windows Error Reporting через панель управления (Control Panel -> System and Security -> Action Center -> раздел Maintenance -> Settings -> выберите опцию I don’t want to participate, and don’t ask me again
Отключаем сбор и отправки отчетов об ошибках в Windows 10
В Windows 10 нельзя отключить Error Reporting через панель управления. В графическогм интерфейсе можно только проверить ее статус (Система и безопасность ->Центр безопасности и обслуживания -> секция Обслуживание). Как вы видите, по умолчанию параметр Поиск решения для указанных в отчетах проблем включен (Control Panel -> System and Security -> Security and Maintenance -> Maintenance -> Report problems = On).
HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting нужно создать новый параметр типа DWORD (32 бита) с именем Disabled и значением 1.
Можно отключить сбор ошибок WER для конкретных пользователей:
reg add "HKCU\Software\Microsoft\Windows\Windows Error Reporting" /v "Disabled" /t REG_DWORD /d "1" /f
Или отключить WER для всех:
reg add "HKLM\Software\Microsoft\Windows\Windows Error Reporting" /v "Disabled" /t REG_DWORD /d "1" /f
Измените параметр реестра и проверьте статус параметра Поиск решения для указанных в отчетах проблем в панели управления. Его статус должен изменится на Отключено.
Отключение Windows Error Reporting через GPO
Также вы можете управлять настройками службы Windows Error Reporting через групповые политики.
Запустите редактор локальной (
gpedit.msc
) или доменной GPO (
gpmc.msc
) и перейдите в ветку реестра Computer Configuration -> Administrative Templates -> Windows Components -> Windows Error Reporting (Компоненты Windows -> Отчеты об ошибках Windows). Для отключения сбора и отправки ошибок через WER включите политику Disable Windows Error Reporting (Отключить отчеты об ошибках Windows).
Аналогичная политика есть в пользовательском разделе политик (User Configuration).
Обновите GPO (перезагрузка не потребуется).
В результате в Windows перестанут формироваться сообщения об ошибках Windows и отправляться в Microsoft.
The Windows Error Reporting service (WER) is used to collect the debug information about system and third-party app failures and send error reports to Microsoft servers. This information should be analyzed by MSFT and if there is a solution, it will be sent to a user through Windows Error Reporting Response. Actually, few people use this feature, although Microsoft always leaves the WER service enabled by default in the latest Windows versions. In most cases, people remember about WER when they see that C:\ProgramData\Microsoft\Windows\WER\ReportQueue\ occupies much space on the system drive (up to several dozens of GB) even though NTFS compression is enabled for this directory by default.
Contents:
- Windows Error Reporting Service
- How to Clear the WER\ReportQueue Folder on Windows?
- Disable Windows Error Reporting on Windows Server
- How to Disable or Enable Error Reporting on Windows 10
- How to Disable Automatic Windows Error Reporting via GPO
Windows Error Reporting Service
Windows Error Reporting displays a dialog box when an application error occurs, prompting you to submit an error report to Microsoft. When you see the “YourAppName.exe has stopped working, Windows is collecting more information about the problem” error message in Windows, the Windows Error Reporting service runs the WerFault.exe tool to collect debug data (may include a memory dump).
User data is saved to the user profile:
%USERPROFILE%\AppData\Local\Microsoft\Windows\WER\
And the system data goes to the ProgramData directory:
%ALLUSERSPROFILE%\Microsoft\Windows\WER\
The Windows Error Reporting service is a separate Windows service. You can check the status of the service using the PowerShell command:
Get-Service WerSvc
In the WER\ReportQueue\ directory there are a lot of folders with the names in the following format:
- Critical_6.3.9600.11285_{ID}_00000000_cab_3212dd23
- Critical_powershell.exe_{ID}_cab_332a45c5
- Critical_sqlservr.exe__{ID}_cab_b3a200181
- NonCritical_7.9.9600.11285__{ID}_0bfab19a
- AppCrash_cmd.exe_{ID}_dba332ad_12eb5425
As you can see, the directory name contains the severity level of an event and the name of the specific EXE file that has crashed. In all folders, there is a file called Report.wer, which contains the description of the errors and some files with the additional information.
How to Clear the WER\ReportQueue Folder on Windows?
Typically, the size of each folder is small, but in some cases a memory dump is generated for a problem process that occupies much space. The screenshot below shows that the size of memory.hdmp is about 610 MB. A couple of such dumps can occupy several gigabytes of the system drive.
To clear all these errors and logs using the built-in tools, open the Control Panel and go to System and Security -> Security and Maintenance -> Maintenance -> View reliability history -> View all problem reports, then click Clear all problem reports.
To free up some disk space quickly, you can manually delete debug and log files generated by the WER service in the following folders:
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive\
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue\
The following PowerShell commands will remove all files older than 30 days from the WER directories:
Get-ChildItem -Path 'C:\ProgramData\Microsoft\Windows\WER\ReportArchive' -Recurse | Where-Object CreationTime -lt (Get-Date).AddDays(-30) | Remove-Item -Force -Recurse
Get-ChildItem -Path 'C:\ProgramData\Microsoft\Windows\WER\ReportQueue' -Recurse | Where-Object CreationTime -lt (Get-Date).AddDays(-30) | Remove-Item -Force –Recurse
To clean up the WER directories in all user profiles, use the following PowerShell script:
$users = Get-ChildItem c:\users|where{$_.name -notmatch 'Public|default'}
foreach ($user in $users){
Get-ChildItem "C:\Users\$User\AppData\Local\Microsoft\Windows\WER\ " –Recurse -ErrorAction SilentlyContinue | Remove-Item –force –Recurse
}
Disable Windows Error Reporting on Windows Server
On Windows Server 2019/2016/2012R2, you can manage the WER service state using PowerShell. You can disable the Windows Error Reporting service:
Get-Service WerSvc| stop-service –passthru -force
Set-Service WerSvc –startuptype manual –passthru
You can disable WER on Windows using the built-in WindowsErrorReporting PowerShell module:
Get-Command -Module WindowsErrorReporting
You can check the status of the Windows Error Reporting service with the command:
Get-WindowsErrorReporting
To disable WER, run:
Disable-WindowsErrorReporting
On Windows Server 2012 R2 you can disable Windows Error Reporting via the control panel (Control Panel -> System and Security -> Action Center -> Maintenance -> Settings -> select I don’t want to participate, and don’t ask me again.
How to Disable or Enable Error Reporting on Windows 10
In Windows 10 you cannot disable the Error Reporting through the Control Panel. You can check the component status in the Control Panel -> System & Security -> Security and Maintenance -> Maintenance. As you can see, the Report problems parameter is enabled.
You can disable Windows Error Reporting on Windows 10 via the registry. To do it, create a new DWORD (32-bit) parameter with the name Disabled and the value 1 under the registry key HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting.
You can disable Windows error collection for specific users with the command:
reg add "HKCU\Software\Microsoft\Windows\Windows Error Reporting" /v "Disabled" /t REG_DWORD /d "1" /f
Or disable WER for everyone:
reg add "HKLM\Software\Microsoft\Windows\Windows Error Reporting" /v "Disabled" /t REG_DWORD /d "1" /f
Now let’s check the status of the Report problems parameter in the Control Panel again. It should be Off.
How to Disable Automatic Windows Error Reporting via GPO
You can disable logging by the Windows Error Reporting service through Group Policy. Open the local (gpedit.msc) or domain GPO (gpmc.msc) editor and go to the following GPO section Computer Configuration -> Administrative Templates -> Windows Components -> Windows Error Reporting. Find the policy named Disable Windows Error Reporting and set it to Enabled. This will disable Windows data collection and error reporting.
There is a similar policy in the User Configuration section.
Update the GPO settings (no reboot required).
As a result, Windows will no longer generate application and system error messages and will no longer be sent to Microsoft.
| Автор | Сообщение | ||
|---|---|---|---|
|
|||
|
Member Статус: Не в сети |
Месяца 3 назад поставил Висту. Сегодня навёл ревизию распухших папок. В упомянутой было 2 Гб какого-то хлама и содержалось почти 3 десятка папок с назваием типа этого — Report050c7842. Рискнул удалить — ничего не случилось |
| Реклама | |
|
Партнер |
|
HertZ |
|
|
Advanced member Статус: Не в сети |
Отчеты об ошибках, содержимое каталогов можно грохнуть. |
|
Vladimir R |
|
|
Member Статус: Не в сети |
Понял. Очистил всё. А нельзя ли отключить составление этих отчётов? |
|
Sanches_95 |
|
|
Member Статус: Не в сети |
Vladimir R писал(а): Понял. Очистил всё. А нельзя ли отключить составление этих отчётов? Актуально |
|
Yubi |
|
|
Member Статус: Не в сети |
Sanches_95 писал(а): Актуально Удобнее всего его чистить в «очистке диска», а вот отключить — это вряд ли |
|
Sanches_95 |
|
|
Member Статус: Не в сети |
Yubi Очистка диска эти папки вообще не трогает |
|
Yubi |
|
|
Member Статус: Не в сети |
Sanches_95 писал(а): Очистка диска эти папки вообще не трогает У меня в Windows 7 еще как трогает |
|
smolvill |
|
|
Member Статус: Не в сети |
Yubi писал(а): У меня в Windows 7 еще как трогает согласен, у меня на 7 очистка тоже все грохает |
|
Sanches_95 |
|
|
Member Статус: Не в сети |
Странно, т.к. когда я выбираю св-ва диска С и очистку диска, она находит обычно 15-30мб мусора, 95% из которых составляют эскизы |
|
evadminka |
|
|
Junior Статус: Не в сети |
столкнулась с той же бедой на 2008м терминальном сервере. нашла в тему интересную ссылочку https://msdn.microsoft.com/en-us/librar … 85%29.aspx а так же кто-то пробовал отключать опцию по данному пути Control Panel\All Control Panel Items\Action Center\Problem Reporting Settings |
|
yura_1988 |
|
|
Junior Статус: Не в сети |
приветствую всех. заранее сорян за поднятие старой темы. |
—
Кто сейчас на конференции |
|
Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 6 |
| Вы не можете начинать темы Вы не можете отвечать на сообщения Вы не можете редактировать свои сообщения Вы не можете удалять свои сообщения Вы не можете добавлять вложения |
Some users report that they are unable to delete the System queued Windows Error Reporting File when trying to free up some space using Disk Cleanup. This might not seem like a big deal, but some affected users report that this file is growing in size with each passing week and there’s no apparent way to get rid of it.
This particular issue is often reported on Windows 7, Windows 8 and Windows 10. There are some cases where the System queued Windows Error Reporting File was reported to have over 200 GB in size.
System queued Windows Error Report files are used for error reporting and solution checking in all recent Windows version. While their deletion will not affect the normal functionality of your OS, removing them might prevent built-in troubleshooters and other utilities from applying the correct repair strategy.
What’s causing the System Queued Windows Error Reporting files issue?
After looking at various user reports and trying to replicate the issue, we noticed a few scenarios that were often confirmed to be responsible for the apparition of this issue. Here’s a list with culprits that are most likely causing this odd behavior:
- Disk Cleanup doesn’t have administrative privileges – This is known to happen when the user tries to run disk cleanup without granting admin access to the utility.
- Disk Cleanup utility is glitched – In this particular case, you have the option of navigating to the location of the files and delete them manually.
- Windows 7 and 8 log file compression bug – Windows 7 has a long-standing bug in the Trusted Installer log that can cause your hard drive to fill up for no apparent reason.
How to delete the System Queued Windows Error Reporting files
If you’re struggling to resolve this particular issue, this article will show you a few repair strategies that others have found helpful. Below you have a collection of methods that other users in a similar situation have used to get the issue resolved.
For the best results, start with the first methods and if it’s ineffective, move down to the next ones in order until you encounter a fix that is successful in resolving the issue for your particular scenario. Let’s begin!
Method 1: Run Disk Cleanup with administrative privileges
In the vast majority of cases, the issue is caused by a privilege issue. A lot of users have reported that the issue was fixed as soon as they opened the Disk Cleanup utility with administrative privileges.
As it turns out, Disk Cleanup will be unable to remove a couple of system files unless the user grants it admin access. Here’s a quick guide on how to do so:
- Press Windows key + R to open up a Run dialog box. Next, type “cleanmgr” and press Ctrl + Shift + Enter to open Disk Cleanup with administrative privileges.
Run dialog: cleanmgr - When prompted by the UAC (User Account Control), choose Yes to accept.
- Now, select the System Queued Windows Error Reporting Files and schedule them for cleanup. You should be able to delete them without issue.
If you’re still encountering the same issue, continue down with the next method below.
Method 2: Deleting the files manually
If the first method is not effective, you might have better luck by deleting the System queued Windows Error Reporting files manually. Some users have reported that the System queued Windows Error Reporting Files where gone from Disk Cleanup after they manually browsed and delete them from their locations.
Here’s a quick guide on how to do this:
- Press Windows key + R to open up a Run dialog box. Then, paste “%ALLUSERSPROFILE%\Microsoft\Windows\WER\ReportQueue” and hit Enter to open up the Report Queue folder.
Run dialog: %ALLUSERSPROFILE%\Microsoft\Windows\WER\ReportQueue Note: If this command is not recognized, try this one instead: “%USERPROFILE%\AppData\Local\Microsoft\Windows\WER\ReportQueue“
- If you manage to find any subfolders or files in this folder, delete them immediately and empty your Recycle Bin.
- Reboot your machine and return to the Disk Cleanup utility at the next startup. You should no longer see any System queued Windows Error Reporting files recommended for deletion.
If this method wasn’t effective, continue down with the next method below.
Method 3: Resolving the Windows 7 and 8 log bug
If you’re encountering this issue on Windows 7 and Windows 8, you should know that Microsoft has had this bug for a couple of years for now without releasing a hotfix.
Whenever this bug occurs, a series of log files will grow to an enormous size. But what’s even worse is that even if you delete those logs, Windows will kick in and start generating those files again (often times more aggressive than before) until you run out of space.
Luckily, there’s one manual fix that seems to have helped a lot of users to resolve the issue permanently. This method involves stopping the Windows Modules Installer service and renaming all logs to stop Windows from choking on oversized log files. Here’s a quick guide through the whole thing:
- Press Windows key + R to open up a Run dialog box. Then, type “services.msc” and press Enter to open up the Services screen. If prompted by the UAC (User Account Control), choose Yes.
Run dialog: services.msc - Inside the Services screen, scroll down through the list of services to locate the Windows Modules Installer service. Once you do so, double-click on it to open the Properties menu.
- Once you’re inside the properties menu, go to the General tab and click on Stop to turn off the Windows Modules Installer service (under Service status).
Stop Windows Modules Installer service - Open File Explorer and navigate to C:\ Windows \ Logs \ CBS
Note: If Windows is installed on a different drive, adapt the location accordingly. - In the CBS folder, move or rename all files. You can rename it anything as long as you preserve the “.log” extension.
Rename all logs - When prompted by the UAC (User Account Control), choose Yes
- Navigate to C:\ Windows \ Temp and delete all “.cab” files that are currently residing in the Temp folder.
- Restart your computer and return to the Disk Cleanup utility at the next startup. You should no longer see a big System queued Windows Error Reporting entry.
If this particular method didn’t allow you to resolve the issue, move down to the final method below.
Method 4: Perform a repair install
If none of the methods above have allowed you to get the issue resolved, we’re down to the last resort. Given the fact that all the popular fixes presented above have failed, it’s very likely that the issue is caused by an underlying system file corruption.
There are a few ways to try and fix system file corruption, but we recommend doing a Repair install since it’s faster and will most likely produce the expected results.
A repair install will replace all Windows-related component with fresh copies while allowing you to keep all your personal files including media, documents, and applications. If you decide to do a repair install, follow our step by step guide (here).
Kevin Arrows
Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.
-
Home
-
Partition Manager
- How to Delete System Queued Windows Error Reporting Files
By Amanda |
Last Updated
Sometimes, you might find that the system queued Windows Error Reporting Files is huge and you want to delete it to free up disk space. In this article, MiniTool Partition Wizard will show you how to delete huge system queued Windows Error Reporting files with 3 different methods.
About System Queued Windows Error Reporting Files
The system queued Windows Error Reporting Files are used by Microsoft Windows for error reporting and solution checking.
These files contain the error reports related to the software and hardware problems and are stored temporarily in the system. They are generated by your Windows system and will be sent back to Microsoft for solutions to those problems. And Microsoft may include fixes for reported problems in the future updates according to the feedback.
But with time going on, these files may take lots of space on your system, and many Windows users have reported the system queued Windows Error Reporting huge issue. So, you may want to remove these files to free up the disk space.
Actually, the normal functioning of your OS won’t be affected if you delete system queued Windows Error Reporting Files. But you should know that removing them may prevent built-in troubleshooters and other utilities from applying the correct repair strategy.
If you have decided to remove them, just keep on your reading to get the methods.
How to Delete System Queued Windows Error Reporting Files
You can choose to delete system queued Windows Error Reporting Files using Disk Cleanup or Windows Settings, or delete manually. The detailed instructions are listed below.
Method 1: Make Use of Disk Cleanup Utility
Disk Cleanup is a Windows built-in tool that can help you delete part or even all of unnecessary files. To delete system queued Windows Error Reporting Files using this utility, just follow the steps below:
Step 1: Press Windows + S, input disk cleanup, and click the result to open the utility.
Step 2: Select your system drive (commonly C: drive) and click OK button. This tool will start scanning your drive and calculating how much space you will be able to free.
Step 3: Click the Clean up system files button in the lower-left corner and repeat the step 2.
Step 4: Check the System created Windows Error Reporting Files and other items you want to remove, and click OK button. In the confirmation prompt, click Delete Files button to remove the files permanently.
Some users complain that they cannot delete the files in Disk Cleanup. If you are facing the same problem, try running Disk Cleanup as administrator and doing the same operations introduced above. Alternatively, you can jump to the next method.
Related article: What Is Safe to Delete in Disk Cleanup? Here Is the Answer
Method 2: Use Windows Settings App
You can also delete Windows Error Reporting files in Windows Settings. Here’s what you need to do.
Step 1: Right-click the Start button and choose Settings to open it.
Step 2: Navigate to System > Storage and click Free up space now in the right pane.
Step 3: Wait patiently until the scanning process is completed. Select System created Windows Error Reporting Files and scroll the page to the top to click Remove files.
Method 3: Delete the Files Manually
Alternatively, you can also choose to delete the Windows Error Reporting (WER) files manually in File Explorer. In this way, you don’t need to spend time on waiting for the scanning process.
Step 1: Press Windows + E to open File Explorer. Go to the View tab and check Hidden items.
Step 2: Copy and paste the path C:ProgramDataMicrosoftWindowsWER to the upper search bar in File Explorer and press Enter key to locate the WER folder.
Step 3: You will see several folders here. Now open each of them and delete all their contents.
Step 4: Go to empty your Recycle Bin to delete the system queued Windows Error Reporting Files permanently.
About The Author
Position: Columnist
Amanda has been working as English editor for the MiniTool team since she was graduated from university. She enjoys sharing effective solutions and her own experience to help readers fix various issues with computers, dedicated to make their tech life easier and more enjoyable.
Amanda has published many articles, covering fields of data recovery, partition management, disk backup, and etc. In order to provide more useful tips and information, she is still committed to expand her technical knowledge.