Choosing default browser in Windows 11

So far we probably all know what are good new and exciting features that W11 is bringing to the table, let’s talk now about features that will be removed and are not there but we had them in W10

1. Taskbar, do not worry, it is still there but it will be locked hard only to the bottom, people is removed, applications cannot customize areas and some icons will not appear in the system tray.
2. Start Menu, No more named groups, cannot be resized, live tiles are history and pinned apps and sites will not migrate
3. Tablet mode is completely removed
4. Touch keyboard will not dock or undock on screen sizes bigger than 18 inches
5. The timeline feature is no more
6. The wallet is also removed
7. Cortana is not active on first boot experience and it is no longer pinned to the taskbar
8. Desktop wallpapers are not synched anymore when using an MS account
9. IE is disabled, IE mode in edge here to fill the gap
10. Math panel is removed with math recognizer as separate install on demand
11. News and interests are now Windows Widgets
12. Quick status is no longer on the lock screen nor in the settings
13. S Mode exclusive only to Windows 11 home edition
14. Snipping Tool continues to be available but functionality has been replaced with the Snip & Sketch tool functionality.3D Viewer, OneNote for Windows 10, Paint 3D, and Skype won't be installed anymore on new systems. They remain available when systems are upgraded.

As you know, Windows Update is the source for everything latest for Windows from Microsoft. Your computer receives essential updates frequently because of the Windows Update service and this Windows Update mechanism depends on various services such as Background Intelligent Transfer Service or BITS, Windows Server Update Service, Windows Update service, and many more. Although it may seem like a complex delivery system, it is a very efficient one. However, it is not without its issues as it still encounters errors every now and then. One of these errors is 80244019 which applies only to the Windows Server operating systems and to resolve it, you need to determine its cause. The Windows Update Error 80244019 is most likely caused by faulty and corrupted DLL files or Registry Entries, connectivity issues, and outdated configuration of Windows Update service on the client end. Moreover, the error can also be caused by malware or if a file is not found on the server. This error can lead to a number of system issues like Startup and shutdown issues, software installation errors, external devices connection, system lags, unexpected application, and program issues, and many more. To resolve the problem, refer to the options given below.

Option 1 – Restart some Windows Update services

The first thing you have to do is to restart Windows Update-related services. Refer to the steps below to do so.

• 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 stop bits

• After entering these commands, it will stop the Windows Update Service and the Background Intelligent Transfer Service.
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files there by 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.
• Once all the contents in the Software Distribution folder are deleted, restart your PC and then go back to Command Prompt and input the following commands again.

net start wuauserv net start bits

 Since the folder has already been flushed, it will be populated afresh the instant your restart your computer and open Windows Update.

Option 2 – Try turning on the Data Execution Prevention or DEP

The problem might be caused by disabled Data Execution Prevention which is why you have to make sure that it’s turned on.

Option 3 – Run the Windows Update Troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing Windows Update Error 80244019. 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.

Option 4 – Try reconfiguring the Windows Update Settings

You can also try to reconfigure the settings in the Windows Update section to resolve the error.

• Tap the Win + I keys to open the Windows Settings.
• Next, click on Update & Security > Windows Updates > Update Settings and from there, click on the Advanced Options.
• After that, uncheck the “Give me updates for other Microsoft Products when I update Windows” option.
• Now restart your computer to successfully apply the changes made and then check if the Windows Update error is now fixed.

Option 5 – Try to manually install the Windows Updates

Windows Update Error 80244019 might be due to a Windows Update that has failed. So if it is not a feature update and only a cumulative update, you can download the Windows Update and install it manually. But first, you need to find out which update has failed, and to do so, refer to the following steps:

• Go to Settings and from there go to Update and Security > View Update History.
• Next, check which particular update has failed. Note that Updates that have failed to install will be displayed under the Status column which has a label of “Failed”.
• After that, go to the Microsoft Download Center and look for that update using its KB number and once you find it, download and then install it manually.

Note: You can also use the Microsoft Update Catalog, a service from Microsoft that provides a list of software updates that can be distributed over a corporate network. With the help of this service, it can be easier for you to find Microsoft software updates, drivers as well as fixes.

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.

Browsing the internet doesn’t always go smoothly, you might encounter ads, pop-ups, viruses, malware, and even errors. In this post, we’ll walk you through how you can fix the 502 Bad Gateway error that you might encounter in browsing the internet. This kind of error suggests the server which is the one that’s acting as a gateway to facilitate in taking your request to the server and bring some response back has received an invalid response or even no response at all. It could be that the connection is broken or that there is an issue on the server-side that returns an invalid response. Even though the 502 Bad Gateway error is a server-related error, there are still a few things you can try that might help resolve it, if tapping the Ctrl + F5 keys does not resolve the problem. Keep in mind that it doesn’t matter what website you open as this error can appear on any website. To resolve the problem, you need to follow the options prepared below.

