Can’t remove Bluetooth mouse & keyboard

Error code 0x803f7000 -What is it?

Error code 0x803f7000 refers to an issue in Windows 10 with downloading apps through Windows Store. When you choose the app or game to download, it heads to Downloads in the Store app. Then it says it is acquiring a license but then fails. When you click the “See details” link, you see the error code 0x803F7000. It could mean that the date and time or region settings in your Windows 10 are incorrect or there are some problems with the Windows Store Cache.

Symptoms

• This error appears when you are running Windows 10 and trying to download an app through the Microsoft store. The error code may appear with this message: “Something went wrong. The error code is 0x803f7000, in case you need it”
• You might also see this message along with the error code: "It looks like you've reached your device limit for installing apps and games from the Store on your Windows 10 device. If you want to install apps and games from the Store on another Windows 10 device, remove a device from the device list."

Solution

Error Causes

There may be several reasons for this error:

1. This problem may arise if the date and time in Windows 10 are incorrect.
2. If the region has been set incorrectly.
3. Problems with Windows store cache.
4. Windows store server overloaded.
5. The Windows version you are using is pirated.

Further Information and Manual Repair

Method 1:

Correcting date and time:

• Open up Control Panel > Clock, Language, and Region.
• Then click on Date & Time.
• Now click on Change date & time to correct your time.

Method 2:

Correcting region:

• Navigate to Control Panel > Clock, Language, and Region.
• Then click on Region.
• Then click on the Location tab.
• Now set your actual region from Home location section.
• Click Apply & OK.

Method 3:

Resetting Windows Store:

• Press Windows Flag Key + X from your keyboard. Then select Command Prompt (Admin). It will launch Command prompt as administrator.
• Then type wsreset and hit Enter.
• Wait for a few seconds. It will automatically open Windows Store.
• Then try to download any apps.

Method 4:

1. Open Command prompt in local machine and type in the Windows Store reset tool exe
2. Activate Windows by going to Settings>Updates and Security
3. Run the Modern UI/metro app troubleshooter from Microsoft
4. Keep trying it several times.
5. Try changing locale and time zone to the United States as shown below
6. Go to control panel, Language settings
7. Select location to the United States
8. This will reset the language to US English. After this try downloading the apps again.
9. Try restarting the Windows Updater service or restart the machine once.

You must make sure that you have a good internet connection. You need that for the updates and downloads complete without disruption.

Method 5:

Make sure the app isn’t blocked by the Windows firewall: To make your PC more secure, some apps are blocked by Windows Firewall by default. For proper functioning, you might need to enable an app to receive info through the firewall. For more info, see the "Allow an app to receive info through the firewall," and follow the procedure from start to finish.

Method 6:

Check with your system admin: If your PC is part of a network in an organization, like a business, school, or government agency, your system administrator might have turned off the use of certain apps using the Group Policy. Contact your system admin if you believe that Group Policy is preventing you from using an app.

Method 7:

Make sure your apps are up-to-date: To make the apps working properly, you must keep your apps up-to-date. This could be done by turning on automatic updates in the Windows Store.

Method 8:

Contact the app publisher To view the publisher’s app support info, follow these steps:

1. On the Start screen, tap or click Store to open the Windows Store.
2. Search or browse for the app, and then tap or click it.
3. Scroll to the Details section of the app's description page, and then tap or click the support link for the app under Learn more. The link will open an email message for you to contact support or will take you to a support website.

If you do not possess the technical expertise required to accomplish this yourself or do not feel comfortable doing so, download and install a powerful automated tool to get the job done.

Error Code 49 – What is it?

Error Code 49 is a common device driver error that users encounter on any Windows 2000 and later operating system versions. The error occurs when the connected peripheral devices fail to function properly due to an overload of the system hive’s size. The error when prompted pops up on your screen with the following message:

"Windows cannot start new hardware devices because the system hive is too large (exceeds the Registry Size Limit). (Code 49)”

The error causes unattached devices to be displayed on the system hive list.

Solution

Error Causes

Error Code 49 mainly results from problems in Windows registry system files; the system hive in the Windows registry exceeds its size limit. The system hive is part of the Windows registry and it is where files regarding devices are contained along with user preferences and applications. The devices will not work until the system hive size is brought back to normal levels.

Further Information and Manual Repair

There are several ways you can use to fix your error code. Here are the following.

Method 1 – Uninstall unused devices

One of the best ways to address the error code is to uninstall the unused devices which are listed on your computer’s system hive. To do this:

• Log in using an Administrator account
• Click the Start button and then click ‘Run’
• In the box, enter the command:
• "set devmgr_show_nonpresent_devices=1 cd%SystemRoot%System32 exit" and click enter
• Open Device Manager, click ‘View’, and then choose ‘Show hidden devices’ to see unused devices.
• When you can see the list, click on the device you want to uninstall by selecting the ‘Driver’ tab and then select ‘Uninstall’.
• After uninstall is complete, restart your computer.

Method 2 – Use System Restore

If the error still persists, you can use system restore to eliminate the problem. Here is how you can do so:

1. Log in using an Administrator account
2. Click ‘Start’ button and select All Programs > Accessories > System Tools > System Restore
3. Click ‘Restore my computer to an earlier time’ and click ‘Next’
4. Select the last Windows restore point from the ‘On this list, click a restore point’ list, and click ‘Next’
5. Click ‘Next’ on the confirmation window to proceed
6. Restart your PC after restoration is complete

By restoring the system via a last saved system checkpoint, you can obtain undamaged Windows system files that can help avert the error code.

Method 3 – Manually uninstall and reinstall the device driver

If using system restore does not work in resolving the error code either, you may have to resort to manually uninstalling and then reinstalling the device driver causing the problem. This would be necessary since the remaining incomplete files due to a partial removal or installation of programs is what results in the error code. By uninstall and reinstalling the device driver program, it would lead to the completion of the files. You can do this by firstly logging in as Administrator and open Device Manager. Select the device that is causing the problem and double click it and make sure that the peripheral is connected properly to the PC. Upon opening, click on the ‘Driver’ tab and then select ‘Update Driver’. Make sure to refer to the system documentation that you received with your PC or computer to check for the motherboard details and driver specifics.

Method 4 – Use software to automatically download the driver

Manually uninstalling and reinstalling the driver will do the trick; however, it may be time-consuming, especially when you would have to resort to your hardware user manual. Therefore, using a program such as DriverFIX can save you a lot of time and frustration in having your device work properly on your computer. DriverFIX, with its user-friendly approach to help you fix your PC issues, comes with an integrated database that detects which drivers you need to reconfigure within just a few seconds and downloads it automatically. It further ensures that your drivers are installed in their entirety leaving no room for any incomplete files to remain that create Error Code 49. It also has the added advantage of being able to backup and restore your files should there be the slightest possibility of system file damage. DriverFIX is the answer to fixing your PC error codes accurately and quickly. Click here to download DriverFIX to fix Error Code 49 quickly and effectively!

Booting the Windows computer system includes loading it from the various boot devices such as drivers, network as well as USB drives when the computer is turned on. The instant the startup sequence is done loading the operating system the system hardware will be ready to perform some complex operations – in this process, the Boot Log in Windows 10 is a record that maintains the list of success or failure of many pieces of Windows 10 system during the booting process. In other words, the Boot Log is the one that keeps a record of all that has happened while loading from the computer storage system to the memory during the boot process. It is available for several devices like network, hardware devices, and the operating system which assist in detecting issues during the boot process and other issues with regards to troubleshooting. Through Boot Log, you’ll know which drivers were unloaded and loaded from the start of the system during the boot process. You have the option to either disable or enable this feature on your Windows 10 PC. Named as “ntbtlog.txt”, the log file lists all the successfully loaded processes and the unsuccessful ones during the boot process. It is saved to the drive C:Windowsntbtlog.txt. As mentioned, you can enable or disable this feature in two ways – the first one is by using the System Configuration or MSConfig while the second one is using the Command Prompt. In this post, we’ll show you how you can enable or disable Boot Log in Windows 10 either way.

Option 1 – Enable or Disable Boot Log using System Configuration

Enable Boot Log:

• Tap the Win + R keys to open the Run dialog box.
• Then type in “msconfig” and click OK to open System Configuration.
• After that, go to the boot tab and check the checkbox labeled “Boot Log” under the Boot options so that you can enable the Boot Log feature.
• Then click on OK to save the changes made.
• Next, click on the Restart button in the prompt window to get started with the Boot Log process.
• After restarting your PC, go to C:Windowsntbtlog.txt to open the boot log.

Note: As pointed out earlier, the log file contains a list of all the successfully loaded drivers and also the list of drivers that failed to load during the boot process and every time you restart the system, the boot log file will keep on updating and will eventually increase the list of entries. For you to locate the drivers and make your troubleshooting a lot easier, I advised disabling the boot log after troubleshooting. To disable the boot log using System Configuration, refer to the steps below. Disable Boot Log:

• Tap the Win + R keys to open the Run dialog box.
• Then type in “msconfig” and click OK to open System Configuration.
• After that, go to the boot tab and unmark or uncheck the checkbox labeled “Boot Log” under the Boot options so that you can disable the Boot Log feature.
• Then click on OK to save the changes made.

Option 2 – Enable or Disable Boot Log using Command Prompt

Enable Boot Log:

• Go to the Start Menu and then type in “command prompt” in the search bar.
• After that, right-click on the Command Prompt option and select the “Run as administrator” option.
• After opening Command Prompt, type in “bcdedit” and tap Enter.

Note: You have to find the Identifier of the current operating system first to enable the Boot log. You can find it under the Windows Boot Loader section in the “Description” field and in this case, it’s Windows 10. You can also find the operating system identifier under the Windows Boot Loader section next to the field name identifier.

• To check if the boot log entry is disabled or enabled, go check the “Bootlog” field under the Windows Boot Loader. And if it turns out that the “bootlog” entry is enabled, the entry will be “Yes”. Otherwise, the entry will be “No”.
• Next, type in the following command with the operating system identifier to enable the boot log.

bcdedit /set {identifier} bootlog Yes

Note: In the command given above, make sure that you replace the given system identifier with your computer’s system identifier. For instance: In this example, the identifier was replaced with the actual operating system identifier as current.

bcdedit /set {current} bootlog Yes

• Afterward, restart the system to start the Boot log process.
• After the restart, go to C:Windowsntbtlog.txt to open the boot log.

Note: Every time you restart your computer, the boot log file will keep on updating which will increase the size of the log eventually. So if you want seamless and easier troubleshooting, it is advised to disable the Boot log after you troubleshoot. To disable it using the Command Prompt, here’s what you have to do. Disable Boot Log:

• Go to the Start Menu and then type in “command prompt” in the search bar.
• After that, right-click on the Command Prompt option and select the “Run as administrator” option.
• Once the Command Prompt is opened, type in the following command and then tap Enter to disable the boot log feature.

bcdedit/ set {identifier} bootlog No

Note: In the command given above, you need to replace the given system identifier with your computer’s system identifier. For instance: In this example, the {identifier} was replaced with the actual operating system identifier as {current}.

bcdedit /set {current} bootlog No

• Now close the Command Prompt.

As of late, users have been reporting about getting an error saying, SAFE_OS phase error during Replicate_OC operation when they tried to upgrade their Windows 7 or Windows 8.1 computers to Windows 10. Although the error code in this problem could vary, in this situation, it states:

0xC1900101 – 0x20017, The installation failed in the SAFE_OS phase error during Replicate_OC operation

To fix this issue, you need to follow the given options below. But before you do, you need to create a System Restore point first so that if anything goes wrong, you can always undo the changes you’ve made.

Option 1 – Try to change the Windows 10 installation

According to security experts, one of the main causes of this error is the KB3064209Windows Update. This particular update is the one responsible for updating the CPU Microcode for processors made by Intel. Thus, if you don’t use an Intel processor, you can skip this option and proceed to the next one. However, if you use Intel, make sure to follow the instructions in this option carefully. Take note that in this solution, C: partition is referred to as the OS Partition while H: partition is referred to as the USB Pen Drive.

