Configure Windows 10 to create Dump Files on Blue Screen of Death

Every computer has to have a graphic card, it is one of the essential components in order for the computer to work. If you have a second-hand computer, got one as a gift, or similar, there is a high chance that you do not really know which components are inside. Luckily finding out which graphic card you have inside is quite easy. Right-click the taskbar and select Task Manager Click the Performance tab at the top of the window, if you don’t see the tabs, click “More Info.” Select “GPU 0” in the sidebar. The GPU’s manufacturer and model names are displayed at the top right corner of the window. You’ll also see other information, such as the amount of dedicated memory on your GPU, in this window. Windows 10’s Task Manager displays your GPU usage here, and you can also view GPU usage by application. If your system has multiple GPUs, you’ll also see “GPU 1” and so on here. Each represents a different physical GPU.

Microsoft just released Windows 11 Insider build 22000.71. Let’s dive in and see what it brings with you.

Changes and features

New entertainment widget. The entertainment widget allows you to see new and featured movie titles available in the Microsoft Store. Selecting a movie will direct you to the Microsoft Store to see more information about that title. Just open widgets and click or tap on the “Add widgets” button and choose the entertainment widget. For now, the entertainment widget is available for Insiders in the following countries: US, UK, CA, DE, FR, AU, JP. The new context menus and other right-click menus have been updated to use acrylic material. We are testing the usability of a SplitButton for making new folders and files in the File Explorer command bar. The Taskbar previews (when you mouse-over open apps on the Taskbar) have been updated to reflect the new visual design of Windows 11.

Fixes

Taskbar:

• We fixed an issue where if you drag app icons on the Taskbar to rearrange them, it was making the apps launch or minimize when you released the icon.
• Using a long press with a touch on an app icon in the Taskbar to open the jump list should now work.
• After right-clicking the Start icon in the Taskbar, clicking somewhere else should now dismiss the menu more reliably.
• Shift + Right-click on an app icon in the Taskbar will now bring up the window menu like it used to and not the jump list.
• We’ve addressed an issue that was making your mouse move slowly when hovering over the Taskbar previews.
• We’ve included the fix for an issue when using multiple Desktops where an app icon in the taskbar might give the appearance of multiple windows being open when that wasn’t the case on that Desktop.
• When using the Amharic IME you should no longer see an unexpected X next to the IME icon in the taskbar.
• The issue where if you click on the input indicator on the Taskbar and it would unexpectedly highlight Quick Settings has been fixed.
• When you hover over Task View, the preview flyout for your Desktops will no longer pop back up after using Esc to dismiss them.
• We made a fix to address an issue where explorer.exe might crash after hovering over the Task View icon in the Taskbar.
• We fixed an issue where the selected date in the calendar flyout was out of sync with the date in the Taskbar.
• We made an update to address a scenario resulting in some Insiders not seeing the lunar calendar text in the calendar flyout when enabled in Settings.
• This flight addressed an issue that could unexpectedly make the Taskbar background transparent.
• Right-clicking the focus assist icon in the taskbar should now show a context menu.
• The issue from the previous flight where icons in the taskbar corner were getting crushed against the top of the Taskbar has been addressed.
• The tooltip for the location in use icon in the Taskbar should no longer appear blank sometimes.

Settings:

• We fixed an issue making Settings crash on launch periodically.
• Using the volume mixer sliders in Sound Settings should be more responsive now, as well as the page responsiveness as a whole.
• We fixed an issue resulting in Disk and Volumes Settings’ change size option being clipped.
• There was a non-functional verify link under Backup Settings – this has been fixed.
• The Power and Battery Settings page should no longer be reporting that the battery saver is engaged if it’s not.
• The Power and Battery Settings page should also now not crash when launched from Quick Settings.
• We fixed a grammatical error in the Sign-in Settings text.
• The “I forgot my PIN” link was unexpectedly missing in Sign-in Settings when a PIN was set up and has now been returned.
• The issue where the Move option under Apps & Features in Settings wasn’t working reliably should be addressed in this build.
• We’ve mitigated a problem where some of the colors in Settings weren’t updating after switching between dark and light mode, leaving the unreadable text.
• We’ve done some work to help improve the performance of Settings when switching between light and dark mode.
• We addressed an issue where some of the elements of the Themes page in Settings would end up crowded together when the window size was small.
• We resolved an issue where the Pen menu toggle under Taskbar Settings was not in sync with the actual state of the feature.
• Changes made to “Dismiss notification after this amount of time” in Accessibility Settings should now persist.
• Some of the icons you could enable in Taskbar Settings were erroneously labeled Windows Explorer even though that’s not what they were – this should now be fixed.
• The Connect text in Quick Settings has been updated to say Cast.

File Explorer:

• Clicking the command bar button twice should now close any dropdown that appeared.
• The new command bar should now appear when “Open folders in a separate process” is enabled under File Explorer Options > View.
• This build addresses an issue where right-clicking a file and selecting Open With > Choose another app might launch the file in the default app rather than opening the Open With dialog.
• Fixed an issue the desktop and File Explorer context menu would stop launching.

Search:

• We fixed an issue where the option to verify your account in Search wasn’t working.
• Hovering over the Search icon on a secondary monitor will now show the flyout on the correct monitor.
• Search should now work if you open Start and start typing after having gone to the apps list and back.

Widgets:

• When using the Outlook client with a Microsoft account, Calendar, and To-Do updates should sync faster down to the widgets.
• We addressed an issue where if you added multiple widgets quickly from the widget's settings, it could result in some of the widgets not being visible on the board.
• We fixed a bug where widgets could all become stuck in a loading state (blank squares in the window).
• The traffic widget should now follow the Windows mode (light or dark).
• The title of the sports widget should no longer mismatch with the content of the widget.

Other:

• This build addresses an issue where ALT + Tab was getting stuck open sometimes after you released the keys and had to be manually dismissed.
• We made a fix for an issue where Narrator's focus wasn’t ending up on the emoji panel after using the keyboard shortcut to open it.
• Magnifier’s lens view has been updated so the lens now has rounded corners.
• We found an issue that was noticeably impacting Start launch reliability for some Insiders, and have addressed it with this flight.
• We’ve updated the “Most Used” text in the Start menu’s app list so it should no longer be getting clipped.
• Using the semantic zoom in Start’s app list should no longer result in the list being pushed down and to the right off the edge of the window.
• We fixed an issue where if you pressed ⊞ WIN + Z you would need to press Tab before you could use the arrow key to navigate through the snap layouts.
• We addressed an issue where an acrylic area could get left on the screen after repeatedly snapping and unsnapping a window with touch.
• We’ve done some work to mitigate an unexpected flash when moving a snapped window with touch.
• We made a change to help window borders have a little more contrast when “Show accent color on title bars and windows borders” was turned off.

Known issues in Windows 11 repaired

Start:

• In some cases, you might be unable to enter text when using Search from Start or the Taskbar. If you experience the issue, press ⊞ WIN + R on the keyboard to launch the Run dialog box, then close it.
• Based on feedback, we are working on adding access keys to ⊞ WIN + X so that you can do things like “⊞ WIN + X M” to launch Device Manager. Insiders may see this functionality in this build, however, we are currently investigating an issue in which sometimes the option is unexpectedly unavailable.

Taskbar:

• There is an issue in this build where Explorer.exe will crash when the date and time button on the Taskbar is clicked to access new notifications with Focus Assist turned off. The workaround for this is to enable Focus assist to priority or alarms mode. Note that when focus assist is turned on, notification popups won’t appear, but they will be in the notification center when opened.
• The Taskbar will sometimes flicker when switching input methods.
• Taskbar previews may draw partially offscreen.

Settings:

• When launching the Settings app, a brief green flash may appear.
• When using Quick Settings to modify Accessibility settings, the settings UI may not save the selected state.
• The button to rename your PC doesn’t work in this build. If needed, this can be done using sysdm.cpl.
• Settings will crash when clicking “Facial recognition (Windows Hello)” under Sign-in Settings if Windows Hello is already set up.
• Reset this PC and Go back buttons in Settings > System > Recovery does not function. Reset and rollback can be accessed from the Windows Recovery Environment by selecting System > Recovery > Advanced startup, and pressing Restart now. Once in Windows Recovery, choose Troubleshoot.
• Choose Reset this PC to perform a reset.
• Choose Advanced options > Uninstall Updates > Uninstall latest feature update to perform a rollback.

File Explorer:

• exe crashes in a loop for Insiders using the Turkish display language when the battery charge is at 100%.
• When right-clicking the desktop or File Explorer, the resulting context menu and submenus may appear partially off-screen.
• Clicking a desktop icon or context menu entry may result in the wrong item being selected.

Search:

• After clicking the Search icon on the Taskbar, the Search panel may not open. If this occurs, restart the “Windows Explorer” process, and open the search panel again.
• When you hover your mouse over the Search icon on the Taskbar, recent searches may not be displayed. To work around the issue, restart your PC.
• The search panel might appear black and not display any content below the search box.

Widgets:

• Widgets board may appear empty. To work around the issue, you can sign out and then sign back in again.
• Launching links from the widgets board may not invoke apps to the foreground.
• Widgets may be displayed in the wrong size on external monitors. If you encounter this, you can launch the widgets via touch or WIN + W shortcut on your actual PC display first and then launch on your secondary monitors.

Store:

• The install button might not be functional yet in some limited scenarios.
• Rating and reviews are not available for some apps.

Windows Security:

• Device Security is unexpectedly saying “Standard hardware security not supported” for Insiders with supported hardware.
• “Automatic sample submission” is unexpectedly turned off when you restart your PC.

Localization:

• There is an issue where some Insiders may be missing some translations from their user experience for a small subset of languages running the latest Insider Preview builds. To confirm if you have been impacted, please visit this Answers forum post and follow the steps for remediation.

That's is so far, the latest update information on Windows 11 insider build. Stay tuned for more information when it comes as it comes.

Error Code 8024402C – What is it?

When upgrading to Microsoft Windows 10, some users may encounter Error Code 8024402C. This error, while attempting to update, is a result of five possible issues. The error code itself is not a critical concern, yet while the error is occurring, users will not be able to upgrade their Windows software. As with any Microsoft error code, even if it is not critical, it is recommended that the error be addressed sooner rather than later. An insignificant error now could lead to a larger, more catastrophic error later on. Common symptoms include:

• A dialog box appears with the Error Code 8024402C when attempting to upgrade to Microsoft Windows 10.
• Your current version of Windows is unable to recognize the need for an update to Microsoft Windows 10.

Solution

Error Causes

As previously stated, there are five major reasons why error code 8024402C occurs.

• An erroneous character in the proxy override settings
• A wrongly configured firewall is preventing the update from taking place.
• Attempting to access the Windows 10 update through a VPN (Virtual Private Network) connection.
• Workstations that operate behind a corporate ISA server.
• A corporate network system that does not have auto proxy enabled.

The sooner these known causes are addressed, the sooner you will be able to successfully upgrade to Microsoft Windows 10.

Further Information and Manual Repair

Microsoft Support posits four different resolutions to these known error code 8024402C issues. Some of these methods will be more comfortable for at-home users than others. If you are experiencing this issue in a corporate or business setting, it may be better to have your IT tech or department attempt the methods.

Method 1:  When your firewall is causing the issue.

1. Access your firewall software.
2. Specifically, look into the settings associated with your firewall.
3. Make sure that the following three websites are listed as exceptions to your firewall or proxy.

• https://*.windowsupdate.microsoft.com
• http://download.windowsupdate.com
• http://*.windowsupdate.microsoft.com

4. If any of these websites are missing from your firewall list, add them to the list.
5. Restart your Microsoft Windows 10 update.

