Logo

Chrome Roblox malware

Roblox is a very popular online game with millions of gamers playing it each day and as such it will naturally bring a lot of malware and attack on players trying to steal and exploit them for monetary gains. The latest attack and high-profile stealing of currency and assets happened exactly in Roblox.

roblox

Malicious activities have been reported to come from chrome extensions. So far 2 extensions have been identified that have hidden malware inside them but there could be more of them currently undetected. Extensions work as a front while in the back they mine user logins and other data in order to steal stuff from the Roblox platform.

To make things worse some of the malware is within long extensions like SearchBlox. The SearchBlox extension allows you to search quickly for other users if it was legitimate but has been compromised within the last month. There is evidence that people are stealing Roblox currency with the data gathered by the hidden backdoor in it.

SearchBlox extension is still Active in Chrome Web Store, with the primary listing still with the "Featured " badge. Google is actively removing malicious software from its storefront on a regular basis but this one still lingers in it.

If you or your kid have this Chrome extension installed, uninstall it right away and always be careful about which extension you install and give access to your system, keep them updated and check various blogs and article sites to inform yourself when a bad one is found.

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

There is a system repair pending
If you are running a System File Checker scan but got an error message instead that says, “There is a system repair pending which requires reboot to complete, Restart Windows and run SFC again”, worry not for this post will walk you through how you can fix the problem. This kind of error can be addressed and fixed with several potential fixes which will be provided in this post. You can try to restart your computer and run a System File Checker scan again or delete the pending .xml file or use the “revertpendingactions” parameter for the DISM tool. For more information, refer to each one of the options given below.

Option 1 – Try restarting your computer and run the SFC again

The first thing you can do to fix the problem is to restart your computer and let the pending process be completed. After your computer restarted, try to run System File Checker again and see if the error is now fixed or not. If not, refer to the other options below.

Option 2 – Try deleting the pending .xml file

The next thing you can do to fix the problem is to delete the pending .xml file. How? All you have to do is navigate to this location at CWindowsWinSxS and from there, look for a pending .xml file and rename it or delete it. This will get rid of any pending tasks and will build a fresh new check.

Option 3 – Try to use the “revertpendingactions” parameter for the DISM tool

If the two options given above didn’t work, you can try using the revertpendingactions parameter for the DISM tool. If you’re not able to boot into Windows, then run Command Prompt from the Recovery Console and execute the given command below.
dism.exe /image:C: /cleanup-image /revertpendingactions
After you execute the command, restart your computer and try to run System File Checker again and see if it has fixed the problem or not.
Read More
Windows Search not searching the entire PC
There are times when the Windows Search results do not include what you want to search. However, if you are trying to search for something that’s located on your desktop and Libraries, they would appear right away on the search results. Actually, the issue is not with the search but with the list of files and folders that Windows can index. If you encounter this issue, read on as this post will guide you on how to fix it. The Windows 10 operating system, ever since Windows v1903 was released, offers two kinds of searches – the classic and the enhanced search. You may have to add more folders to the classic search or use the enhanced mode to resolve the issue. In other words, to fix the problem with the Start Menu Search, you can try to enable the Enhanced Mode or add folders to the Class Search or remove the excluded folders, as well as run the Search and Indexing troubleshooter. For more information, refer to each one of the options provided below.

Option 1 – Try to enable the Enhanced Mode

To fix the problem, you have to enable the Enhanced Mode search and configure the folders you want to be indexed. How? Follow these steps:
  • First, you have to go to Settings > Search > Searching Windows.
  • Next, select the radio button for the Enhanced option.
  • After that, select the folders you want the Windows Indexer to exclude from the Enhanced Search mode.

Option 2 – Try to add folders to the Class Search

If you don’t want to enable the Enhanced search mode, then you might want to add folders that are important to you. All you have to do is configure the Search Indexing Options by following these steps:
  • Go to Settings > Search > Classic and from there, click on the “Customize search locations” option.
  • Next, click on Modify in the pop-up window that appears.
  • Then add drives and folders that are important to you. Once the indexing is completed, Windows will be able to find the file and display it in the search results.

Option 3 – Try removing the excluded folders

