Enable or disable Fast User Switching

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

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

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

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

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

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

Option 2 – Run the Windows Update Troubleshooter

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

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

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

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

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

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

Each time you open an application inside your Windows 11 operating system, it is opened with standard privileges. Now, please note that your account privileges and application privileges are two different things, you might be the administrator of the system but when you open the app, it still opens with standard privilege. Most of the time running applications with typical settings is fine but from time to time we might have some applications that will require running with administrator privilege in order to work properly. In this case, it is very easy to do it, you just right-click and choose run as administrator. Although a very easy solution, it can be quite annoying if running the app is on a daily basis or even more times per day. If this is the case then right-clicking and choosing to run as administrator can be a daunting task, sometimes you can even forget to run it like this in heat of work and some unforeseen consequences might occur. Luckily there is an easy hack so you can open the chosen application each time as an administrator with a simple double click each time.

Setting application to run as administrator always

1. Locate application executable file
2. Right-click on in and choose properties
3. Click on the Compatibility tab
4. Check the box next to Run this Program as an Administrator
5. Click on Apply
6. Click on OK

From now on each time you open an application normally with a double click, it will be opened as administrator privileges.

There are a lot of users who use their Windows 10 PCs to create and access data on their servers using their network. However, some of them reported getting an error saying that the server is not accessible. Here’s the full content of the error message:

“\server is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Logon Failure: The target account name is incorrect.”

If you are among the users who experience the same issue, read on as this post will help you resolve this error when accessing your server. But before you start troubleshooting the problem, you might want to perform System Restore, especially if tend to create one. To use System Restore, here’s what you have to do:

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

If System Restore didn’t help in fixing the ACPI.sys Blue Screen error now’s the time for you to make use of the potential fixes laid out below.

Option 1 – Try rebooting your router

The first thing you can try to do to fix the error is to simply restart your router. All you need to do is reboot the router from its Admin panel or you can also turn it off manually and turn it back on after a couple of seconds so that it can completely reboot. Once you’re done, try accessing your server again and see if the error is now fixed.

Option 2 – Try checking the status of the Workstation Service

You might want to check the status of the Workstation Service as the error might have something to do with it.

• Tap the Win + R keys on your keyboard to launch the Run utility.
• Then type “services.msc” in the field and click OK or hit Enter to open the Windows Services Manager.
• After opening the Services Manager, you will see a list of all the services on your computer and from there, locate the Workstation Service.
• Double click on the Workstation Service to open its Properties.
• Next, Stop the Service and Start it again or you can also right-click on it and select Restart and then make sure that its Startup type is set to Automatic.
• Now restart your computer and check if the error is fixed.

Option 3 – Try to change the File Sharing Connections setting

You can also try to change the File Sharing connections setting. All you have to do is go to Control Panel > Network and sharing center > Advanced sharing settings > File sharing connections. From there, you need to select “Enable file sharing for devices that use 40 or 56-bit encryption and check if it helps in fixing the problem. If not, undo the changes you’ve made and proceed to the next given option.

Option 4 – Try checking the Network Configuration

Checking the Network Configuration can also help you fix the error. Refer to the steps below to do so:

• Right-click on the Wi-Fi connection or on the Ethernet connection icon located in the system tray.
• Then select open Network and Internet Settings and then click on the “Change Adapter Options”.
• After that, a new window will appear and from there, select the network connection that connects your computer to your network – this can either be a Wi-Fi connection or Ethernet connection.
• Right-click on that connection and select Properties where you will see a list of items.
• Select the Internet Protocol Version 4 or Internet Protocol Version 6 from those items according to your system requirement.
• Then click on the Properties button.
• Check if everything is now configured as to how it is supposed to be and then check if the error is resolved.

Option 5 – Try to reset Winsock, TCP/IP & Flush DNS

You might also want to try resetting Winsock, TCP/IP, and flushing DNS might help you resolve errors. 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 6 – Run the Network Adapter Troubleshooter

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.

Intel announced that Pat Gelsinger (CEO) and Dr. Ann Kelleher  (technology Department head) will discuss Intel’s process and packaging innovations on an upcoming webcast that will happen on July 26^th. The spokesman will talk and provide a deeper look at the process and packaging roadmaps for Intel. As we know Intel is planning to expand its production capabilities, outsource some of its technologies and offer foundry services to other chip design companies. The strategy will also include a shift to a 7nm process and Intel’s effort to set itself again as leader of CPU performance by 2024. There is also a chance that we will hear exact plans for Intel in the next three or four years. Intel didn't reveal much else about what Gelsinger and Kelleher plan to discuss during the webcast. The event will be streamed on July 26 at 2 pm PT via the Intel Newsroom; it will also be available to watch on-demand after the stream ends.