Method 2: For an erroneous character in the proxy override settings.

1. Open internet explorer, if you use another program to access the internet, you will still need to use internet explorer for this solution.
2. Open your internet explorer tools window.
3. Click on internet options.
4. Choose the connections tab.
5. Select LAN settings.
6. Choose the Advanced option.
7. Delete anything that appears in the exceptions section.
8. Closeout of internet explorer.
9. Click on your start button.
10. Select RUN and type CMD into the field, press ENTER.
11. This will access the command prompt screen. Type “proxycfg -d” and press ENTER.
12. Type the command “net stop wuauserv” and press ENTER.
13. Finally, type “net start wuauserv” and press ENTER.
14. Now you have cleared your proxy cache. Access the Microsoft Windows 10 update again to download.

Method 3: If a VPN connection is causing error code 8024402C.

1. Disconnect from your VPN connection, thus connecting directly to the internet without a proxy or network.
2. Retry the Microsoft Windows 10 update.
3. After the update is successful, reconnect to the VPN network.

Method 4: Use this is an ISA server is in place at your networked business site.

1. Access the ISA firewall client option. From here your goal is to initiate the ISA server automatic detection feature.
2. From the control panel, select the firewall client option.
3. Choose the configure option.
4. Check the box next to “automatically detect firewall server”.
5. Select the “update now” button.
6. Click the OK button.
7. Restart your Microsoft Windows 10 update.

Again, not all of these methods are meant for computer users who do not usually explore and change software settings of this nature. If you do not feel comfortable with any of these methods, you can opt to download and install a powerful automated tool to repair Windows error code 8024402C.

Rundll Error - What is it?

Rundll Error, DLL is also known as Dynamic Link Library is a Window library that basically consists of instructions and codes used and shared by multiple programs installed on your system. It helps programs load and run smoothly. Rundll error is generated when the system fails to access DLL files thereby hampering your ability to successfully run your desired program.

Solution

Error Causes

The rundll error code is triggered due to multiple reasons such as:

• DLL file affected by virus and malware
• Poor program installation
• Invalid Windows registry entries

It is advisable to fix the run.dll error immediately without any delay because this error exposes your PC to serious threats such as system crash, freeze, failure, data loss, and even privacy threats like cybercrime, data breaches, and identity thefts.

Further Information and Manual Repair

To resolve the rundll error on your system, here are some solutions that you can try:

Solution 1: Reboot your System

Sometimes rebooting your system can also resolve the issue. However, if it doesn’t then you need to try some other solution to fix it.

Solution 2: Identify the Program Triggering the Error

To fix rundll error, the first thing that you need to do is to identify the program generating this error and check it for validity. For this, simply analyze the rundll error dialog box. Let’s say you get the following run.dll error on your system Error loading

C:\WINDOWS\system32\usvdgpo.dll.

This error message indicates that the program ‘usvdgpo’ is causing the run.dll error on the system. Once the program is identified, the next step is to stop it manually. For this, you go to the start menu and click run, now type ‘services.msc’ in the dialog box, and press ‘Enter’. After that right-click the related process to your rundll error and then click the ‘Stop’ button to stop the program. Now close the window. Though this action will stop the process it will not remove the reference to the bogus items. To remove that you will have to remove the program from the Windows Registry. This can be done by typing ‘Regedit’ in the Run dialog box. This will open the registry editor. From the keys listed in the left panel, navigate to the following key: HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/Run. Now right-click on this key and click delete and then simply close the windows registry and reboot your system. After this, you will then have to uninstall the program to completely eradicate the rundll error. To do this, go to the control panel, Add/remove programs, and right-click to uninstall the program causing the run.dll error on your system. Click yes to confirm your decision. Once the program is uninstalled, reinstall the program using the program CD to get yourself an error-free program. This procedure is tricky, time-consuming, and maybe slightly challenging for you especially if you are not a computer programmer.

Solution 3: Run an Antivirus

