Fix oobesettings error inside Windows 11

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.

If you are trying to install or reinstall a program on your Windows 10 computer but encountered an error instead that says, “Fatal error, Installation fails, Installation ended prematurely because of an error”, then you’ve come to the right place as this post will guide you how you can fix it. This kind of error is most likely caused by some files that may have been left behind by the previous installation of the program. Each time a program is uninstalled, it leaves behind its files and if the uninstallation process wasn’t completed properly, then it would result in errors like the

“Fatal error, Installation fails, Installation ended prematurely because of an error”.

Moreover, this kind of error is a generic one that can also occur with any software reinstallation or installation. And to fix this error, there are several suggestions you must check out. You can try to install or reinstall the program in a Clean Boot State or restart the Windows Installer Service. You could also try to re-register the Windows Installer Service or re-register the VBScript.dll file.

Option 1 – Install or reinstall the program in a Clean Boot State

It is possible that there are some third-party applications in your computer that are preventing the program from getting installed and to isolate this possibility, you need to boot your computer in a Clean Boot State and then try installing the program again. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.

• 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” checkbox 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” checkbox.
• 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.)
• After you’ve set your computer into a Clean Boot State, make sure that you’re signed in as administrator and then try to install the program again.

Option 2 – Try to restart the Windows Installer Service

The next thing you can do to fix the problem is to restart the Windows Installer Service. To do this, follow these steps:

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and then hit Enter to open the Windows Services Manager.
• Next, look for the Windows Installer service among the list of services shown.
• Once you found it, right-click on it and open its Properties.
• From there, click on the Stop button and then click on the Start button.
• But if it isn’t running, then just click on the Start button.

Option 3 – Try to unregister and re-register the Windows Installer Module

• Tap the Win + R keys to open the Run dialog box.
• Then type the “msiexec /unregister” command and hit Enter to unregister the Windows Installer Module.
• Next, type the “msiexec /regserver” command and hit Enter to re-register the Windows Installer Module.
• Now restart your computer and see if unregistering and re-registering the Windows Installer Module fixed the problem or not.

Option 4 – Try to re-register the vbscript.dll file

You may have to re-register the vbscript.dll file using the regsvr32.exe before you can successfully install the program and fix the error. The Regsvr32 tool is a command-line utility that can be used to register and un-register the OLE controls like DLL and ActiveX (OCX) control in the Windows operating system. Follow the steps below to use it.

• Open Command Prompt as admin from the WinX menu.
• Next, type regsvr32.exe vbscript.dll in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
• You should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

If you are dissatisfied with your internet speed on your computer but do not want to shell out more money for a faster package or simply there is not a faster package, lay down and enjoy this article where we will go through some common practices and tweaks which will result in increasing your internet speed. Please note that this guide will not be able to go beyond the limits of your internet provider's physical speed, this guide is made you can squeeze the maximum from your existing plan and eliminate speed drops.

1. 1. 1. Modify IRPStackSize

         Press ⊞ WINDOWS + R to open the run dialog In run dialog type RegEdit and press ENTER In registry editor find HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters Right-click on Parameters> New> DWORD 32 Name it IRPStackSize and change the value to 32 Save and reboot your computer.

      2. Add a Default TTL

         Press ⊞ WINDOWS + R to open the run dialog In run dialog type RegEdit and press ENTER In registry editor find a key Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters Right-click on Parameters> New> DWORD 32 Name it DefaultTTL and change the value to 64 Save and Reboot

      3. Close Background Applications which are using the internet

         If some applications are running in the background that are using the internet, your speed will be much lower. CLose them to gain speed.

      4. Modify the TCP1323Opts value

         Press ⊞ WINDOWS + R to open the run dialog In run dialog type RegEdit and press ENTER In registry editor find a key Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters There should be a DWORD Value, TCP1323Opts, if not, then create it. Right-click on Parameters> New> DWORD (32-bit) Value. Double-click on it and change its value to 1 Save and reboot

      5. Scan system for Viruses and other malware

         Viruses and malware applications can not only slow your entire system, but they can also reduce your internet speed as well. Do a complete scan of your system to be sure you do not have any malicious software on it.