• First, you need to download the Windows 10 ISO from the Windows 10 Media Creation tool and then copy its contents to the Pen Drive H.
• Next, tap the Win + X keys and click on the Command Prompt (Admin0 option. If a User Account Control appears, simply click Yes.
• After opening Command Prompt, type the following command:

dism /Mount-Image /ImageFile:H:sourcesboot.wim /index:1 /MountDir:C:UsersUserDesktopmount

• Now navigate to the following path in the Windows File Explorer:

C:UsersUserDesktopmountWindowsSystem32mcupdate_GenuineIntel.dll

• From there, right-click on the file named “mcupdate_GenuineIntel.dll and click on Properties.
• Next, go to the Security tab and click on Advanced. In the Advanced section, change the Owner to your User Account and click OK.
• And then back to the Security tab, click on the Edit button and check on Full control to make sure that your User Account has all the privileges.
• Now click on Apply and then OK.
• After that, delete the file you saw earlier which is named mcupdate_Genuine.dll.
• Then close all the Windows File Explorer instances and go back to the Command Prompt window and unmounts the image you mounted before by typing the following command:

dism /Unmount-Image /MountDir:C:UsersUserDesktopmount /commit

• Afterward, repeat the steps from mounting up until here for these files:
  • wim /index:2
  • wim /index:1
  • wim /index:2
• Now delete the mount folder and remove the USB Pen Drive and then boot with the installer.

Option 2 – Try to perform a Disk Cleanup

Chances are, some unnecessary files in your computer might be interrupting the installation process which explains why you’re getting SAFE_OS phase error during Replicate_OC operation instead so you need to perform a Disk Cleanup in order to fix the problem.

Option 3 – Try updating all your drivers

Every now and then, drivers get corrupted or outdated so it’s no surprise that they conflict with the operating system and cause errors like the SAFE_OS phase error during the Replicate_OC operation. To fix the problem, you need to update all your drivers. Follow the steps below to update your drivers.

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

Note: You also have the option to go directly to the website of your graphics card manufacturer and check if there’s a new update – if there is, download it.

Option 4 – Try to update your system’s BIOS

Aside from outdated drivers, outdated BIOS could also be the reason why you’re getting the SAFE_OS phase error during Replicate_OC operation which is why you need to update your system’s BIOS in order to resolve the issue.

Option 5 – Try checking the Windows Services status

• In the Cortana search box, search for “Services” and then click on the Services icon.
• After that, the Services utility will be opened in a new window.
• Next, look for the following services:
  • BITS (Background Intelligent Transfer Service)
  • Windows Update Service
  • Cryptographic Service
• Then right-click on each one of the services and click on Properties. From there, select Automatic from the drop-down of the Startup Type menu.
• Now click on OK for each one of them and restart your PC to apply the changes made.

Option 6 – Try to check the RAM modules

There are many times when all the components of the RAM weren’t able to be used by the computer so you need to check the RAM modules.

• You need to first turn off your PC and then take out your RAM physically.
• Next, clean it with a soft cloth and blow some air into the RAM slot in the motherboard.
• After that, put your RAM back in the same slot.
• Then try updating your computer system again.

If you are experiencing a Low Wi-Fi signal strength on your Windows 10 PC after you’ve updated or reinstalled it, read on as this post will guide you on what you can do to fix the problem. The way devices connect these days has evolved with our cognitive revolution. Various devices use some or other wireless technology to connect with other devices. However, all wireless technology has some kind of limitation when it comes to range and signal strength. From time to time, you might have faced several Wi-Fi issues. Low Wi-Fi signal strength usually happens after you update or reinstall your Windows 10 system. This issue can be identified easily by looking at the signal bars in the Wi-Fi icon or by measuring its strength. Since this problem is wide scope, there are tons of possibilities which is why this post covers the most generic situations that could help most users. Refer to the options given below to fix the low Wi-Fi signal strength of your Windows 10 PC.

Option 1 – Try running the Network Adapter Troubleshooter

If a few days ago the range and signal of the Wi-Fi was perfectly fine before you did an update or reinstall, it is possible that there were some changes made in the configuration as well. In most cases, the latest configuration that came with the update has not aligned the config in your computer or laptop. The easiest and simplest way to fix this is by using the Network Adapter Troubleshooter. How? Follow the steps below.

• Right-click on the Wi-Fi icon from the system tray to start troubleshooting.
• After that, select Troubleshoot problems. Note that it might take a while to run it but once it’s finished, it will show you all the problems with the network adapter.

Note: The Network Adapter Troubleshooter will also fix the issues in the background but there might be some issues that will require manual action. And if the troubleshooter wasn’t able to identify and fix the problem for you, proceed to the next given option below.

Option 2 – Try using the Device Manager

If the problem is related to hardware, you need to seek out the help of the Device Manager. To do so, follow the steps below.

• Pull up the Device Manager.
• Next, look for your Wi-Fi adapter under the Network Adapters.
• Once you found it, right-click on it and open Properties.
• After that, you will see all the actions related to drivers under the driver tab.
• You can either update or roll back the selected driver or you could also disable and re-enable it to see if the problem’s fixed.

Note: If updating the driver didn’t help, you might have to dig into the advanced settings. From this post on, it can get a bit complicated as there are terms that you might not understand as well as some configuration. To make it easier for you, you can search for your Wi-Fi adapter online and try following the instructions from there. And before you make any further changes to your computer’s settings, make sure that you create a system restore point first.

Option 3 – Try changing the Wi-Fi Roaming Sensitivity

If you want to enhance the Wi-Fi reception as well as the performance on your Windows 10 PC, you might want to change the Wi-Fi Roaming Sensitivity or Aggressiveness. Roaming Sensitivity is the rate at which your computer chooses and switches to the nearest available point of access which offers a better signal. It is based on the strength and quality of the Wi-Fi and not on the distance to the Wi-Fi point.

Option 4 – Try adjusting the Wi-Fi range

The issue could also be caused by the position of your computer with respect to the Wi-Fi router instead of your hardware or drivers. It could be that your physical location might be a factor for the low signal strength of your Wi-Fi so you might want to adjust the Wi-Fi range to fix the problem.

As you know, one of the most highlighted features of Windows 10 is Windows Updates. It was offered to the customers as a service rather than a product with the release of Windows 10 under the scenario of Software as a Service which led to Windows Updates being set by default on Windows 10 and without an option for any users to disable it. Although not all users are happy with what Microsoft did, this is an ultimate step towards the greater good of all its customers since Windows Updates helps users in keeping their computers secured against all kinds of threats as well as provide them with the greatest and latest updates from Microsoft. So if you are one of those users who approved of the Windows Updates service, then read on as this post will guide you in running Windows Updates from Command Line either via Command Prompt or Windows PowerShell. For the complete set of instructions, refer to the options given below.

Option 1 – Run Windows Update via Command Prompt

Command Prompt in the Windows operating system exists for a very long time now compared to the comparatively new Windows PowerShell. That’s why it has similar capabilities to run Windows Updates. However, the highlighting point here is that you don’t have to download any module for Windows Updates. To get started running Windows Updates using Command Prompt, refer to the steps below.

• First, type “cmd” in the Cortana search box, and from the search results, right-click on Command Prompt and select the Run as Administrator option to open it with Administrator privileges.
• If a User Account or UAC prompt appears, just click on Yes to proceed.
• Next, type in the commands listed below, and don’t forget to tap Enter right after you type each one of them.
  • UsoClient StartScan – use this command to start checking for updates.
  • UsoClient StartDownload – use this command to start downloading updates.
  • UsoClient StartInstall – use this command to start installing the downloaded updates.
  • UsoClient RestartDevice – use this command to restart your computer after you install.
  • UsoClient ScanInstallWait – use this command to check, download and install updates.

Note: Keep in mind that the commands in Command Prompt listed above are only meant for Windows 10. On the other hand, if you are using an older Windows version, you can try using the following commands instead:

• wuauclt /detectnow – use this command to start checking for updates.
• wuauclt /updatenow – use this command to start installing the updates detected.
• wuauclt /detectnow /updatenow – use this command to check, download and install updates.

Option 2 – Run Windows Updates via Windows PowerShell

If you run Windows Updates in the Windows PowerShell, it will require you to install the Windows Update module manually. Hence, you have to get the Windows Updates downloaded and install Windows Updates.

• Search for PowerShell in the Cortana search box and then run it with administrator privileges.
• Once you’ve opened the Windows PowerShell, type the following command and hit Enter.
  • Install-Module PSWindowsUpdate – use this command to install the Windows Update module for Windows PowerShell.
  • Get-WindowsUpdate – use this command to connect to the servers of Windows Update and download the updates if found.
  • Install-WindowsUpdate – use this command to install the Windows Updates you’ve downloaded to your computer.

If you find that the scroll bar in your Google Chrome browser is missing all of a sudden, and it becomes difficult for you to scroll down the web page and see its content, worry not for this post will guide you on what you can do to resolve this problem. Usually, when the mouse cursor stays hidden in the corner and only appears when you point it to the edge of the screen. However, there are instances when it won’t appear which makes navigating the web page you are visiting quite impossible. So if you encounter this kind of strange behavior on your Google Chrome browser, there are several suggestions you can check out to resolve it. In most cases, updating the browser resolves the problem, but if it does not, you can try restoring the browser’s settings to their default state by resetting Chrome or you could also disable hardware acceleration or disable the overlay scrollbars flag. For more information, follow each one of the options provided below.

Option 1 – Reset Google Chrome

Before you proceed, make sure that the Chrome browser is not running anywhere in the background via Task Manager. Once you’ve made sure that it’s no longer running, refer to these steps:

• Tap the Win + R keys to open the Run dialog box.
• Then type “%USERPROFILE%AppDataLocalGoogleChromeUser Data” in the field and tap Enter to open this location.
• From there, look for the Default folder and then tap the Shift + Delete button and if a confirmation prompt appears, click on Yes.
• After deleting the Default folder, open Google Chrome and click on the three vertical dots icon located in the top-right corner to open the menu.
• Next, click on Settings and scroll down and then click on Advanced to open the Advanced Settings.
• Then scroll down until you see the “Reset and clean up” section and click the “Restore Settings to their original defaults” option.
• After that, you will see a confirmation box and from there, click on the Reset settings button to reset your Google Chrome browser.

Option 2 – Try to disable the Hardware Acceleration

For better performance, Google Chrome uses the Hardware Acceleration by default. Unfortunately, there are just some cases when your hardware, GPU to be specific, might not be able to cope with the requirements, resulting in the black screen issue. And if this is your case, you should try to disable the hardware acceleration from your Google Chrome browser settings panel. To do so, follow the steps below.

• Open the Google Chrome settings page.
• Click on the Advanced button to get more options.
• Look for the option called “Use hardware acceleration when available” and then disable it by toggling the button to the left.
• After that, check if the screen flickering issue in Chrome is fixed.

Option 3 – Try to disable “Smooth Scrolling” in Chrome

Disabling “Smooth Scrolling” in Chrome might also help you fix the issue. To do so, follow these steps:

• Open Chrome and type “chrome://flags” and hit Enter.
• Next, look for a flag named “Smooth Scrolling”. You can scroll down until you find it or search it in the Search Flag bar. Note that Smooth Scrolling is enabled by default in the newer versions of Chrome.
• After that, select the drop-down menu and select Disabled.
• Then click on the “Relaunch Now” button.

Windows 11 has some cool animations including fading effects which make working in it feels nice and futuristic but the cost of this is that there is a slight delay to certain actions performed. If you want the snap fast feature in Windows 11 and do not care about this eye candy there is an easy way to turn animations off inside it.

• First, open Windows Settings by pressing ⊞ Windows + I on your keyboard
• Alternatively, click on Start, search for Settings, and then click its icon.
• When Settings appears, look in the sidebar and select Accessibility.
• In Accessibility settings, click on Visual Effects.
• In Visual Effects, switch Animation Effects to Off.

That’s it, changes will be applied automatically, you can close settings and continue working inside Windows 11 without animations and fades. You can always switch animations back On via settings if you change your mind.

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.

What Is 0x00000050 Stop Error?

While running your Windows 7/Windows Server 2008 R2, your system suddenly stops responding out of complete randomness and you see an error message popping up which says something like this:

0x00000050 (parameter1, parameter2, parameter3, parameter4)

Solution

Error Causes

The stop error 0x00000050 signifies that there’s a PAGE_FAULT_IN_NONPAGED_AREA problem. If you’ve seen this error on different occasions then you will find the parameters in the message to be varying. That is because they are dependent on your PC’s configuration. Not all Stop errors "0x00000050” occur due to a single issue.

However, the most common problem which is encountered which results in the stop error popping up is due to a pool corruption occurring in the Srvnet.sys file.

This issue might be caused because of software incompatibility or a defective physical memory which resulted in requests for data for a hardware driver or service which was not found in the memory.

If you find the error occurring after you’ve installed a new application or a device driver then you should access Safe Mode and uninstall, disable or remove that application or driver.

Further Information and Manual Repair

In order to fix this issue, you should try booting your computer to the “Last Known-Good Configuration” as listed during startup.

For this you have to follow the below-mentioned steps:

1. Start your system.
2. When you see the message which says “For Troubleshooting And Advanced Startup Options For Windows, Press F8” hit F8 and proceed.
3. Use the up and down arrow keys to highlight “Last Known-Good Configuration” and hit enter (This method will only work if your system boot was not successfully carried out ever since you made any specific changes).
4. When you are starting the computer, press F12 and proceed with the PSA/32 Bit Diagnostics.
5. Do the following so that a clean boot can be performed:

• Go to the Start menu when the Windows 7 desktop shows up.
• On the search bar, type “msconfig” and hit search.
• Disable all the applications which are listed on the “Startup” tab.
• Now head over to the “Services” tab and mark the option which reads "Hide all Microsoft Service".
• Select the “Disable All Services” option.
• Apply the changes by clicking on “Apply” then restart your PC. You should now check the performance of your computer. If you don’t see a BSOD then you start re-enabling all the Services and Startup applications one by one until you finally figure out which one is causing the BSOD to appear.

6. Update your Windows with “Windows Updates”.