When Windows 10 was introduced as an upgrade to Windows 7 and 8, a lot were thrilled because of its new features. One of the most interesting features that this has is the Microsoft Store. Just like in our tablets and smartphones, we can now download our favorite apps from a trusted source. Without the Microsoft store app, you can’t download any applications that you can use on your computer. But what happens if you can’t open your Microsoft Store or you accidentally uninstalled it? The most common error that users encounter when accessing Microsoft Store is the error code 0x80072efd. This error code appears when there is a problem with the internet connection. To resolve this, troubleshoot your modem by doing a simple power cycle. Turn off your modem and wait for a couple of minutes and turn it back on. It should refresh your internet. This works if there is really no problem on the Service provider’s side. Disable your Proxy server, if you are using one to access the internet. To do this, press Windows + R keys on your keyboard. Type “inetcpl.cpl” in the box and go to Connection. Next, click on LAN settings then tick on the box next to Automatically detect settings. Uncheck the box below Proxy Server Among the useful apps that came with the Windows 10 upgrade is PowerShell. It allows you to install and uninstall individual and all apps by using a series of commands. So you don’t have to worry if you can’t find your Microsoft Store or if you accidentally delete it. To access PowerShell, type in the word PowerShell into the search box found beside your Window Icon. Look for PowerShell from the results and right-click on it and hit Run as Administrator.

When you are in the PowerShell window, enter the command below:

Get-AppxPackage -allusers Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"

Another option is to download a Windows Update Troubleshooter. After you download it, open the troubleshooter tool and follow the steps. If you saved the file instead of directly opening it, go to the folder where the troubleshooter was saved and double click on the wu.diagcab file to rub the troubleshooter. One of the most interesting error codes that you might encounter when accessing the Microsoft store is error code 1. This particular error code is resolved by changing your PC’s region to the United States. To do this, go to Settings and look for Time & Language. Then go to region and language. Under the Country or region, choose the United States from the dropdown menu then restart your computer. The troubleshooting procedures above are the most common solution to resolve the problem on Microsoft Store issues but there are times that these procedures won’t work. If you are not confident to resolve this through the procedures mentioned in this article, there are so many tools online that you can download to help you out. It also helps to contact Microsoft or consult a technician to ensure that you are doing the correct procedure.

There are times when you might notice that the Drive letter from the File Explorer is missing, right after you install an update in your Windows 10 computer. So if you are facing this issue right now, then you’ve come to the right place as this post will guide you on what to do to fix it. In case you don’t know, a drive letter represents a single alphabetic character which is through A-Z typically. This could be assigned to a physical disk partition, floppy disk drive or the removal device/ CD-ROM/ mapping network drive in your PC. In most cases, the drive letter “C:” is assigned to the first disk partition where the running Windows is installed. Thus, if the assigned letter is missing from either the Disk Management or the Windows File Explorer, it could result in inconveniences or will leave the partition inaccessible. To fix this problem, you can try to show the missing drive letters manually or make sure that the drive has a drive letter assigned in the Disk Management as well as assign the letter using a tweak in the Windows Registry. For more details, refer to the options provided below.

Option 1 – Try to show the missing drive letters manually

• Open the Folder Options from the Start Search and go to the View tab,
• Next, scroll down on the list of given options until you see the “Show drive letters” option and then check the box that’s marked against this option.
• After that, click on the Apply and OK buttons and then go back to the “This PC” window. You should now see the drive letters

Option 2 – Make sure that the drive has a drive letter assigned in Disk Management

As you know, every drive is assigned a drive letter in Disk Management. However, if it goes missing, you can still get it back through Disk Management. To do so, follow the steps below.

• Open Disk Management and from there, right-click on the menu of a partition or volume and you should see a function named “Change Drive Letter and Paths”.

Note: This function allows you to add the drive letter, remove the drive letter and change the drive letter. If the last option, namely, “Remove”, is selected and applied, the letter of the drive will be removed and won’t appear in Disk Management. Thus, this could be one of the reasons why a drive letter is missing.