If you got the FAULTY_HARDWARE_CORRUPTED_PAGE Blue Screen error on your Windows 10 computer then it is most likely caused by various factors. It could be caused by an incomplete installation or uninstallation of some applications or program, or it could also be caused by some exploit that intervenes with the normal functioning of the computer, as well as bad sectors on the hard disk, damaged system files, malfunctioned system drivers, modified Windows Registry files, or a Blue Screen occurrence during a Windows Update and many more. Getting this bug check means that a single-bit error was found on this page. It also indicates that this is a hardware memory error and to resolve it, you need to follow the suggestions laid out below but before that, it is recommended for you to create a System Restore Point first so that if anything goes wrong, you can always go back to the previous state.

Option 1 – Run a Memory Check to test RAM

Since the problem might have something to do with hardware memory, you need to test RAM by running a Memory Check using the Windows Memory Diagnostic. Refer to these steps to do so.

• Tap the Win + R keys to open the Run dialog box.
• Then type “mdsched.exe” in the field and hit Enter to open the Windows Memory Diagnostic.
• After that, the Windows Memory Diagnostic will give out two options such as:

1. Restart now and check for problems (recommended)
2. Check for problems the next time I start my computer

• Select any of the given options. After that, your computer will restart and check for memory-based issues upon the restart. If there are any issues, it will automatically them.

Option 2 – Run the System File Checker

System File Checker or 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 with good system files that might be the cause why you’re getting the FAULTY_HARDWARE_CORRUPTED_PAGE Blue Screen error. 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

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 3 – Check for conflicting or incompatible programs by putting your PC in a Clean Boot state

As mentioned, the FAULTY_HARDWARE_CORRUPTED_PAGE Blue Screen error might be caused by some problematic programs that clash with your existing operating system. Several users reported that numerous programs that are supposedly designed to enhance computer performance are causing conflict in the system instead. 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” checkbox 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” checkbox.
• 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.

Option 4 – Update or rollback drivers

If the first few options didn’t work for you, then it’s time to either update or roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Fatal error C0000034 happens during the installation of the Windows update and if you are one of the unlucky users who sadly run into this, keep reading as we will provide solutions to this error and how to get around it. Start from point 1 to the bottom and hopefully you will have your PC back into working order in no time.

1. Run Windows Update troubleshooter

   Usually, a built-in Windows troubleshooter can solve issues painlessly and fast, my advice is to try this as the first option, it is a simple and clean solution worth trying and in 90% it solves the issue all by itself.

2. Do a clean boot

   Using task manager, remove all nonessential applications and services from starting up, reboot your computer, and once it is cleanly booted try re-running the update process again, if the issue was running the application this time everything will work since the problematic application is not running.

3. Reset Windows update components to the default

   This solution requires you to use the Reset Windows Update Agent Tool to reset Windows Update components to default or use this PowerShell script to reset Windows Update Client. You can also manually reset each Windows Update component to default and then re-run the update.

4. Disable firewall and antivirus

   Altho not likely it is still a possibility that some firewalls and antivirus can detect windows updates as malicious software and cut them off. If everything else failed, disable the firewall and your PC protection and when it is fully disabled try updating.

5. Do automatic startup repair

   This should be the last thing to do but if everything else failed, do it. Perform Windows 10 Startup Repair. Once the startup repair completes successfully, you can re-run the update. The update should install without errors.

If you are trying to restore your computer using a System Image that has been created by the Windows Backup and Restore tool but encountered an error message instead that says, “Windows cannot find a system image on this computer”, you’ve come to the right place as this post will walk you through in fixing this error. Here’s the complete context of the error message:

“Windows cannot find a system image on this computer, Attach the backup hard disk or insert the final DVD from a backup set and click Retry. Alternatively, close this dialog for more options.”

In the error message, you are offered two choices – to either Retry or Cancel the operation. You can try to select Retry to try again but you will most likely get the same error if you do so. This kind of error can occur if the name of the WindowsImageBackup folder or any of its sub-folders has been modified. On the other hand, this error can also pop up if this folder or any of its sub-folders have gone missing or have become corrupted. To resolve the error, you can try to move the WindowsImageBackup folder or check its sub-folders. You can also try to isolate the System Image file or rename the System Image folder or remove all the unwanted sub-folders as well as use Command Prompt in Repair mode.