If you have already enabled the Enhanced mode but your files still don’t appear, then you might want to check out the excluded folder list.
  • The first thing you have to do is go to Search and from there, you will find a list of folders under the Excluded folder list.
  • Next, click on the excluded folder that you want to remove by clicking on the “Remove Excluded folders” button.
  • If you are using the Classic search, you have to check if the index has restrictions on the file type. You can find it in Advanced options > File Types.
Note: If you want to search in Documents, you could also enable the Index Properties and File Contents. This should resolve the problem.

Option 4 – Try to run the Search and Indexing troubleshooter

You might also want to run the Search and Indexing troubleshooter in Windows 10 as it checks whether the settings for the Windows Start Search are in place and automatically corrects any issues if the update or software installation has changed the settings. To run it just click on the Start button and select Settings > Updates and Security > Troubleshoot. From there, select the Search and Indexing Troubleshooter.
Read More
Disable Touchscreen in Windows 11
The touchscreen feature inside Windows 11 is a pretty good thing but sometimes can be very impractical. The screen can easily and constantly get dirty due to fingers touching it all the time and there are users that do not wish or want to have this feature at all. touchscreen windows 11If you are one of the mentioned users and for any reason, you do not wish to have a touchscreen-enabled then sit back and relax, we have you covered in this tutorial on how to fully disable touchscreen inside Windows 11.

Turn off touchscreen via device manager

  1. Click on the Windows Search icon in the taskbar
  2. Type Device Manager
  3. Click on Device Manager from the list of results
  4. Inside locate Human Interface Devices and click on the right arrow
  5. In the list, find HID-Compliant Touch Screen and select Disable Device
  6. Click on Yes to confirm

Disable it via Windows Terminal

  1. Right-click on the Windows icon in the taskbar
  2. Click on Windows Terminal (admin)
  3. Inside run this command: Get-PnpDevice | Where-Object {$_.FriendlyName -like '*touch screen*'} | Disable-PnpDevice -Confirm:$false

Conclusion

No matter which method you prefer, both of them will disable the touch screen inside Windows 11. Thank you for reading trough article and I hope to see you again. Take care.
Read More
How to Fix PFN_LIST_CORRUPT Error on Windows
If you suddenly encounter PFN_LIST_CORRUPT Blue Screen of Death error while using your computer then it means that the Page Frame Number or PFN list is corrupted. Page Frame Number is an indexing number used by the hard drive to find out the location of every single file on the physical disk. This kind of Blue Screen error is usually caused by a driver that’s passing a bad memory descriptor list and it can either be temporary or permanent. And so to fix this particular BSOD error, read on as this post contains a couple of suggestions that could help. Keep in mind that when you get a Blue Screen error like PFN_LIST_CORRUPT, the power connection to your PC must not be interrupted and so if you are using a laptop, it’s best if you connect it to a power source. On the other hand, if creating a dump from 0% to 100% takes up more than 5-10 minutes, then you have to force shut down your computer by pressing and holding the Power Key for 10 seconds or at least until the CPU lights turn off. After you do that, proceed to the troubleshooting tips prepared below.

Option 1 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like PFN_LIST_CORRUPT. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:
  • Tap the Win + I keys to open the Settings panel.
  • Then go to Update & Security > Troubleshoot.
  • From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 2 – Run a System File Checker scan

You can also try to run a System File Checker or SFC scan in order to scan your computer for corrupted files that might be the cause behind the PFN_LIST_CORRUPT error. Once it finds any corrupted system files, it will automatically fix them. To run System File Checker, here’s what you have to do:
  • Tap Win + R to launch Run.
  • Type in cmd in the field and tap Enter.
  • After opening Command Prompt, type in sfc /scannow
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.
  • Restart your computer after the scan is completed.

Option 3 – Check for any hard disk errors

  • On your desktop, right-click on the “This PC” or computer icon and then select Manage to open the Disk Management. Here you get to check your drive’s health.
  • Next, click on Disk Management on the left side panel.
  • From there, check the state of your drives. If it shows that all your partitions are healthy then it means all is good and that the problem may have something to do with some physical issues with your hard drive.
You might also want to run the CHKDSK utility to help you fix any issues with your hard disk. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.
  • Open Command Prompt with admin privileges.
  • After opening Command Prompt, execute the following command and hit Enter:
chkdsk /f /r
  • Wait for the process to be completed and then restart your computer.

Option 4 – Update the Device drivers

Updating the Device drivers can also help you fix the PFN_LIST_CORRUPT Blue Screen error. To do so, follow the steps below.
  • 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, a list of device drivers will be displayed. If you see a red or yellow sign that shows up against the driver, right-click on the driver and select “Update Driver Software”.
  • Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
  • Restart your PC and then check if the Blue Screen error is now fixed or not.

Option 5 – Disable OneDrive

The PFN_LIST_CORRUPT error might also be caused by OneDrive. Thus, you have to try disabling this program to resolve the problem.
  • Tap the Ctrl + Shift + Esc keys to open the Task Manager.
  • Once the Task Manager is open, click on More Details located at the bottom left portion of the window.
  • Then go to the Startup tab and select Microsoft OneDrive and then click Disable.
Read More
How to Resolve Internal Error 2753

Internal Error 2753 - What is it?

Internal error 2753 is associated with Windows Installer failure. The Windows Installer is basically an in-built software program in Windows 7 and 8. It installs all programs on the system smoothly, saves the program in the computer program files and in the Windows Registry. Though this can be carried manually Windows Installer makes the installation process much easier. However, internal error 2753 can cause a great deal of distress and frustration during program installation. This error prevents you from installing your desired program successfully.

Solution

Restoro box imageError Causes

The 2 known causes for Internal Error 2753 are:
  • Viral infection
  • Windows Installer not properly registered

Further Information and Manual Repair

To resolve internal error 2753 on your system, try the methods discussed below. These methods are easy and require no technical expertise. Let’s get started:

Method 1 - Remove All Malicious Programs

Malicious programs like viruses, malware, adware, Trojan and spyware can corrupt programs on your PC like Windows Installer. If this is the underlying cause of error code 2753, then simply download a powerful antivirus on your system. Run it to scan for all such malicious programs and remove them. Once your PC is clean, try installing your desired program. This will hopefully resolve the issue. If the error still pops up then try method 2.

Method 2 - Register Windows Installer Properly

To do this, go to the start menu and then open Run and type ‘cmd’ in the box, and press OK. This will open the DOS command window. In the command prompt type "regsvr32 vbscript.dll" and then press Enter to proceed. After that, you will see a message that will read as "DllRegisterServer in vbscript.dll succeeded." This means Window Installer files have been successfully registered on your PC.  Now you can try installing your desired program again. If the installation begins and completes successfully, then the error is resolved.

Method 3 - Undo Recent Changes

If nothing works, then use the Windows System Restore Utility tool to undo recent changes. This will bring back your PC in the former state before you experienced the error 2753 on your PC. To access System Restore Utility, press Start and type System Restore in the search box. Now follow the steps in the Wizard to choose a restore point. Once you select the point, reboot your system to activate changes.
Read More
Install Windows 11 on any computer officially
Windows 11 system requirementsMicrosoft’s initial Windows 11 hardware requirements were not really well received by users and they were not really clearly represented from the start making a lot of potential customers slowly drift away from the hype. It seems that Microsoft has acknowledged this since they have changed their tune about system hardware requirements for the upcoming Windows 11. It seems that Windows 11 will be able to be officially installed on unsupported computers but with a little inconvenience.

What is a catch?

Windows 11 will still have the same hardware requirements and if the PC meets them, that computer will be officially supported, other ones (any that can run Windows 10) that do not meet system requirements can still run Windows 11 but the system will have to be clean installed. So no upgrade option for old computer users, just a clean install. This means of course that you will need to download the ISO image and make a bootable USB in order to install it. Also since you will be doing a clean install do a backup of the hard drive since it will need to be formatted. Also, Microsoft has stated that with unofficially supported PC some driver updates might not be delivered leaving you with either older driver versions or relying on your hardware manufacturer on them. This is still not confirmed by Microsoft, just stated as an option. We will see how it goes.

Conclusion

