Happy New Year from ErrorTools.com!!!

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.

If you find it hard to update Google Chrome to its latest version and each time you try to do so it keeps on failing, worry not for this post will guide you in fixing a list of Google Chrome Update errors. Even though there are a lot of error codes around Chrome, these are only caused by issues with the update. Here are some of the errors you can encounter when updating Google Chrome:

• Update failed: You can encounter this error when the Updates are disabled by the administrator.
• Update failed with
  • Error 3 or 11: When Chrome’s inbuilt updater fails to find the Update server to download the latest version.
  • Error 4 or 10: This happens while checking for updates with the message “Update check failed to start”
  • Error 7 or 12: This occurs when the download fails while checking for updates.
• Windows OS version is not supported.
• Google Chrome may not be able to keep itself updated.
• Any other errors that mention that “Update failed”

Since these aforementioned error codes are related to “Update Failure”, then they have common solutions and here they are:

Option 1 – Restart your computer

You need to restart your computer first and then try updating Chrome again. There are times when it’s only a temporary issue that can be fixed by simply restarting your computer.

Option 2 – Try checking antivirus programs, firewall, and parental control settings

If you have antivirus programs, a firewall installed in your computer, as well as parental controls, then any of these could be blocking you to download anything, including the update for Chrome. This is why you have to double-check and make sure that software updates aren’t being blocked by these programs. On the other hand, you can also try running the Network Troubleshooter as it can help you resolve any DNS or connectivity issues. To use it, follow the steps below.

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

Option 3 – Try to remove Proxy

Removing the Proxy might also help you in fixing the Chrome Update errors. Here’s how you can do it:

• Tap the Win + R keys to open the Run dialog box.
• Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
• After that, go to the Connections tab and select the LAN settings.
• From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
• Now click the OK and the Apply buttons.
• Restart your PC.

Note: If you are using a third-party proxy service, you have to disable it.

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

Resetting Winsock, TCP/IP, and flushing DNS might help in resolving the Chrome Update errors just 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 5 – Try to run the Chrome Cleanup tool

You might want to run Google Chrome’s built-in Malware Scanner & Cleanup tool as it could also help in getting rid of any unwanted ads, pop-ups, and even malware, as well as unusual startup pages, toolbars, and anything else that might overtake the network and could affect the performance of the browser.

Option 6 – Get rid of any conflicting browser extensions

• Open Chrome and press Alt + F keys.
• Go to More tools and click Extensions to look for any suspicious browser extensions or toolbars.
• Click the Recycle bin and select Remove.
• Restart Chrome and press Alt + F keys again.
• Proceed to On Startup and mark Open a specific page or set of pages.
• To check if the browser hijacker is still active, click Set pages, if it is active, overwrite the URL.

Option 7 – Reset Google Chrome

Resetting Chrome can also help you get rid of the error. Resetting Chrome will restore its default settings, disabling all the extensions, add-ons, and themes. Aside from that, the content settings will be reset as well and the cookies, cache, and site data will also be deleted. To reset Chrome, here’s what you have to do:

• Open Google Chrome, then tap the Alt + F keys.
• After that, click on Settings.
• Next, scroll down until you see the Advanced option, once you see it, click on it.
• After clicking the Advanced option, go to the “Restore and clean up option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.

The dialog boxes that you see on your Windows computer exist to send you a message or to notify you. However, you can also encounter issues with them. Recently, some users reported that they’re getting empty or blank dialog boxes. It’s definitely hard to choose between Yes or No or to click OK when you don’t know the context of the dialog box. If the same thing happened to you, worry not for there are some possible solutions that can help you fix the problem. This kind of problem usually happens when there are some issues with the graphics driver or when there is some corrupted software. Whichever the case is, here are some fixes you can check out to fix the empty or blank dialog boxes on your Windows 10 computer.

Option 1 – Run the System File Checker

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files that might be the cause why you’re getting the errors 0x8024a11a and 0x8024a112. 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 2 – Try to update or rollback the Graphics driver