• You need to click on “Add” to assign a letter to the selected drive in order to reverse the change. Note that you must assign the drive with the original letter because if not, the programs that rely on the original letter might not work as expected.
• If the original letter is already taken by a new drive, you need to change the letter of that new drive to another available letter.
• Then allocate the released letter of the targeted drive.

Option 3 – Try assigning the letter using a Registry tweak

The next thing you can do to fix the problem is to assign the letter using a tweak in the Windows Registry but before you do that, make sure that you create a System Restore point first, after that, follow these steps:

• Tap the Win + R keys to open Run and type “Regedit” in the field and then tap Enter to open the Registry Editor.
• Next, navigate to this registry path: HKEY_LOCAL_MACHINESYSTEMMountedDevices
• From there, check if a device is shown as being mounted at the specific drive letter and then right-click on that drive letter.
• Select the “Rename” option from the right-click menu to change the letter to any other available letter.
• Exit the Registry Editor and restart your computer.

Option 4 – Try to format the destination drive

Formatting the drive can also help you resolve the error. To format it, follow these steps:

• To get started formatting your drive, tap the Win + E keys and then go to the access page of the drive.
• Next, right-click on the drive and select Format.
• After that, uncheck the “Quick Format” option and then format your drive properly.
• Now once the formatting process is finished, unplug the drive and plug it back in afterward.
• Check if the error is already fixed. If the drive is not initialized, tap the Win + R keys and hit Enter.
• After opening the Run dialog box, type “diskmgmt.msc” and hit Enter to open Disk Management.
• From there, right-click on the drive volume and select initialize disk.
• Next, select the correct partition type and proceed.

As of late, many users reported getting an error in Windows Sandbox that has an error code of 0x80070015. According to users, they encountered this error when they tried to start Windows Sandbox. Based on the error code, it seems that there are some problems with the supporting services of Windows Sandbox that trigger the error. It is possible that these services are misconfigured or that they are outdated and have to be updated. Here’s the complete message of the error:

“Windows Sandbox failed to start. Error 0x80070015. The device is not ready. Would you like to submit feedback about this issue?”

If you are one of the users who encountered this kind of error in Windows Sandbox, then you’ve come to the right place as this post will help you sort this problem out. All you have to do is follow each one of the options provided below.

Option 1 – Make sure that all the supporting processes and services of Windows Sandbox are running properly

If running Windows Sandbox as an administrator didn’t fix the error, you have to ensure that all related processes for Windows Sandbox are running properly. To do that, follow these steps:

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, from the list of services, look for the following services in the given order:
  • Network Virtualization Service: (Startup type: Manual)
  • Virtual Disk: (Startup type: Manual)
  • Hyper – V Virtual Machine: (Startup type: Manual)
  • Hyper – V Host Compute Service: (Startup type: Manual)
  • Container Manager Services: (Startup type: Automatic)
• After you find the aforementioned services, restart each one of them.
• Once done, try to open the Windows Sandbox again and see if the error is fixed or not.

Option 2 – Try to install any pending Windows Updates

If the second option still didn’t work, then you might want to check Windows Updates on your computer and see if there are any pending Windows Updates you have to install. All you have to do is go to the Windows 10 Settings app and then go to the Windows Updates section and click on the “Check for updates” button to check if there are any pending updates that are needed to be installed. This could fix the Windows Sandbox Error 0x80070015.

Option 3 – Try to run Windows Sandbox as an admin

• In the Start Menu, scroll down until you see the entry for the Windows Sandbox.
• Then right-click on it and select More and then select the “Run as administrator” option to open it with admin privileges.
• Next, if a User Account Control or UAC prompt pops up, just click on Yes to proceed.
• You should now be able to open the Windows Sandbox without the error. However, if the error persists, proceed to the next given option below.

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

Changes and features

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

Fixes

Taskbar:

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

Settings:

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

File Explorer:

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

Search:

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

Widgets:

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

Other:

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

Known issues in Windows 11 repaired

Start:

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

Taskbar:

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

Settings:

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

File Explorer:

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

Search:

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

Widgets:

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

Store:

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

Windows Security:

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

Localization:

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

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

Error 0x80004005 - What is it?

Error 0x80004005 is a typical Outlook error. This error code occurs either when sending emails or receiving them. The error message may be displayed in either of the following formats:

‘Sending and receiving reported error "0x80004005": The operation failed.’ ‘This message could not be sent. Try sending the message again or contact your network administrator. The client operation failed. Error is [OX80004005- 0X0004B9-OXOO501].’

Error Causes