Option 1 – Check the network cable connections and restart your router

As with other connection problems, this is the most basic thing to do before you try other troubleshooting options because the root cause of the problem might be as simple as a cable not connected properly or a router that just needs to be restarted. Thus, checking the network cable connection to see if there is anything out of order can help as well as restarting your router.

Option 2 – Reset Winsock, TCP/IP & Flush DNS

Resetting Winsock, TCP/IP, and flushing DNS might help you resolve the issue. To do so, follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.

1. netsh winsock reset – type in this command to reset Winsock
2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
3. ipconfig /flushdns– type in this command to flush the DNS cache

• Next, restart your PC and check if the problem’s fixed.

Option 3 – Change the DNS

Changing the DNS server for your network can also help you fix the 502 Bad Gateway error. You can use a public DNS like the Google Public DNS, Open DNS, Yandex DNS, Comodo Secure DNS, and many more. All you have to do is to override the default DNS settings on your PC so that you can specify which DNS server is used as well as which IP address should be used for a specific domain.

Option 4 – Try updating the Network Adapter Driver

Follow the steps below to update your Network Adapter Driver:

• Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
• From there, expand the list of all the network drives and update each one of them.

Note: If updating the network drivers didn’t help in fixing the problem, you can also try to uninstall the very same drivers and restart your Windows 10 PC. After that, the system itself will reinstall the drivers you just uninstalled. Alternatively, you can also download and install the drivers from the manufacturer’s website directly.

Option 5 – Try a Network Reset

When all else fails, you might have to consider resetting your entire network settings. Simply follow the steps below to do so.

• Click on the Start button and then click on the gear-like icon for Settings to open it.
• Next, select Network and Internet.
• Then scroll down and look for “Network Reset” – click on it and then click on the Reset now button.

If you are running the Windows Update service but decided to stop it but you encountered an error message instead that says, “The Windows Update service could not be stopped”, read on as this post will help you fix the problem. This kind of error appears when you use the Command Prompt to stop the Windows Update service, especially if you are using cmd without admin privileges. A lot of users reported that they were not able to disable the automatic Windows Update in Windows 10 using Command Prompt. The command used to stop the Windows Update service is the “net stop wuauserv” command. However, when some users executed this command, they got the error message. So if you are one of these users that can’t stop the Windows Update Service via Command Prompt, you can try to fix that using PID as well as checking the Service dependencies. For more details, follow the given options below.

Option 1 – Try to stop the Windows Update service via PID

In case you don’t know, each running service or process has its own unique ID or PID and you can find it in the Task Manager. You can use it to stop the Windows Update service. How? Refer to these steps:

• Tap the Ctrl + Shift + Esc keys to open the Task Manager.
• Next, go to the Services tab and look for the service named “wuauserv” and get its PID.
• After that, type “cmd” in the Windows Start search and right-click on Command Prompt from the search results and then select the “Run as administrator” option.
• After opening Command Prompt with admin privileges, execute this command: taskkill /f /pid <PID>

Note: You need to replace “<PID>” with the PID of the “wuauserv” service. For instance, the PID is 6676, then this is how the command should be “taskkill /f /pid 6676”.

• After you execute the command, you will this message on your screen, “SUCCESS: The process with PID 6676 has been terminated” which indicates that you have stopped the Windows Update service successfully.

Option 2 – Try to check the Service dependencies

Dependencies of a Windows Service in Windows 10 are when windows services depend on other services. Such is the case with the Windows Update service – it also depends on three different services such as the Remote Procedure Call or RPC service, DCOM Server Process Launcher, and the RPC Endpoint Mapper. Meaning to say, if two of these services are not working as expected, then the dependant service will also be affected. This could be the reason why the Windows Update service could not start.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “services.msc” in the field and hit Enter to open Windows Services.
• From the list of Services, look for the following services:
  • Remote Procedure Call (RPC) Service
  • DCOM Server Process Launcher
  • RPC Endpoint Mapper
• After you find these services, double click on each one of them and check whether the Startup type for all is set to Automatic and the Service status is set to Running or not.
• If the service status is not running, then click the Start button. Afterward, check if you can now run the Windows Update service.

Fix Rstrui.exe error in Windows 10

Rstrui.exe is a service assigned to controlling system restore, it is considered an essential part of the Windows system and without it working you will not be able to perform a system restore operation. Without system restore working you will not be able to "rewind" Windows into a working state if needed which can create in itself many new complications. Luckily we have working solutions for this specific problem, so get ready, and let's start.

SFC scan

Sfc scan is a built-in Windows tool that scans and repairs system corrupted and missing files. To run it open up the command prompt in administrator mode and type in it: SFC /SCANNOW then, let the whole process finish, do not interrupt it, and reboot after it is done.