You can try to update your Graphics card driver using the Device Manager in your computer to resolve the blank dialog boxes problem or you can also go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it. To update your Graphics driver via Device Manager, refer to these steps:

• First, boot your computer into Safe Mode.
• After that, 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. From there, look for the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: If updating the Graphics driver didn’t fix the problem, you can also try to roll back to its previous version and see if that helps.

Option 3 – Run the DISM tool

The next thing you can do is run the DISM tool. This tool is known to repair potentially corrupted files in your system as having them could also system issues like the blank dialog boxes. To repair these corrupted system files, you can run the DISM commands:

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer and check if the problem is now fixed.

Option 4 – Try to repair or reinstall the software

If the issue with the empty dialog boxes only occurs in a specific program, you can either try to repair the program or reinstall it. You can find the Repair option in the Add/Remove program section when you select the concerned program. If repairing the program didn’t work, you might have to uninstall it and then reinstall it.

Option 5 – Try troubleshooting the problem in a Clean Boot State

You might also want to troubleshoot the problem in a Clean Boot State. Doing so will help you isolate the problem. Refer to the steps below to do so:

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

Windows 10 has displayed one of the most efficient and user-friendly interfaces. However there have been many issues on the backend of this commonly praised operating system: For example, Windows Update is still a wonky and error-laded system application. One example of this error is Windows Update Error 0x80073712 which stands in the way of users just wanting to keep their PCs updated hassle-free. The error code 0x80073712 signifies that a file needed by Windows Update to function is either damaged, missing, or corrupted. However, this does not mean that your Windows version will forever stay as-is with no mode to update it. Windows Update Error 0x80073712 is perfectly fixable with the set of provided steps below and some of Windows’ built-in troubleshooting steps:

Solution 1: Open Windows Update Troubleshooter

1. Open the Windows Update Troubleshooter by pressing the Window Key and  “S” keys simultaneously.
2. Enter the word “Troubleshoot” in the search box and select the Troubleshoot result
3. On the new window, select “Windows Update” to troubleshoot.
4. Run the troubleshooter, then open Windows Update and try to install the update again.

Solution 2: Run the DISM tool

1. Open the command prompt by pressing Windows Key and “S” key simultaneously
2. Enter “cmd” in the search box. Right Click command prompt among the results and select “Run as administrator”
3. In the Command Prompt window type the following and press the Enter key after every command

DISM.exe /Online /Cleanup-image /Scanhealth DISM.exe /Online /Cleanup-image /Restorehealth

4. To close the Administrator: Command prompt window, type Exit, and then press Enter.
5. Run Windows Update again.

Solution 3: Rename the Software Distribution folder

1. Open the command prompt as previously mentioned
2. Input the following command pressing Enter after every line net stop wuauserv net stop cryptSvc net stop bits net stop msiserver rename c:windowsSoftwareDistribution softwaredistribution.old net start wuauserv net start cryptSvc net start bits net start msiserver exit
3. Restart the PC and run the updater if it works again.

Solution 4: Restart Windows Update Services

1. Press the Windows logo key and R together to open Run -> Input services.msc -> and press Enter
2. Search for the Windows Update service -> Check its status
3. If it is not indicated, right-click on the service and select Start to force start your Windows Update
4. If you see an error, locate the Startup Type option and set it to Automatic
5. Now you should reboot your computer and see if your Windows Update is OK

Solution 5: Fix Registry Issues

If after all the aforementioned solutions, you still experience problems with Windows Update, the problem may lie in the registry that is either damaged or corrupted. You may choose to do manual editing of your Windows registry by opening your Windows registry editor. But doing so is risky as one wrong letter may do incalculable damage to your system. To do so safely for more inexperienced users., we recommend using a third-party registry cleaner/tools, many of which can be found online.

As you know, the Windows 10 Action Center has a stack of all the notifications that come from different applications on your computer. So each time an app displays notifications, it will be displayed for about 5 seconds and then it disappears right away. Although the allotted time for the notifications to be displayed is quite enough to catch your attention and help you get a glance at the message, there are times when you might miss it and you hoped it could’ve been displayed a lot longer. So in this post, you will be guided on how you can increase or decrease the display time of the notification in Windows 10. The best way you can view the missed notification is to click on the Action Center. From there, you will see all the notifications that are grouped by the applications. This means that if you have a lot of notifications, it would be hard for you to find what you are looking for. Thus, in such cases, the best way you can do is to increase the display time for which notification to stay on the screen.