Option 1 – Try to move the WindowsImageBackup folder

The WindowsImageBackup folder must be stored in the root of the volume where it is stored, in line with the functioning of the System Restore utility. For example, if the WindowsImageBackup folder is stored in the “C:/Backups/System Restore Backups/New” location, then you have to move it to the C: drive as well.

Option 2 – Try to check the subfolders of the WindowsImageBackup folder

The classification of folders and files plays an important part to restore in restoring a computer from a System Restore point. Thus, if have modified the names of any files or folders inside the WindowsImageBackup folder, then you need to set the defaults. After that, run System Restore again and check if it fixes the error.

Option 3 – Try to isolate the System Image file

If the System Image file is stored in a USB storage device along with various System Restore images, then it’s no wonder why you’re getting this error. To set things right, you have to make sure that the System Restore image you wish to restore your computer from, is the only one that’s present at the root of the USB storage device.

Option 4 – Try renaming the System Image folder

If you have renamed the System Image folder prior to running System Restore, then it is most likely the reason why you’re getting the “Windows cannot find a system image on this computer” error. This error pops up because the System Restore utility in Windows 10 looks out for the WindowsImageBackup folder so if you have renamed it, you need to change its name back to what it originally was to fix the error.

Option 5 – Try to remove all the sub-folders of the WindowsImageBackup folder

If you have stored some foreign files inside the WindowsImageBackup folder, you need to get rid of them right away and return the folder to its default state as this folder must be left alone and should not be meddled with if you want to run System Restore smoothly.

Option 6 – Try to use Command Prompt in Repair Mode

• Open Command Prompt while your computer is in the Repair Mode.
• Next, type and enter this command where you need to replace “<Partition Letter>” with your drive’s letter: dir <Partition Letter>
• After you’ve found the WindowsImageBackup folder in any of the partitions, type and enter this command: dir <Parition Letter>WindowsImageBackup /s
• The command you entered will display all the contents of the folder exceeding 10 GB in total size. You can check and confirm the integrity of the folder and if you find that the integrity is violated, then it is the reason why you’re getting the error.

What Is Error 103?

Error 103 is an error that is usually encountered by those who use Google Chrome. This error is usually generated because of a conflict arising between Google Chrome and the antivirus program running on the user’s computer. Primarily, error 103 is an incompatibility issue. It is not critical in nature. However, since it will disrupt the smooth functioning of the browser, it is strongly advised to rectify this error that is generated due to any temporary conflicts between the logic of the two programs namely Google Chrome and antivirus. In layman's terms, it would be only justified to say that this error has a lot to do with the way programs react to each other in real-time.

Solution

Error Causes

When the error is displayed to the user, it usually states something like ‘chrome error 103 connection aborted’, ‘chrome error 103 err_connection_aborted’ or ‘Error 103 (net: ERR_CONNECTION_ABORTED): Unknown error. This begs the question, what triggers this error? Here it is important to understand that Google Chrome constantly applies to upgrade. In most instances, the upgrades almost go unnoticed. In the meanwhile, there are other programs running on any system such as firewall, Antispyware, or antivirus programs. All such programs govern the functionality of the web browser. Now, when the web browser attempts to update and any programs on the system view the update as a threat, the connection to the internet will be terminated. It is also important to understand that these programs will keep you from upgrading or from doing anything with your browser.

Further Information and Manual Repair

Before we move on to the discussion of fixing the underlying causes for error 103, it is important to understand all those programs that are most likely to generate this error. A list of all such programs is outlined below as follows.

• Kaspersky Pure 3.0
• Kaspersky ONE
• Kaspersky small office security 2013
• Kaspersky internet security 2013
• Kaspersky antivirus 2013

A downside associated with error 103 is that it won’t disappear on its own. That’s why it is important to make some manual changes as there are no tools available online to rectify this error automatically. Follow the steps listed below to easily fix the problem.