DISM scan

Similar to SFC scan, DISM is also a built-in tool for fixing files linked to Windows essential working. Start a command prompt in administrator mode and type in: DISM /Online /Cleanup-Image /RestoreHealth Again let the process completely finish and then reboot your system.

Scan for viruses and other malware

Viruses and other malware can seriously damage the system and with it rstrui.exe along with it. Scan your system with Windows defender or even better with some other dedicated security suite to eliminate malicious threats if they exist.

Update Windows

Keeping Windows updated can bring you more good than harm, it is very advisable to keep it up to date all the time so all security leaks and bugs are repaired and that you have your OS in top-notch working order. Updating can also fix corrupted system files or replace them with newer versions so if your Windows is not updated go to update central and do it. Congratulations, you have just Fixed the Rstrui.exe error in Windows 10 all by yourself. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily. Your Rstrui.exe error in Windows 10 should have been fixed now.

Whether you’re using Windows Update or upgrading or installing on your Windows 10 computer, you can’t really tell if things will go smoothly as there are times when you might encounter some issues that prevent you from completing the update or upgrade or the installation. One of the errors you can encounter is error 0x80070057. Usually, when you receive this error, it means that one or more arguments are not valid. You can encounter this error in the following cases:

• Windows Update, Upgrade, or Installation
• Windows Backup, The parameter is incorrect
• Partitioning a Disk
• System Image Restore error 0x80070057
• Downloading Windows Store apps

Keep in mind that the troubleshooting steps you need to take will depend on the scenarios you are in. Thus, you need to go over each one of the troubleshooting options given below and make sure to carefully follow each one of them but before you proceed, you have to create a System Restore Point first.

Option 1 – Run the Windows Update Troubleshooter

The first thing you can do to fix error 0x80070057 is by running the Windows Update Troubleshooter. It is a built-in tool in Windows that helps users resolve any issues with Windows Update. All you need to do to run it is go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button.

Option 2 – Use the Registry Editor

If you get the error 0x80070057 during Windows Backup, then you need to make some modifications to the Windows Registry. To do so, follow these steps:

• Tap the Win + R keys to open the Run dialog box.
• Type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to the following registry key:

HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftSystem

• Then create a new DWORD value and input “CopyFileBufferedSynchronousIo” as its name and put “1” as its value.
• Close the Registry Editor and restart your computer then check if the error is fixed or not.

Option 3 – Run the DISM tool

Running the DISM Tool helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Note: If it happens that the Windows Update client is broken, you need to run the following command to repair it then restart your PC and click on Update once again.

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess

Option 4 – Flush the contents of the SoftwareDistribution folder

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.

Option 5 – Reset Windows Store Cache

• Right-click on the start button and click on Command Prompt (administrator).
• Next, type in the command, “wsreset.exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.

Option 6 – Run SFC scan

Running the SFC scan or System File Checker might also help in fixing error 0x80070057.

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

As previously announced by Google feature to quickly delete the last 15min of browsing history via one button is rolling out now. For now, only Apple users will be available to use this feature but the Android update is scheduled for later this year, a strange move by Google but it is what it is. For anyone who is unfamiliar with this feature, basically, Google wants a quick way to remove the last 15min of browsing history as a supposedly stated request to make deleting browsing history much easier. Google came up with this idea so you can keep the previous history intact but remove just 15min time frame, no additional explanation was given on why 15 but I presume it is some round number that came up as the middle one with research, read telemetry info. Using quick delete requires being signed into Search with a Google account. Users can access the option by simply tapping on the avatar icon to access the settings then choosing "Delete last 15 minutes."

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.

For PC users that are blind or have low vision, the Narrator accessibility feature in Windows 10, lets you use your PC without a display or mouse to complete common tasks – it reads and interacts with things on the screen, like text and buttons. The narrator can be used to read and write an email, browse the internet, and work with documents. In Windows 10, there are a lot of options for Narrator that you can customize. You can change its keyboard shortcuts, personalize Narrator’s voice, enable Caps Lock warnings, and more. You can choose the voice for the Narrator, adjust the speaking rate, pitch, and volume. To change the default audio output device used to play the voice of the Narrator in Windows 10:

• Press the ⊞ WINDOWS + I
• From the Settings menu, click Ease of Access.
• Click Narrator on the left pane.
• In the Narrator window, on the right pane, toggle the button to On to enable Narrator if required.
• Scroll down to the Personalize Narrator’s voice section.
• For the Select where you hear Narrator’s voice option, click the drop-down and select the audio output device you want from the list. Please know that you will not be able to choose if you do not have multiple audio output devices connected to your Windows 10 computer.
• Exit Settings when done.

If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.