To get started, refer to the instructions given below.

Step 1: Tap the Win + I keys to open Settings. Step 2: Next, navigate to Home > Ease of Access > Display. Step 3: After that, scroll down to the end until you see the dropdown to change the notifications where you should see the “Show notifications for”. Step 4: Then you can change the time from the default 5 seconds to 7, 15, 30, and so on. Step 5: Once done, the display time of the notifications should stay longer but keep in mind that you must choose the length wisely so if you have notifications from a lot of apps, then the screen will also be filled with multiple notification cards.

To function properly and as intended, Windows 10 depends on a number of resources and software components. Even with a simple task as powering the machine, there are already several smaller software components supporting it. However, if any of these resources or components experience issues, it will affect the overall function of the computer. One of the errors reported is the Kernel Power Blue Screen error which is triggered by the Windows Kernel that mostly comes with a Windows Kernel Event ID 41 error. This kind of error can turn off and reboot the computer randomly. Here’s an example of a Bugcheck code entry with the same event:

 “EventData BugcheckCode 159 BugcheckParameter1 0x3 BugcheckParameter2 0xfffffa80029c5060 BugcheckParameter3 0xfffff8000403d518 BugcheckParameter4 0xfffffa800208c010 SleepInProgress false PowerButtonTimestamp 0Converts to 0x9f (0x3, 0xfffffa80029c5060, 0xfffff8000403d518, 0xfffffa800208c010)”

This kind of BSOD error is caused by an issue with the Power Supply components in both the software and hardware parts of your computer. In such cases, if your computer is stuck in a reboot loop, you need to troubleshoot the problem via Safe Mode or in the Advanced Startup options screen.

Option 1 – Try disabling Overclocking

If you have enabled Overclocking, you might have to disable it as some users reported that the Kernel-Power Blue Screen error started to appear right after overclocking. To disable it, follow the steps below.

• Go to the Start Menu and open Settings.
• Next, select Update and Security and go to the Recover tab.
• From there, click on Restart now in Advanced startup. This will restart your computer.
• Once you’re in the Advanced startup, go to Troubleshoot and then select Advanced Options.
• From there, select the UEFU Firmware Settings.
• Now click on Restart. Once your computer has restarted, it will automatically open BIOS.
• From the BIOS, go to the Advanced tab and navigate to Performance and then look for Overclocking.
• Once you’ve found Overclocking, make sure that it is disabled. If it’s not, then disable it and then save the changes made by tapping the F10 key.
• Start your computer normally and check if the Kernel-Power Blue Screen error is now fixed.

Option 2 – Try to run the Power troubleshooter

The next thing you can do is to run the Power troubleshooter. To do so, follow these steps:

• Go to Settings and navigate to Update & Security > Troubleshoot.
• After that, look for the “Power” option from the given list of built-in troubleshooters and click on it.
• Next, click on the “Run the troubleshooter” button to run the Power troubleshooter.
• Once the troubleshooter is done identifying the problems, follow the next on-screen instructions to resolve the problem.

Note: You could also try to run the Blue Screen troubleshooter to fix the Kernel-Power BSOD error. You can find it under the same page as the Power troubleshooter.

Option 3 – Try to replace the Power Supply Unit

You could also try to consider physically replacing the Power Supply Unit or PSU of your computer and see if that helps or not.

Option 4 – Run the Windows Memory Diagnostic tool

Since this error could be caused by some issues in the memory, you can try running the Windows Memory Diagnostic tool and see if it helps.

• Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Note: After you select the option, your PC will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 5 – Try to check physically check your RAM

In this option, you have to check your RAM physically especially if you tend to use multiple physical RAMs on your computer so it can be quite tricky and technical. You have to check first if they are of the same frequency and then verify if the chip is compatible or not. You also have to check if the sockets are attached using some adapter or non-recommended apparatus as it can cause some problems while giving performance hit to your computer.