• Click on the Start button.
• In the search box, enter ‘expand.exe’.
• Right-click on the file that appears and select the option ‘Open Folder Location’.
• Now, copy the file and paste it at the destination ‘C:\Windows\System32’.
• If you are not able to find the file, it is advised you copy it from Windows Installation Disk.
• Now, click on the ‘Start’ button again.
• Find and select ‘Run’.
• Now enter ‘C: ’ in the search box and press Ok.
• Now right-click anywhere on the screen, select new, and then select folder.
• Rename this folder. Change the name from ‘New Folder’ to ‘Temp’.
• Now go to the Start button again.
• Select ‘Run’ once again.
• Type ‘cmd.exe’ in the command prompt and press Ok.
• Now type Command. Press enter.
• Now type this code as it is: ‘set TMP=C:temp’ and press enter.
• Now restart the browser.
• If it fails, install Google Chrome once again.
• Just make sure everything is in sync to avoid any data loss.

If you are trying to start a service using the Windows Services Manager but you got an error message stating, “The executable program that this service is configured to run in does not implement the service”, then you’ve come to the right place as this post will provide you instructions on how you can fix this error. Since almost all program requires service to run on your computer, if the service is not listed in the corresponding registry key, then you will most likely encounter this error on your Windows 10 computer. Here’s the entire content of the error message:

“Windows could not start the service on Local Computer. Error 1083: The executable program that this service is configured to run in does not implement the service.”

To fix this error, you have to add the service name in the respective host in the Registry Editor, and to do that, here are some steps you need to take on. Step 1: The first thing you have to do is to take note of the service name that’s given in the error message. For instance, you get the “Windows Management Service. Step 2: Next, you need to open the Services Manager by tapping the Win + R keys and typing “services.msc” in the Run dialog box, and then tapping Enter. Step 3: After opening the Services Manager, look for the Windows Management Service and once you see it, double click on it. This will open a new mini window. Step 4: From the newly opened window, copy the Service name and the Path to executable under the General tab. If the path to the executable is displayed as “C:/Windows/system32/svchost.exe -k netsvcs –p”, you need the “netsvcs” part only. Note that it can be different for different services and you need the part that comes after “-k”. Step 5: Now tap the Win + R keys again to open Run utility and type “Regedit” in the field and click OK to open the Registry Editor. Step 6: After that, navigate to the following registry path:

ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionSvchost

Step 7: From the given registry path, look for a key named “REG_MULTI_SZ” located on your right-hand side. This key is named after the “Path to executable” part. For instance, you should see “netsvcs”. Step 8: Double click on the REG_MULTI_SZ key and enter the Service name that you’ve copied earlier and then write it down at the end of the preset list. Step 9: Now save the changes you’ve made and try to open the program or run the service again.

In previous versions of Windows changing the system, the font was a pretty straightforward process, but it seems Microsoft did not want this feature to keep for whatever reason and there is no option as of the time of the writing of this article to do it in standard options in Windows 10. But do not worry, you are still able to customize your Windows and choose which font would you like to see inside it in all of its dialogs. You can choose whichever font you desire, the only prerequisite is it to be installed on your system. This guide will require you to change values in the registry of Windows itself so please follow step-by-step instructions and always make a backup of the registry before changing it in order to prevent some permanent Windows issues. All of that being said, let's start.

Setting new font

First thing is to open notepad, in the notepad paste the next block of code:

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts] "Segoe UI (TrueType)"="" "Segoe UI Bold (TrueType)"="" "Segoe UI Bold Italic (TrueType)"="" "Segoe UI Italic (TrueType)"="" "Segoe UI Light (TrueType)"="" "Segoe UI Semibold (TrueType)"="" "Segoe UI Symbol (TrueType)"="" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes] "Segoe UI"="NEW_FONT"

Where in "Segoe UI"="NEW_FONT" instead of NEW_FONT you need to write the exact name of the font that you wish to use as a system font. Once you have replaced the default system font with your desired one, go to File and save as, from file type drop-down menu, choose all files and save this file as .REG type giving it whatever name you wish. When the file is saved, close notepad, right-click on the saved file and choose the merge option. Confirm with YES and click on OK. Reboot your system and your Windows will now use the font of your choice as its default system font.

Restoring default font