It is very good that Microsoft has reconsidered its system requirements and will not stubbornly push its initiatives over the top requirements allowing even older computers to install new OS. I am sure over time lot of users will upgrade their hardware and drive into officially supported waters, but it is good that they will be able to use new OS on their current hardware.
Read More
Repairing or rebuilding the WMI Repository
There are times when the WMI Repository gets corrupted which results in the Provider Load Failure. To resolve this issue, you need to repair or rebuild the WMI Repository in your Windows 10 computer. In this post, you will be guided on how exactly you can do that. In case you don’t know, the WMI which stands for Windows Management Instrumentation is a set of specifications from Microsoft to consolidate the management of devices and applications in a network. The WMI is a database that stores meta-information and definitions for WMI classes. Using only these, the conditions of the systems can be known. You can find the WMI Repository in %windir%System32WbemRepository. It provides end-users with the status of the local or remote computer system. Keep in mind that you must not use this on the Server 2012 Cluster machine. Although there are command-line tools that can fix or restore the Windows Management Instrumentation repository. However, Microsoft suggests that it’s better if you verify if there is corruption. Here are a list of errors as well as permission issues you might encounter:
  • Unable to connect to root default or rootcimv2 namespaces. It fails with the error code “0x80041002” pointing to “WBEM_E_NOT_FOUND.”
  • 0x80041010 WBEM_E_INVALID_CLASS
  • When you open Computer Management and Right Click on Computer Management (Local) and select Properties, you get the following error: “ WMI: Not Found” or it hangs trying to connect
  • Trying to use wbemtest , and it hangs
  • Schemas/Objects missing
  • Strange connection/operation errors (0x8007054e)
To verify if there is corruption, you can try running the following command in an elevated Command Prompt:
winmgmt /verifyrepository
 After you enter the command, if there is a response saying, “repository is not consistent”, then the repository has an issue. If not, then something else is causing the problem. Since you are certain that corruption exists in the WMI repository, then here are some suggestions you need to check out to repair or rebuild the WMI repository.

Option 1 – Try to reset WMI Repository

  • Type “command prompt” in the Start Search and right-click on Command Prompt from the search results and then select “Run as administrator”.
  • After opening Command Prompt with admin privileges, type and enter this command: winmmgmt /salvagerepository
The command you entered is used when the winmmgmt command performs a consistency check. So if an inconsistency is detected, it will rebuild the repository.
  • Next, execute this command to see if the WMI repository now comes back as consistent: winmgmt /verifyrepository
This command will perform a consistency check on the WMI repository.
  • If it states that the WMI repository is not consistent, then you need to type and enter this command: winmgmt /resetrepository
This command is used to reset the repository to its initial state when the operating system was first installed.

Option 2 – Try to force recover the WMI Repository

The WMI Repository comes with a built-in self-recovery process so when the WMI service restarts or detects any corruption, it will automatically trigger the self-recovery procedure. This can happen in two ways:
  • AutoRestore: This will use the backup images if the Volume Shadow copy or VSS backup is turned on.
  • AutoRecovery: The rebuilding process will generate fresh images of the WMI repository based on the registered MOFs. The MOFs are available in the registry located at HKLMSoftwareMicrosoftWBEMCIMOM: Autorecover MOFs
Note: Autorecover MOFs is a key so double click on it to check its value. On the other hand, if the self-recovery procedure does not work, you can try to use the force-recovery process instead. How? Refer to these steps:
  • First, you need to check the reg key value is empty or not under this registry path: HKLMSoftwareMicrosoftWBEMCIMOMAutorecover MOFs
  • If the reg key value is empty, you have to copy-paste the reg key value from another computer. Just make sure that it’s from the System which is equivalent to the computer in question.
  • Next, type and enter this command: Winmgmt /resetrepository
  • After you enter the command, if you get an error that says, “WMI repository reset failed. Error code:0x8007041B. Facility: Win32”, then you have to stop all the Dependency Services on the WMI service by running the following commands:
    • net stop winmgmt /y
    • Winmgmt /resetrepository
This should fix the problem.
Read More
0x800ccc79 Error Code - A Quick Fix

0x800ccc79 Error - What is it?

0x800ccc79 error is an error message that you may come across when sending emails through Outlook Express from Microsoft. This error message is accompanied by a notification that is displayed as ‘email was not delivered’ or ‘the server doesn’t support SSL connection’.

Solution