If the cause of the run.dll error is a malware attack then you need to download an antivirus and run it on your system. However, this may impact the speed of your PC. Antivirus is notorious for slowing down PC speed.

Solution 4: Download Restoro.

If you are not a computer programmer, then running Restoro is possibly the easiest way for you to resolve rundll errors on your system in seconds. Restoro is an innovative, cutting edge, and multi-functional feature-filled PC repair tool that can be used to repair all kinds of system-related errors including rundll errors. The registry cleaner utility cleans up the RAM by removing unnecessary and obsolete files like junk files, invalid registry entries, and files from the uninstalled programs. It resolves disk fragmentation issues, repairs dll files, and the registry. In just a few clicks you can easily repair the registry and remove malware thereby resolving rundll errors on your system. Operating Total System Care is quite simple. It has a user-friendly interface and easy navigation. It is safe, efficient, bug-free, and compatible with all Windows versions Click here to download Restoro and resolve ‘rundll errors’ and access/run programs on your system smoothly.

One of the most useful and efficient command-line disk management tools is the DISKPART utility. It can be used to manage, delete or create new hard drive partitions. However, despite its efficiency, there are still times it could face some errors like the “No usable free extent could be found”. You can encounter this error when you create a partition. This error could be due to insufficient disk space which is why it is not able to carry out the operation. It is also possible that the disk is not recognized by the system. And since there are only four recognized primary partitions, when you try creating a fifth one, you will get this error. In addition, this error could also occur if the disk has been partitioned using the MBR disk partitioning format. To fix the “No usable free extent could be found” error, here are some suggestions you can follow.

Option 1 – Free up disk space using Storage Sense

The error could be caused by insufficient disk space in your computer and so you need to free up disk space using Storage Sense to fix the problem.

• Open Setting > System > Storage from the WinX Menu.
• From there, you will see a list of all the local and connected storage devices along with the details on the free space. Make sure that Storage Sense is on.
• Next, find a link that says “Free Up Space” and click it to open.
• After that, a screen which is the built-in program in Windows 10 will appear and will scan your computer for the following junk files so you can free up disk space:
  • Windows Upgrade Log Files
  • The system created Windows Error Reporting Files
  • Thumbnails
  • Temporary Internet Files
  • Previous Windows Installation Files
  • Delivery Optimisation Files
  • DirectX Shader Cache
• Choose the files you want to get rid of and then click on the remove files option. Note that you’ll have an idea of the total size as you select any of the junk files listed above.
• Now go to the “Free Up Space Now” section and click the Clear Now button. This will get rid of all the temporary or junk files in your computer and should hopefully fix Error 1310.

Note: You can also run the Disk Cleanup tool to free up disk space.

Option 2 – Try to run DISKPART in Command Prompt with administrator permissions

The next thing you can do to resolve the error is to run the DISKPART utility with admin privileges.

• In the Start Search, type “command prompt” and from the search results that appear, look for Command Prompt.
• Once you found it, right-click on it and select the “Run as administrator” option.
• After that, try to execute the Diskpart operation once again. Note that you also have to specify different size & offset values for the partitioning and then see if you still encounter the same error.

Option 3 – Try to execute the DISKPART clean command

The next thing you can try is to execute the clean command in DISKPART to fix any issues in the disk.

• Open Command Prompt with admin privileges.
• Then execute this command: diskpart
• The command you entered will initiate the DISKPART utility. Now execute this second command to view all the disk connects or all the partitions on those disks formed: list disk
• After that, you need to select one command depending on the list command you executed and then execute this third command: select disk #
• The third command you just executed will select the disk or partition you want to select. Now execute this fourth command: clean
• The command you entered will remove all the volumes or partitions formatting the disk in focus.
• Once it’s done, try to carry out the DISKPART operation you were trying to execute.

Option 4 – Try to update the USB drivers