Option 6 – Try to update the BIOS

Updating the BIOS can help you fix the Kernel-Power BSOD error but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “msinfo32” in the field and press Enter to open System Information.
• From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
• After that, you should see the developer and version of the BIOS installed on your PC.
• Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
• If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
• Now double click on the downloaded file and install the new BIOS version on your computer.
• Now restart your computer to apply the changes made.

Note: If updating the BIOS didn’t help, you might want to consider resetting it instead.

Option 7 – Disable Fast Start-up

If you want your computer to boot faster, then you might have enabled Fast Start-up. This feature is ideal for computers that are using a hard disk drive. However, turning on this feature also means that when the computer boots, it might lag some drivers that are loaded when it initially boots up. Thus, it might be the potential cause of the Kernel-Power BSOD error. Thus, you need to disable Fast Start-up. To do that, follow these steps:

• Boot your PC into Safe Mode.
• Then tap the Win + R keys to open the Run dialog box.
• Next, type in “control” to open Control Panel.
• After that, select Hardware and Sound and click on Power Options.
• Select “Choose what the power buttons do” from the left side menu pane and click on Change settings that are currently unavailable.
• Afterward, uncheck the “Turn on fast startup (Recommended)” entry and click on Save Changes.
• Now restart your PC for the changes to take effect and then check if the problem’s fixed afterward.

As you know, Windows 10 comes with the option to create Mobile Hotspot for other devices. This allows you to share your Ethernet connection. However, there are times when one of your devices might fail to reconnect to the mobile hotspot again. For instance, you moved out of the Wi-Fi range because you have somewhere to be and whatnot and when you’re back you find that you are now unable to reconnect to the Windows 10 Hotspot or the shared network. Although you can always restart the mobile hotspot to resolve the problem, however, it might only be a temporary fix. So in this post, you will be given options for a much better solution to the problem. This kind of problem seems unusual and does not occur that often. To fix it, you can try to set up DNS on your Windows 10 device and then configure the settings on the mobile device. It seems that what’s happening here is that the mobile device is unable to lock on to the Mobile Hotspot when the IP address changes for some reason.

Option 1 – Try changing the DNS settings on your laptop

In this option, you need to make sure that IPv4 and IPv6 are selected on your Ethernet connection. You also have to change the Preferred DNS server as well as the Alternate DNS server to 8.8.8.8 and 8.8.4.4, respectively. You also have to validate the settings before you exit just to ensure that you’ve entered everything correctly. After that, open Command Prompt and run the ipconfig command and then take note of the IP address, Gateway DNS 1 and DNS 2.

Option 2 – Try changing the Wi-Fi settings on your mobile device

This option should be mostly the same on all your mobile devices. And given that OEMs build their customization and skin, you might have to fiddle around a little to get the settings. Refer to the steps below to change the Wi-Fi settings:

• Go to the Settings of your mobile device and tap on Wi-Fi.
• Then click the Mobile Hotspot connection that you’ve created on your laptop.
• After that, input the password and tap the Advanced options.
• From there, tap on IP settings and select the Static option instead of DHCP.
• Now you have to enter the IP address, Gateway, DNS 1, and DNS 2 of the laptop you’ve taken note of earlier and that’s it.

Note: If you are already connected to the Mobile Hotspot, long press on the Wi-Fi network and select the Modify Network option and then follow the steps given above to change from DHCP to static. Once you’re done, your mobile device should now be able to connect to the Windows 10 Mobile Hotspot all the time.

If you suddenly encountered the PDC WATCHDOG TIMEOUT BSOD Blue Screen stop error with a bug check value of 0x0000014F, then it’s probably due to a system component that has failed to respond with the allocated period which prevents the system from exiting connected standby. This kind of Blue Screen error could be caused by both hardware and software components. To fix this Stop error, here are some possible fixes you can try that might help but before you proceed, make sure that you create a System Restore point first and boot your computer into Safe Mode with Networking.

Option 1 – Try to rollback, update or disable drivers