If you wish to return the old default system font as it was, follow the same steps but in your notepad paste this code:

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts] "Segoe UI (TrueType)"="segoeui.ttf" "Segoe UI Black (TrueType)"="seguibl.ttf" "Segoe UI Black Italic (TrueType)"="seguibli.ttf" "Segoe UI Bold (TrueType)"="segoeuib.ttf" "Segoe UI Bold Italic (TrueType)"="segoeuiz.ttf" "Segoe UI Emoji (TrueType)"="seguiemj.ttf" "Segoe UI Historic (TrueType)"="seguihis.ttf" "Segoe UI Italic (TrueType)"="segoeuii.ttf" "Segoe UI Light (TrueType)"="segoeuil.ttf" "Segoe UI Light Italic (TrueType)"="seguili.ttf" "Segoe UI Semibold (TrueType)"="seguisb.ttf" "Segoe UI Semibold Italic (TrueType)"="seguisbi.ttf" "Segoe UI Semilight (TrueType)"="segoeuisl.ttf" "Segoe UI Semilight Italic (TrueType)"="seguisli.ttf" "Segoe UI Symbol (TrueType)"="seguisym.ttf" "Segoe MDL2 Assets (TrueType)"="segmdl2.ttf" "Segoe Print (TrueType)"="segoepr.ttf" "Segoe Print Bold (TrueType)"="segoeprb.ttf" "Segoe Script (TrueType)"="segoesc.ttf" "Segoe Script Bold (TrueType)"="segoescb.ttf" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes] "Segoe UI"=-

Reboot your system and your Windows will now revert the font of your choice as its default system font.

The Local Security Authority Subsystem Service or LSASS.exe is a process in the Windows operating system that is valuable as it enforces the security policy on the computer. Every time you log in to the Windows Server, the LSASS.exe is the one that handles the password changes and creates the access tokens while updating the security log. However, it is also frequently targeted by malware and is often imitated. The original location of this file is at “C:/Windows/System32” so if you open the Task Manager and notice that a process with a similar name has a different location then it is definitely a threat and is exploiting the security of your computer. To resolve issues related to LSASS.exe, here are some fixes that could help.

Option 1 – Use the Performance Monitor’s Active Directory Data Collector

Note that this option will only work on the recent Windows server versions. Refer to the steps below to use the Performance Monitor’s Active Directory Data Collector set on your computer.

• Tap the WINKEY + R button to open the Run dialog box.
• Then type “Perfmon.msc” in the field and hit Enter to open the Performance Monitor and from there open the Server Manager.
• Next, navigate to Diagnostics > Reliability and Performance > Data Collector Sets > System from the left side of the navigation bar.
• Then right-click on “Active Directory Diagnostics” and select Start from the context menu. This will take about 5 minutes or 300 seconds depending on the performance capabilities of your hardware to gather the data required and then take some more time to compile a report from the gathered data. Note that these timings are dependent on one another.
• After the report is compiled, you can find it under Diagnostics > Reliability and Performance > Reports > System > Active Directory Diagnostics. The report will contain all the information as well as conclusions. However, it does not mean that it will also contain the exact cause of the problem with LSASS.exe. Nevertheless, it should help you in fixing the problem.

Option 2 – Try to run the System File Checker

System File Checker or 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 that might be the cause why the LSASS.exe file is having some issues. To run the SFC command, follow the steps given below.

• Type “cmd” in the Start search and then right-click on the appropriate search result.
• Next, select “Run as administrator” to open Command Prompt with admin privileges.
• 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.

 Now restart your computer and see if the problem is fixed or not.

Option 3 – Put your computer in a Clean Boot State

If none of the options given above helped, you can try putting your computer in a Clean Boot State as this can help you in finding any incompatible programs that’s causing the problem.

• 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.

Once you’ve found any incompatible programs, you need to uninstall them. Refer to the steps below to do so.

• In the search box, type in “control” and then click on Control Panel (desktop app) among the search results.
• After that, select Programs and Features from the list which will give you a list of all the programs installed on your computer.
• From there, look for the concerned program and select it and then uninstall it.

Note: If you have downloaded the app from the Windows Store, you can simply right-click on it from the application list and then uninstall it.