Outdated USB drivers can also be the reason why you’re getting the error. Thus, you must update them from time to time. You can install the latest version of the USB driver for your system. But you need to check the manufacturer’s website or guidelines to update the driver according to your system. If it happens that the drivers might not be compatible with the version of the system your laptop is using which is unlikely, you can run the driver software in Compatibility Mode in that kind of situation. To update your USB drivers, follow these steps:

• Tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, look for the USB Serial Bus controllers from the list of device drivers displayed. If you see a red or yellow sign that shows up against the driver, right-click on the driver’s name and select “Update Driver Software”. And if you find any “Unknown device”, you need to update it as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.

Option 5 – Run the Hardware and Devices troubleshooter or the USB troubleshooter

You can find the Hardware and Devices troubleshooter under the Troubleshooters section of the Windows Settings panel on your Windows 10 PC. You can use this troubleshooter to fix common hardware and external device-related issues without exerting too much effort. If you don’t know where to find it, follow these steps:

• Tap the Win + I keys to open the Windows Settings.
• Next, navigate to Update & Security > Troubleshoot.
• You should see the option for Hardware and Devices on your right-hand side where you can also find the “Rub the troubleshooter” button – click on it to get started.
• Follow the next on-screen instructions to fix the basic issues of common hardware and external device.

Note: If you want to, you can also use the USB Troubleshooter to fix the problem just go back to the Troubleshoot page where you can find it.

As you know, every Windows Update is essential for every Windows operating system. They have to be regularly installed, especially since they include various security updates that are important to the system. However, there are times when Windows Update fails to execute properly and you get errors like the error code 0x80070BC9. When you encounter this particular Windows Update error, you will get the following error message on your screen:

“0x80070BC9 – ERROR_FAIL_REBOOT_REQUIRED. The requested operation failed. A system reboot is required to roll back changes made.”

This kind of Windows Update error is most likely caused by a newly installed problematic software, corrupted Windows Update files, or policies that restrict the behavior of the Windows Module Installer. The Windows Module Installer, also known as “WMIW” or “TiWorker.exe”, is the one that checks for new updates from the Windows server and installs them on your computer. This is why you need to make sure that you do not have any policies that control the start behavior of the Windows Module Installer since this service must not be hardened to any start value and should be managed by the operating system. To resolve the Windows Update error code 0x80070BC9, you can check out the options provided below.

Option 1 – Try checking the status of the Windows Modules Installer Worker Service

Since the Windows Update error code 0x80070BC9 has something to do with the Windows Module Installer Worker service, you need to check its status in the Service Manager. Refer to the following steps to do so.

• In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “MSC” in the field and hit Enter to open the Services Manager.
• After opening the Services Manager, look for the Windows Modules Installer Worker Service.
• Once you found it, check its status and make sure that its Startup type is set to Manual.
• Now click on the Start button and see if it fixes the Windows Update error.

Option 2 – Run the Windows Update Troubleshooter

You might want to run a built-in Windows Update troubleshooter to resolve the Windows Update error. It is one of the things you can check out as it is known to automatically resolve any Windows Update errors like error code 0x80072EE2. To run this troubleshooter, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 3 – Try contacting the IT administrator to modify the group policies

You could also try to contact the IT administrator to have the group policies modified. This option is applicable for company-managed systems. As mentioned, one of the possible causes of the Windows Update error 0x80072EE2 is the policies that control the start behavior of the Windows Module Installer. Thus, you need to have them removed so that the Windows Module Installer Worker service is managed by the operating system itself. And since there could be many policies, it is highly advised that you contact your company’s IT administrator to get the job done for you.

Option 4 – Try to install the Windows Updates in a Clean Boot State

There are some instances that some conflicting programs installed in your computer might be the one that’s causing Windows Update error code 0x80070BC9. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

When you upgrade or update your Windows 10 computer but you suddenly got Error 0x8024a206 while trying to install the updates, it is due to a rouge update that was downloaded or because of some corrupted component in Windows. In case you don’t know, any file downloaded by Windows is verified for its integrity and if the files don’t pass the integrity test, then Error 0x8024a206 will most likely pop up during the Windows update or upgrade.