Download Available to Recover all Lost Outlook data

Restoro box imageError Causes

This error code 0x900ccc79 is triggered due to the following causes:
  • Problems related to email servers
  • Changes in the configuration settings
  • Corrupted Windows Registry

Further Information and Manual Repair

When you receive the error 0x800ccc79 it may hamper your ability to send emails. Therefore it is advisable to fix it to ensure your emails are sent and received without any difficulty.

This Outlook error 0x800ccc79 is quite easy to repair. By following the quick fix 0x800ccc79 error code solutions given below you can resolve this error in just a couple of minutes.

Here’s what you need to do to fix this error right away:

Cause: Configuration issues

Solution: If the error occurs due to Outlook Express being configured to use the SSL protocol while sending and receiving emails via the web, then to resolve it, you need to allow Outlook Express to bypass the Secure Socket Layer settings.

To do so, click on ‘tools’ and then on ‘Accounts’. Now select the email account that you want to modify.

Now select the ‘Properties’ tab and then click on ‘Advanced Settings’.

Here search for the following text message ‘This server requires a secure connection’. Once you locate it, uncheck all the checkboxes given next to this option. After that save the changes and restart Outlook Express to see bring the changes into effect.

Cause: Missing or Corrupt Registry Entries

Solution: If the error 0x800ccc79 occurs due to missing or corrupt registry entries, then the best way to fix this error is to download and install a good registry cleaner on your PC.

The registry cleaner will help you clean your corrupt and damaged Windows registry entries and get rid of this error right away. It is suggested you download the registry cleaner tool from a reliable website to avoid any malware or virus downloads simultaneously.

Once you download the registry cleaner on your system, click on scan. The cleaner will scan your computer completely for registry errors and show you the results in a list form.

After the scanning is complete, click on repair to fix the errors.

So, next time, if you or anyone at your office comes across the Outlook Express error 0x800ccc79, you can try these solutions and fix the error immediately without waiting for the network personnel to come and resolve it.

Read More
RAC Manager not working, Error 0xc0000005
If the Diagnostic Data level in your Windows 10 computer is configured manually to the non-default security setting of zero and you’ve encountered an error code of 0xc0000005, read on as this post will guide you in fixing the problem with the Remote Access Connection Manager Service. In relation to error 0xc0000005, you might also encounter an error in the Application section of Windows Logs in the Event Viewer, along with the Event ID 1000 which would most likely have a reference of “svchost.exe_RasMan” and “rasman.dll”. Before you troubleshoot the problem, keep in mind that the Remote Access Connection Manager or RasMan service is the one that manages dial-up and VPN connections from the computer to the internet as well as other remote networks. Each time you connect, the Services dials the connection or sends out a request for a VPN connection. However, the error 0xc0000005, only occurs when a VPN profile is configured as “Always On VPN or “AOVPN” connection with or without a device tunnel. There are several options you can check out to resolve this error, you can try to install the KB Update 4505903 or fix it via Group Policy. You could also try to enable Telemetry from the Settings app or enable it via Registry Editor. For more information, make sure to check out the provided options below.

Option 1 – Try installing the KB Update 4505903

The first thing you can do to fix the problem is to make sure that you’ve already installed the KB Update 4505903 in your computer. If not, then you have to go to Settings > Update & Security > Windows Update and from there select the Check for updates link. You need to get the standalone package if you are using the Microsoft Update Catalog to update your computer and for that, you have to the website of the Microsoft Update Catalog. On the other hand, if you are using the Windows Server Update Services or WSUS, then you can just manually import the KB Update 4505903 into WSUS.

Option 2 – Try to enable Telemetry in the Group Policy and run the RASMAN service

The next thing you can do to fix the problem is to enable Telemetry via Group Policy and then run the RASMAN service. To do that, follow these steps:
  • Tap the Win + R keys to open the Run dialog box and type “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
  • Next, navigate to Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds > Allow Telemetry.
  • After that, open the policy and select one of the security levels like Basic, Enhanced, and Full.
  • Then click on the Apply and OK buttons to save the changes made and close the Group Policy Editor.
  • Once one, open the Run dialog box again and type “services.msc” in the field, and hit Enter to open the Windows Services Manager.
  • From there, look for the Remote Access Connection Manager Service and restart it. And then check if it resolved the problem or not...