The next thing you can do to fix the PDC_WATCHDOG_TIMEOUT Stop error is to roll back, or update, or disable device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• After opening the Device Manager, look for the device driver named “IDE ATA/ATAPI controllers” and expand it.
• Then look for the SATA AHCI Controller entry and right-click on it. If you haven’t updated this driver in a while, select the “Update Driver” option. On the other hand, if you’ve just updated this driver, then select the Uninstall Device option.
• Next, follow the screen option to update or uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically if you have chosen to uninstall them.

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

Option 2 – Try to disconnect or disable newly installed hardware

In this option, you will have to disable or remove the hardware you’ve just installed recently since external devices could be the one that’s causing the Blue Screen of Death error to appear. To do that, just disconnect any external device that’s connected to your computer physically and then check if it fixes the PDC_WATCHDOG_TIMEOUT Blue Screen error.

Option 3 – Try running the Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the PDC_WATCHDOG_TIMEOUT Blue Screen error by checking and automatically fixing any memory-based issues. To run it, refer to these steps:

• Tap the Win + R keys to open Run and type mdsched.exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Option 4 – Try to update the BIOS

Updating the BIOS can help you fix the PDC_WATCHDOG_TIMEOUT BSOD error but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “msinfo32” in the field and press Enter to open System Information.
• From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
• After that, you should see the developer and version of the BIOS installed on your PC.
• Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
• If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
• Now double click on the downloaded file and install the new BIOS version on your computer.
• Now restart your computer to apply the changes made.

Option 5 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like PDC_WATCHDOG_TIMEOUT. It can be found in the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

What is TrayApp Error 1706? A TrayApp Error 1706 is not something you want to see. It is generally caused by an error in hexadecimal formatting, which is a common format employed by software programmers for Windows OS-compatible hardware drivers, Windows system files, and software apps. Developers and manufacturers of hardware drivers and software apps employ different codes in order to indicate different types of errors. The TrayApp error 1706 occurs in a long numeric code with a technical explanation of the cause. In many cases, the TrayApp error 1706 can have different TrayApp error 1706 parameters. It will usually sport a message like:

• Install Error 1706 Trayapp
• Reinstall Error 1706 Trayapp
• Error 1706 Trayapp crash
• Error 1706 Trayapp is missing
• Remove Error 1706 Trayapp
• Download Error 1706 Trayapp
• Error 1706 Trayapp virus

Solution

Error Causes

More often than not, the TrayApp error will occur because there are damaged files in your operating system. When the Windows system file entry gets corrupt, it means that there malfunctioning in your system and it can be exposed to major security threats. And if it’s not resolved, it can potentially result in complete and permanent data loss and can make your storage media or your system as a whole inoperable. There can be other triggers for the TrayApp error, the common of which include:

• Incomplete installation of software
• Incomplete un-installation of software
• Improper deleting of hardware drivers
• Improper deleting of software applications

If you have the TrayApp error, you realize how common it is when restarting your system followed an improper shutdown or a recent malware or virus recovery. These situations result in corruption or deletion of essential system files. When Windows system files get corrupted or go missing, the data that is needed to run software won’t be linked properly.

Further Information and Manual Repair

There are two common manual ways of fixing TrayApp error 1706. The manual solution is:

Boot Your System and Log in As Administrator.

• Click on Start and select All Programs.
• Go to Accessories, then System Tools, and select System Restore.
• In the dialog box, select, ‘Restore computer to an earlier date’ and then click on Next.

Click next twice on the dialog boxes and then the Automatic System Restore will start and restart your device.

Reimage Plus Fix for Trayapp Error 1706

This is the easiest way to resolve TrayApp Error 1706. However, there are cases when the manual process may not really work, and this can be caused by improper maintenance of your system. For that, Restoro is your short and comprehensive answer. Restoro is a multi-functional PC Fixer that works as an antivirus, registry cleaner, system optimizer, and much more. It can not only help resolve TrayApp Error 1706, but can also resolve other errors that can hinder the performance of your system, programs, and applications. It can also clean your registry and optimize your system to make it faster and quick loading. The software is compatible with all Windows versions. Just click here and download Restoro and get rid of any issues in your system!