Option 1 – Reset the Windows Update components to the default

You have to stop a couple of services such as BITS, Cryptographic, MSI Installer, and Windows Update Services. And to do that, you need to flush the contents in the SoftwareDistribution folder. The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. Aside from that, it also contains all the Windows Update History files and once you delete them, you will most likely lose the Update history. As a result, the next time you run the Windows Update, it may result in a longer detection time.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net start cryptSvc net start bits net start msiserver

• After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.

After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:

• Type each one of the following commands.

net start wuauserv net start cryptSvc net start bits net start msiserver

• After that, exit Command Prompt and restart your computer, and then try to run Windows Update once more.

Option 2 – Re-register DLLs related to Windows Update

DLL files, also known as Dynamic Link Library, are parts of applications that are separated from the core program so that they can be used again as well as independently be updated. The DLL files are loaded into memory and then used. Note that they have to be registered with Windows so they can be loaded. So if they’re not, the main program will fail. And this is the same with the DLL files related to the Windows Update. Thus, you need to register them in order to resolve Error 0x8024a206.

• In the Cortana search box, type “command prompt”.
• From the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
• After that execute the commands listed below one after the other and don’t forget to hit Enter right after you key in each one of them.
  • regsvr32 JSCRIPT.DLL
  • regsvr32 MSXML3.DLL
  • regsvr32 WUPS2.DLL
  • regsvr32 WUPS.DLL
  • regsvr32 WUAUENG.DLL
  • regsvr32 WUAPI.DLL
  • regsvr32 WUCLTUX.DLL
  • regsvr32 WUWEBV.DLL

Note: You also have the option to run the commands together via a batch file. Simply create a batch file by copying all the commands in a notepad and then save it as “WURegisterDLL.bat”. After that, run the batch file and it will execute the commands all at the same time. Then you have to restart your computer and see if it has fixed the Error 0x8024a206.

Option 3 – Run the System File Checker

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the Error 0x8024a206. SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow and hit Enter.

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

Option 4 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update Error 0x8024a206. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

There has been recently discovered in the field of malware targeting Android devices. Affecting more than 10 million users of Android phones, the malware GriftHorse is doing its attacks via phishing and premium services scams. A lot of applications have been discovered that are hosts for this malware and many of them are inside the Google store and available for download. According to Zimperium zLabs, this malware that was recently detected has been doing its scams and attacks even in November of 2020 and has thus far accumulated hundreds of thousands of dollars in its scam. On the surface it looks very harmless, asking for typical permissions like internet access, calls, and other related needed functions, and then it waits. After few months the real attack happens when users get charged with premium service they never subscribed to in the first place.

List of Infected Applications that Carry GriftHorse Trojan

Zimperium zLabs listed out some of the apps with this malware. Users are advised to avoid installing them.

•     Amazing Video Editor
•     Bag X-Ray 100% Scanner
•     Bus – Metrolis 2021
•     Call Recoder Pro
•     Call Blocker-Spam Call Blocker
•     Cinema Hall: Free HD Movies
•     Coupons & Gifts: InstaShop
•     GPS Phone Tracker – Family Locator
•     Fingerprint Changer
•     Fitness Point
•     Free Calls WorldWide
•     Geospot: GPS Location Tracker
•     GPS Phone Tracker – Family Locator
•     Handy Translator Pro
•     Horoscope : Fortune
•     iCare – Find Location
•     iConnected Tracker
•     Instant Speech Translation
•     Lifeel – scan and test
•     My Chat Translator
•     My Locator Plus
•     Plant Camera Identifier
•     Racers Car Driver
•     Safe Lock
•     Screen Mirroring TV Cast
•     Slime Simulator
•     Smart Spot Locator

These are only some of the many infected apps available on the internet. Zimperium zLabs also warned that GriftHorse Trojan exists in over 70 countries worldwide. The infected app quickly changes the language and displays content depending on the user’s IP address.