Option 3 – Try enabling Telemetry via Settings

  • Tap the Win + I keys to open the Settings app.
  • Next, go to Privacy > Diagnostics and Feedback and select Basic or Enhanced under the Diagnostic data.
  • After that, tap the Win + R keys to launch Run and type “services.msc” in the field, and hit Enter to open the Services Manager.
  • From there, look for the Remote Access Connection Manager Service and restart it.

Option 4 – Try to enable Telemetry via Registry Editor

  • Launch the Run utility and type “regedit” in the field and tap Enter to open the Registry Editor.
  • Then navigate to this path: HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsDataCollection
  • From this path, look for “AllowTelemetry” and double click on it.
  • Now enter the values, 1, 2, 3 for Basic, Enhanced, Full, respectively.
  • If you can’t find AllowTelemetry, then just create a DWORD (32-bit) and name it “AllowTelemetry” and edit its value.
  • Once done, exit the Registry Editor and restart the Remote Access Connection Manager Service from the Services Manager.
Read More
PowerShell script Error 0xFFFD0000 in Windows
If you like to schedule different tasks on your Windows 10 computer and automate them, then you would find the Windows Task Scheduler very useful. It is commonly used by a lot of users to schedule various tasks like scheduling periodic execution of scripts and some programs to make sure that the intended tasks are automatically carried out. Apart from being a preinstalled application, the Task Scheduler is already available on your computer. However, there are times when you might encounter some errors while using it. One of these errors is error 0xFFFD0000. You can encounter this error while executing some PowerShell scripts. It can occur to any tasks as well especially to the ones that have a file executed using a particular program. And just like the PowerShell script, files also use PowerShell to be executed. To fix Error 0xFFFD0000, you need to follow the instructions provided below carefully. Step 1: In the Start Search, type “task scheduler” and click on Task Scheduler from the results to open it. Step 2: After opening Task Scheduler, right-click on the task that’s giving you the error and then click on Properties. Step 3: After that, navigate to the Actions tab in the new mini window that appears. Step 4: From there, select the action for the task and click on the Edit button which will open another mini window. Step 5: Next, make sure that the path to the executing program is properly typed inside the field of Program/script. Note that it should be set to the executable file for that particular program. For instance, you have to set it to “C:WindowsSystem32WindowsPowerShellv1.0powershell.exe” for the Windows PowerShell program. Step 6: You can also utilize the Browse button and navigate through Windows Explorer to locate that particular executable file for the program. Step 7: Now make sure to use the file argument in the Add arguments field followed by the path of the file to be executed. It should look like this:
-file "C:/Users/Ayush/Desktop/Powershell Script Sample.ps1"
Step 8: Once done, click on OK to save the changes made and see if the task is still giving you an error or not. On the other hand, if you are still getting the same error, you can try to repair the Task Scheduler by deleting corrupted tasks. Note that a single corrupted file can cause big problems so this option is quite important. And for you to delete a corrupted task or any task from the Task Scheduler, you have to use the Registry Editor if you are not able to use the Task Scheduler interface. To do so, follow these steps:
  • Tap the Win + R keys to open the dialog box for Run.
  • Next, type in regedit and click on OK or tap Enter to open the Registry Editor.
  • Then navigate to this path: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTree
Note: In this path, you can see all the tasks that are currently set in the Task Scheduler. And since it would be hard to tell which one of them is corrupted, you have to delete the latest one in Task Scheduler last. But before you do so, make sure that you take a note of the ID of the tasks. And for you to get the ID, you have to select the task you wish to delete and double click on the ID string located on your right-hand side, and then copy it in the Notepad.
  • Right-click on the task name and then delete it.
  • After that, delete the very same GUID which you have copied earlier from these folders:
  • ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheBoot
  • ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheLogon
  • ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheMaintenance
  • ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCachePlain
  • ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTasks
Note: You might not see the same GUID from these folders but if you see it, delete it right away.
  • Next, navigate to this location: C:WindowsSystem32Tasks
  • Delete the very same tasks you just deleted from the Registry Editor.
  • Restart your PC and check if the Task Scheduler is back to its normal state or not.
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status