If you suddenly find your Windows 10 computer stuck on the “Preparing to configure” screen for quite a long time now after you run Windows Update, read on as you will be guided on how you can fix that issue in this post. During an update process, there’s a lot of things that go on in the background which is why Windows Updates take quite a while before it finishes. It can be at 25%, 50%, or even 100% but the only message you’re going to see on your screen is the “Preparing to configure Windows, Don’t turn off your computer”. However, if you notice that the Windows Update is taking a longer time than it’s supposed to, the first option is to wait some more but if it’s still the same, then there’s definitely something wrong. This kind of issue occurs when Windows Update fails to configure in short correctly download and install the update. When this happens, it will revert all the changes which are why you were advised to wait for a couple of hours. There are two possibilities why your computer is stuck on the “Preparing to configure Windows, Don’t turn off your computer” screen. The first one is that the Windows 10 operating system is installing any updates. The second one is when the user profile takes time to load or encounters an error. There are several options you can try to fix the problem. You can try running System Restore or boot your computer in Safe Mode or repair the corrupted profile via Registry Editor. You might also want to try using installation media to boot and repair your computer if the other options didn’t work.

Option 1 – Perform System Restore

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

Note: If you can’t boot into the desktop of your computer, you can run System Restore in the Advanced Startup Options by following these steps:

• Boot your computer into the Advanced Startup Options screen.
• From there, you will see some options to troubleshoot when you can’t log in to Windows in the usual way.
• Now select Troubleshoot > Advanced Options > Command Prompt.
• After that, type “rstrui” and hit Enter to execute the command which will start the System Restore process.
• Once it’s done, restart your computer.

Option 2 – Boot your computer in Safe Mode

You can try to tap the F8 key if you have it enabled in your Windows 10 computer, as you start your system to boot into Safe Mode. Once your computer is in Safe Mode, you can access the Start Menu and the Mouse and Keyboard. Aside from that, you can also access your files and other built-in tools in Windows such as Command Prompt, PowerShell, Computer Manager, Device Manager, Event Log Viewer, and many more. On the other hand, if you haven’t enabled the F8 key, you can just go to the Advanced Startup options to boot your computer into Safe Mode. Once you’re there, select Troubleshoot > Advanced Options > Startup Settings > Restart > Tap the number 4 key. After that, your computer will restart in Safe Mode. If you want to reboot into Safe Mode with Networking instead, you can tap the number 5 key and for Safe Mode with Command Prompt, tap the number 6 key. Once your computer is in Safe Mode, you can use any of the built-in tools to restore your computer or troubleshoot the problem that’s causing your computer to get stuck at the “Preparing to configure” screen.

Option 3 – Try to repair your corrupted profile via Registry

In this third option, you can try to repair the corrupted profile using the Registry but before you proceed, take note that you can only try this if you can boot into your desktop and if you can, make sure to create a System Restore Point and then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and hit Enter or click OK to open the Registry Editor.
• Next, go to this registry key: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileList
• Once you’ve opened the registry key, you should see a list of all the user profiles on your computer. Now click on each S-1-5 folder and look for the “ProfileImagePath” entry and double click on it to check which user account it is related to. You will see a path like “CUsersACK” where “ACK” is the username.
• You should know which of the user account is corrupted. Just look for a key named “RefCount” and change its Value data to “0” and click OK. And if it isn’t available, simply right-click on the right pane and create it.
• After that, double click on the key named “State” and make sure that the Value data is “0” and click OK.
• Exit the Registry Editor and restart your computer to apply the changes made.

Option 4 – Try to use installation media to boot and repair your computer

Another thing you can try to resolve the issue is to use the Windows installation bootable media so you can boot and repair the operating system. To use it, follow these steps:

• You need to first create an installation media which has the dame version of the operating system installed in your computer.
• After that, once you reach the Install Windows screen, click on the “Repair your computer” link.
• Wait until the repair is completed and then shut down your computer
• Now once your computer has restarted, check if it can now boot properly.