Qualcomm Atheros Qca61x4a Driver is a software driver used in WI FI communication between OS and device itself. When this driver stops working usually it means loss of connection and no internet available. This error knows to comes frequently and repeat itself over long periods of time which makes it quite annoying. If you are one of the unlucky users of Windows who get this error please keep reading in order to eliminate it and continue working on your computer normally.

1. Disable & Enable the Qualcomm Adapter Driver

   Press ⊞ WINDOWS + X to open the secret menu, click on the device manager. In device manager expand network adapters. Right-click on Qualcomm Atheros Qca61x4a wireless network adapter and click on disable Right-click on Qualcomm Atheros Qca61x4a wireless network adapter and click on enable

2. Rollback the Qualcomm Adapter driver

   Press ⊞ WINDOWS + X to open the secret menu, click on the device manager. In device manager expand network adapters. Right-click on Qualcomm Atheros Qca61x4a wireless network adapter and click on properties Under properties, window click on Driver tab and left-click on Roll Back driver (if the option is greyed there is no previous driver, follow next step) Choose your reason and click on OK

3. Update Qualcomm Atheros driver to the latest version

   Press ⊞ WINDOWS + X to open the secret menu, click on the device manager. In device manager expand network adapters. Right-click on Qualcomm Atheros Qca61x4a wireless network adapter and click on Update Driver

4. Install the new driver in compatibility mode

   Right-click on the installer package and choose properties Go to the compatibility tab Choose compatibility settings and install.

Creating a System Restore point is definitely a must especially when you are about to make some changes to your computer. This will help make sure that the system settings and files can go back to an earlier point, should something go wrong, without affecting any personal files. However, there are cases when creating a System Restore Point does not go smoothly and you encounter an error that says, “The shadow copy provider had an unexpected error while trying to process the specified operation ( ox8004230F )”. Aside from creating System Restore Point, you can also encounter this error when you create a system image or backup. According to reports, this error pops up when the required services are not running or not properly responding. And to fix it, there are several recommendations that will be provided in this post to fix the Error 0x8004230F when creating System Restore point in Windows 10. You can try to check the Volume Shadow Copy Services status or run the VSSADMIN tool. You could also check the status of the Microsoft Software Shadow Copy Provider Service or create System Restore Point in a Clean Boot State. For more details, refer to the provided options below.

Option 1 – Try checking the status of the Volume Shadow Copy Service

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• From the list of services, look for the Volume Shadow Copy service and double-click on it.
• After that, this will open the Properties where you have to make sure that the Startup type is set to Automatic (Delayed Start) and then click on the Start button underneath it.
• Once done, click on Apply and then OK to save the changes made.
• Now try creating a System Restore Point again and see if the error is already fixed or not.

Option 2 – Try to run the VSSADMIN tool

In case you don’t know, the shadow copy provider is sensitive and some other backup, disk cloning, etc. can make it malfunction. To fix this, you can run the VSSADMIN tool by following these steps:

• Tap the Win + R keys to open the Run dialog box and type “cmd” and hit Enter to open Command Prompt.
• Next, execute this command to check if you have other third party VSS admin providers: vssadmin list providers
• After that, if it finds any, you need to disable them but if it does not find anything, then proceed.

Option 3 – Try to check the Microsoft Software Shadow Copy Provider Service status

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• From the list of services, look for the Microsoft Software Shadow Copy Provider Service and double click on it.
• After that, this will open the Properties where you have to make sure that the Startup type is set to Automatic (Delayed Start).
• Once done, click Apply and OK to save the changes and then try creating System Restore Point again.

Option 4 – Troubleshot the problem in a Clean Boot State

It is possible that some third-party program installed in your computer might be the one that’s causing the ox8004230F when you try to create a System Restore point. Thus, you can try to boot your computer in a Clean Boot State and then try to perform the task again.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And to configure Windows to use the usual startup, just simply undo the changes.)
• Once your computer has restarted try to create a System Restore Point again and if it now works, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.