There are several causes for the error 0x80004005 such as:

• The Script Blocking Feature Enabled While Using Norton Antivirus
• Spyware
• Viruses
• Registry problems-Missing or corrupt registry keys

It is advisable to repair and resolve error 0x80004005 immediately as it may cause a great deal of inconvenience to you. This error may hamper your ability to receive and send emails from your Outlook account and lower your productivity too as you may be unable to communicate with your peers.

Further Information and Manual Repair

To fix error 0x80004005, you don’t have to wait for the network personnel or be a technical expert yourself. This may be a critical error but the good news is that it is easy to resolve. Here are some effective methods and quick fixes to resolve the error 0x80004005 instantly.

Method 1: Disable Script Blocking Feature in Norton Antivirus

After installing Norton Antivirus on your PC, if you start experiencing the Outlook error 0x80004005, then the best way to resolve it is to simply disable the script blocking feature. However, the downside of this is that by disabling this feature your PC will become vulnerable to viruses and malware.

Method 2: Disable the New-Mail Notification Feature in MS Outlook

If you don’t have Norton Antivirus downloaded on your PC, then try method 2. This method involves disabling the new-mail notification feature in MS Outlook. The error code 0x80004005 is often resolved by switching off this feature. Try it to see if it works. To disable the new-mail feature all you have to do is open your Outlook account and then go to the Tools menu, then go to Options and then select the ‘Preferences’ tab. After that click on the ‘Emails Options’ tab and then simply uncheck the check-box against ‘Display a notification message when new mail arrives’. To confirm changes press OK.

Method 3: Scan for Viruses

The error 0x80004005 may also be triggered due to viral infection or spyware. Such malicious software enters your PC through phishing emails and while downloading files and attachments. You may not be aware of this but your PC may be infected by viruses. It is important you remove them immediately as they can expose you to serious risks including privacy issues, identity thefts, data breaches, and more.

On September 18th, 2017, Cisco’s Talos announced that CCleaner, a popular utility with billions of worldwide users, had been compromised by hackers, and was used to unwittingly distribute hidden malware in its installer. Later in the day, Piriform, the publisher of CCleaner, confirmed the problem.

Undetected by all but 1 major antivirus including CCleaner’s own parent company, this occurred for over a month and impacted over 2.7 million users. Users of CCleaner v5.33.6162 and CCleaner Cloud v1.07.3191 for 32-bit Windows are affected. These downloads were live on CCleaner’s official site from August 15th to September 12th, 2017. Anyone who downloaded the program during this time could be affected. The company claims that while the hackers set up the backdoor and many users were impacted, that the perpetrators have been arrested and that the malware never successfully performed its full task and compromised user’s PCs or sent out their data; in the wake of recent security breaches such as Equifax, users are understandably worried. Given the severity of the threat of hacking and data theft, users should take action immediately if they have CCleaner.

Technical Details of CCleaner Malware Injection

First reported by Talos, the malware, which was hidden in the CCleaner installer without the publisher noticing (despite them being owned by Avast, a massive Anti-virus company), modified a core program DLL file to evade detection, and creates several registry keys. Not only were these files not flagged by any major Anti-Virus, but they were also even digitally signed by Piriform via their Symantec certificate, meaning your PC and security program would likely whitelist and trust the malicious installer. The malware gathers personal information on a user’s PC, including IP address and running programs, and sends it to a remote server. In our testing, the program sent data to IP 216.126.225.148.

Restore Your PC (If Possible)

As of the publication of this article, there have been no assurances given that updating or even uninstalling CCleaner will remove the malware is installed. The only action thus far has been shutting down the remote server where user data was being sent has been shut down by authorities. For this reason, it is best to remove the underlying malware separately, as its presence represents a serious security threat. Unfortunately, as this could have been installed as far back as August 15th, 2017, your System Restore points may not go back that far, or even if they do, restoring to such an outdated point may cause unintended problems with other programs you use and potentially lost files and data. Manually backing up files and doing a full format or clean Windows installation would likely be successful in fully removing the malware, but is extremely time-consuming and can be difficult for many PC users. Unfortunately, this makes a PC Restore or format an unattainable option for many.

Update CCleaner to the Latest Version

While CCleaner has told users to update to the latest version of the program. Prior to doing so, we recommend fully uninstall CCleaner, ensuring you check its program files folders and registry keys, manually deleting any remnants, and then re-downloading the latest version from the official site and reinstalling clean.