Windows 11 Insider Preview Build 22000.71

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

windows insider 2000Changes 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.

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

A Quick Guide to Fixing Error 2046

Error 2046 - What is it?

Error 2046 is an error code related to Adobe Flash Player. It usually occurs while watching movies or videos on the web browser. This error code may interrupt video display and hamper you from watching your favorite movies and videos.

Solution

Restoro box imageError Causes

Narrowing down the reason for the occurrence of this error code is quite difficult virtually because it may trigger due to several reasons such as:
  • There might be issues with Adobe Flash Player settings
  • Ad-blocking products
  • Windows not updated
  • Registry issues
  • Malware infection
  • Flash Player Add on not properly installed

Further Information and Manual Repair

The good news is that the error 2046 is not fatal. It is easy to fix. In fact, it is so easy to repair that you can do it all by yourself even if you are not a computer whiz. You don’t have to hire a professional and spend hundreds of dollars on repairs. Here are some of the many manual solutions that you can try to fix this issue on your computer screen:

Reinstall Adobe Flash Player

Since this error code is largely related to Adobe Flash Player, it is advisable to start by reinstalling the Flash Player. Here is a step-by-step guide to help you work through it.
  1. First, click start and then select the control panel.
  2. Now click on programs and then uninstall Flash Player from the program list.
  3. After that’s done, reboot your computer.
  4. Now download Adobe Flash Player from a reliable website and run it.
If it works perfectly, then the issue is resolved. If not, then try other methods given below.

Re-Enable Flash Player Add-on

Adobe Flash Player add-on is basically installed in IE (Internet Explorer) which is loaded each time you load IE. Sometimes the problem with this add-on can also generate error 2046.
  1. To resolve this, open Internet Explorer and press Alt-Key.
  2. Select tools and then manage add-ons.
  3. Now select Adobe Flash Player Active X and then click disable tab.
Once that’s done, restart the web browser and repeat the same steps but this time click enable button. This will hopefully resolve the issue.

Unblock Ad Blocking Products

Sometimes error 2046 may pop up on your screen if you use ad-blocking products like AdBlock Plus. If so, then try uninstalling ad-blocking products installed on your PC to fix the issue.

Install Window Update

Microsoft releases new updates every now and then. These updates are made with the objective of solving bugs and run-time errors like error 2046. Therefore if the error code is related to Windows updates then to resolve it is it advisable to launch the Windows update program and update your operating system. For this, click Start, All Programs, and then click Windows Update. Now click the Check for updates button and download and install the new updates. Once that is complete, restart your PC to bring changes into effect.

Scan for Malware and Look For Registry issues

Whether the issue is related to malware or the registry, it is recommended to download Restoro. This is a next-generation and a multi-functional PC Fixer embedded with a powerful antivirus and a registry cleaner. Run it on your PC and scan for viruses and registry issues and click repair to resolve. It is user-friendly and compatible with all Windows versions. Click here to download Restoro to resolve error 2046.
Read More
New Chrome update brings surveillance debate
Google Chrome 94 is here and it has introduced a controversial idle detection API. For those people that do not know what idle detection API is, well basically Chrome can be asked by a website to report when a user of the site has a site open and is idle on the device. The issue that people have with this is that this particular feature can be used to report when the user is not using a computer at all. chrome idle detection featureGood thing is that website or web application will prompt you to allow it to use this feature like when a site/application wants to use your microphone or web camera. Developers are on board with this feature since it can provide them with more telemetric data on how users are interacting with their website/application but there are some that are strongly voicing against this. Tantek Çelik, Mozilla Standards Lead, commented on GitHub, saying:
As it is currently specified, I consider the Idle Detection API too tempting of an opportunity for surveillance capitalism motivated websites to invade an aspect of the user’s physical privacy, keep long-term records of physical user behaviors, discerning daily rhythms (e.g. lunchtime), and using that for proactive psychological manipulation (e.g. hunger, emotion, choice)… Thus I propose labeling this API harmful and encourage further incubation, perhaps reconsidering simpler, less-invasive alternative approaches to solve the motivating use-cases.
Others who have spoken against this feature are people from the WebKit development team inside Apple. Ryosuke Niwa, an Apple software engineer who works on WebKit said:
That doesn’t seem like a strong enough use case for this API. For starters, there is no guarantee that the user won’t immediately come back to the device. Also, who is such a service supposed to know what another device user might be using at any given point? We’re definitely not going to let a website know all the devices a given user might be using at any given point. That’s a very serious breach of the said user’s privacy. It seems to me that such a suppression/distribution mechanism is best left for the underlying operating systems/web browsers to handle.
Of course, technology itself as always can be used for good or for bad and time will tell if this feature has brought good stuff or it has paved another brick in surveillance and privacy manipulation. As said for now option will prompt for agreement and let's hope that it will be used for good causes from this day into the future.
Read More
Fixing Upside Down Screen in Windows 10
As you know, Windows 10 comes with a pre-packed feature that allows you to rotate the screen at different angles, and to facilitate this feature, there are keyboard shortcuts you can use as well. However, from time to time, no matter how useful this feature is, users still experience a handful of issues. One of which is that they suddenly find their screen rotated or Upside Down even when they didn’t do a thing or adjust the setting. You may have pressed the shortcut on the keyboard by accident or some other program changed the setting on your computer without your permission – whichever the case is, this post will show you what you can do to fix the upside-down screen on your Windows 10 PC using the options laid out below.

Option 1 – Try using hotkeys

As mentioned earlier, Windows have hotkeys in the UI that changes the orientation of the display. So the first thing you need to do is to make sure that these hotkeys are enabled and if they are, you can use the keyboard shortcut to adjust the orientation of your screen.
  • Right-click on an empty part of your Desktop and then select the Graphic options.
  • Next, select “Hot Keys” > “Enable”. After verifying that the hotkeys are enabled, you can tap the Ctrl + Alt + Up arrow keys to change your computer screen’s orientation.
  • Alternatively, you can also tap the Ctrl + Alt + Right or Left or Down arrow keys to change the direction the other way.

Option 2 – Try using the Graphics Properties

You will probably see the “Graphics Properties” option if you use the Intel HD Graphics every time you click on your Desktop. Note that this option has all the graphics driver properties and helps you in changing the configurations as well as control several options like refresh rate, resolution, color-depth and many more. You have to navigate to these options to see if the orientation is changed in these properties. To do so, follow the steps below.
  • Right-click on any empty space on your Desktop and then select Graphics Properties or Intel Graphics Settings.
  • After that, select Display from the list of sub-options that appears.
  • From there, you will see the rotation of the screen under the “Display settings” option where you have to make sure that the slider is set to “0”.
  • Click the Apply button to save the changes made and then click on Exit. The orientation of your screen should automatically change.

Option 3 – Try using the Windows Display Settings

Since the Windows Settings have a section where you can manage the display settings of your computer, you can use them to help control the resolution of your PC’s display without any trouble. There is a possibility that the settings are changed there so that’s probably why your screen is turned upside down all of a sudden.
  • Tap the Win + S keys to open search and then type in “settings” in the field and then hit Enter to open Settings.
  • After opening Settings, click on System and then on Display using the left navigation bar and then scroll to the end and select the Advanced display settings.
  • Next, click on the Display adapter properties and click on Intel HD Graphics control panel.
  • Now change the rotation to 0 Degrees. Afterward, the display should revert back to its original form automatically.

Option 4 – Check your monitor’s physical controls

There are monitors that have buttons in them that allows users to shift the rotation of the screen to 90 degrees. It could be that your monitor has these buttons without you knowing and you suddenly pressed them by mistake which caused your screen to rotate. Thus, you have to check your monitor for any physical buttons on the side and if you see a menu, navigate to its options and check if there are screen rotation options. To make it easier for you, you can simply search your monitor’s model online and see if these buttons exist. You could also go over your monitor’s manual if you still have it as it contains details with regards to screen rotation.

Option 5 – Update your Graphics drivers

  • Tap the Win + R keys to open the Run dialog box and then type in devmgmt.msc and tap Enter or click OK to open the Device Manager.
  • Expand the section for the outdated device drivers.
  • And then select the outdated driver(s) and right-click on it/them.
  • From the drop-down menu, select the Update Driver option if you wish to update the driver or select the Uninstall device if you want to uninstall the driver and then follow the on-screen instructions to install the latest version of the driver.
  • Restart your PC after the installation to allow the system to reinstall the driver.
Read More
Enable or Disable Windows 10 Boot Log
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.
Read More
Change Legacy to UEFI without reinstalling
There are some new generation motherboards for laptops and PCs that bring in support for both the Unified Extensible Firmware Interface or UEFI as well as the Basic Input Output System or BIOS. The main advantage of UEFI over the traditional BIOS is the fact that UEFI supports a hard drive that has a capacity of more than 2 terabytes. However, the disadvantage of UEFI is that it only supports the x64 Windows operating system versions and that the hard drive is supposed to use the GPT structure. So if your PC is compatible with and supports UEFI and you want to change from Legacy to UEFI, then you’ve come to the right place as this post will guide you on how you can exactly do that without having to reinstall it. There are two ways to change Legacy to UEFI. You can convert MBR to GPT using either the built-in utilities in Windows or using the Recovery Environment. Before you proceed, make sure that your computer fulfills the following prerequisites:
  • Your PC’s motherboard should support both Legacy and UEFI.
  • Your PC should be running at least the 1703 Windows 10 version or newer on an MBR partition.
Once you’ve made sure that your computer covers the aforementioned prerequisites, refer to the given options below.

Option 1 – Convert MBR to GPT via Windows built-in utilities

  • In the Windows Search box, type “command prompt” and from the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
  • After that, execute this command: exe /convert /allowfullOS
  • Now, wait until the process is completed since you can track its process on your screen.
  • Once it’s done, go to Settings > Update & Security > Advanced Startup options and from there, click on Restart Now. This will restart your computer and give you advanced options.
  • Next, select Troubleshoot > Advanced Options where you will see further options including System Restore, Startup Repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
  • Now select the UEFI Firmware Settings. This will take you to the BIOS. Boot Mode is typically available under Boot > Boot Configuration. Once you’re there, set it to UEFI and then save the changes you’ve made. After that, your computer will restart.

Option 2 – Convert MBR to GPT via the Recovery Environment

  • When the message appears on your screen while running Windows Setup, you need to tap the Shift + F10 keys to open Command Prompt.
  • Make sure to run Command Prompt as admin and then execute this command: exe /convert
  • After that, wait until the process is completed. When it’s done, you have to go to the BIOS just like in the first given option above.
  • As mentioned, you can usually find the Boot Mode under Boot > Boot Configuration. Once you’re there, set it to UEFI.
  • Now save the changes made and exit as your computer will restart.
Read More
Fixing To use System Restore you must ...
There are cases when you want to undo some changes you’ve made to your computer and to do that you have to perform the System Restore task. However, if you encounter an error that states “To use System Restore you must specify which Windows installation to restore”, when doing so, read on as this post will help you fix the problem. This kind of error in System Restore could be due to corrupted files in the system. There are also situations where you are not able to boot up once you encounter this error which could be a big problem. On the other hand, this error might have something to do with corrupted BCD files. Whatever the cause is, here are some potential fixes you have to try.

Option 1 – Try to run System File Checker offline

Like pointed out, since the error might be due to corrupted system files, you can try to run System File Checker offline. How? Refer to these steps:
  • You need to go to the Advanced Startup Options and from there select Troubleshoot.
  • Next, select the Advanced Options and then Command Prompt.
  • After opening Command Prompt, type the commands given below and tap Enter right after you type each one of them.
    • Cd /
    • Dir
  • If you can see the “Users” folder, that is your system’s drive. However, if you can’t see it, you can just change the drive-by assigning “D” as its alphabet volume.
  • Then execute this command where “C” is the system drive: sfc /scannow /offbootdir=C: /offwindir=C:Windows
  • Now repeat the given steps sequentially.

Option 2 – Try to run DISM tool

You can also run the DISM tool to repair the potentially corrupted system image. First, you have to check the health of the system like checking the integrity of the system files and Windows services. To run DISM, follow the given steps below sequentially.
  • Open Command Prompt from the Advanced Startup options.
  • After that, execute this command where “C:” is the system volume: DISM /Image:C:Windows /Cleanup-Image /RestoreHealth /Source:C:WindowsWinSxS
  • If you encounter an error after executing the given command, insert the Windows USB or DVD and then execute this next command where “E:” is the USB or DVD drive: DISM /Image:C:Windows /Cleanup-Image /RestoreHealth /Source:esd:E:SourcesInstall.esd:1 /limitaccess
  • In some cases, “install.esd” would be “install.wim” and in such case, you have to modify and execute this command: DISM /Image:C:Windows /Cleanup-Image /RestoreHealth /Source:wim:E:SourcesInstall.wim /limitaccess

Option 3 – Try to repair corrupted BCD

As mentioned, the error could also be due to corruption in BCD, and to fix it, you can use Bootrec.exe – a built-in command-line tool used to troubleshot issues related to boot up and Windows Startup. Before you run this tool, make sure that you have inserted a bootable USB or DVD into your computer. Once you have that covered, follow these steps:
  • You need to go to the Advanced Startup Options.
  • Then click on Troubleshoot.
  • Next, select the Advanced Options and then Command Prompt.
  • Once Command Prompt has been pulled up, enter each one of the following commands and in the sequence that they are given to rebuild BCD files and repair MBR files:
    • Bootrec /Fixmbr
    • Bootrec /FixBoot
  • After you execute the commands given above, you should see a confirmation message that says, “The operation completed successfully”.
  • Now type the “Bootrec /RebuildBCD” command to rebuild BCD.
  • Finally, close Command Prompt and then restart your computer to successfully apply the changes made.

Option 4 – Try to run the Automatic Repair Utility

You might also want to use Automatic Repair in fixing the error. To do so, follow the steps below.
  • You can start by creating and booting from a bootable Windows 10 USB Stick.
  • After that, click on Repair your computer located in the bottom left corner when you are on the initial Windows Startup screen.
  • Next, click on Troubleshoot, and then on the other screen, click the Startup Repair option.
  • Now select the operating system you want to repair. Once you do that, it will start to repair your operating system. Wait until the process is completed and then check if the problem’s now fixed.

Option 5 – Try to use the Windows Recovery Environment

If the four options given above didn’t help fix the problem, you could try running Windows Repair and a Windows bootable USB or DVD.
  • First, insert the bootable USB or DVD and boot into it, and select the “Repair your computer” option.
  • Next, once you see the manufacturer logo on your computer, tap the key to enter into Windows Recovery Environment.
  • After that, change the Boot sequence to DVD drive under the UEFI Firmware settings and restart your computer.
  • Once your computer has restarted, select the boot order and make changes accordingly as displayed in the BIOS.

Option 6 – Try running System Restore in Advanced Startup Options

Since you probably can’t boot into your Windows 10 computer, you can try to run System Restore again in the Advanced Startup Options.
  • 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 “exe /OFFLINE:C:Windows” and hit Enter to execute the command which will start the System Restore process.
Note: You need to replace “C” with the drive where Windows Installation is located.
Read More
Fixing Tcpip.sys Blue Screen Error in Windows
One of the most common Blue Screen of Death errors you can encounter on your Windows 10 computer is the Tcpip.sys Blue Screen error. The Tcpip.sys file is a driver file that is associated with the Transmission Control Protocol over Internet Protocol. When you see this kind of BSOD error, you may see any of the following error descriptions:
  • IRQL_NOT_LESS_EQUAL
  • KMODE_EXCEPTION_NOT_HANDLED
  • PAGE_FAULT_IN_NONPAGED_AREA
Whichever error description you got, you need to do use the following instructions below as a reference to obliterate the Tcpip.sys Blue Screen error.

Option 1 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like Tcpip.sys Blue Screen error. It can be found on 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.

Option 2 – Try resetting TCP/IP

In case you didn’t notice, the Tcpip.sys file is associated with the TCP/IP protocols in your computer system which is why resetting TCP/IP can help in resolving the Tcpip.sys Blue Screen of Death error especially when the TCP/IP has been modified.
  • First, you need to type “command prompt” in the Windows Search bar and then right-click on the related search result and select the “Run as administrator” option to open Command Prompt.
  • After that, type the following command in the elevated cmd window and hit Enter:
netsh int ip reset
  • Now reboot your computer after the command has been executed and check if it helped to fix the Blue Screen error.

Option 3 – Try to rollback your Network driver

If you have updated the driver software as of late and you suddenly got this BSOD error, you might have to roll back the device driver – in other words, switch back to the previous working version. To do that, follow these steps:
  • Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
  • Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
  • Next, select the driver entries that are labeled appropriately other than anything in the context of the WAN Miniport.
  • Then select each one of them and double click to open a new mini window.
  • After that, make sure that you’re on the Driver tab and if you are not, just navigate to it then click the Roll Back Driver button to switch back to the previous version of your Network adapters.
  • Now restart your computer to successfully apply the changes made.

Option 4 – Try to update the Network drivers

You might also want to try updating all your network drivers in order to fix the Tcpip.sys Blue Screen error. To do so, here’s what you have to do:
  • Tap the Win + R keys to launch the Run window and then type in the “MSC” command and hit Enter to open the Device Manager window.
  • Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
  • Then right-click on each one of the Network drivers and update them all.
  • Restart your PC and see if it helped in fixing the BSOD error.
Note: If updating the network drivers didn’t help in fixing the problem, you can also try to uninstall the very same drivers and restart your Windows 10 PC. After that, the system itself will reinstall the drivers you just uninstalled. Alternatively, you can also download and install the drivers from the manufacturer’s website directly.

Option 5 – Try to disable both the Antivirus program and Firewall temporarily

There are times when antivirus programs and the firewall blocks a website that they consider to be malicious or even because of false-positive effects which is why you have to disable these programs temporarily as it might be the reason why you’ve encountered the error when trying to browse the internet.
Read More
Windows Update service could not be stopped
If you are running the Windows Update service but decided to stop it but you encountered an error message instead that says, “The Windows Update service could not be stopped”, read on as this post will help you fix the problem. This kind of error appears when you use the Command Prompt to stop the Windows Update service, especially if you are using cmd without admin privileges. A lot of users reported that they were not able to disable the automatic Windows Update in Windows 10 using Command Prompt. The command used to stop the Windows Update service is the “net stop wuauserv” command. However, when some users executed this command, they got the error message. So if you are one of these users that can’t stop the Windows Update Service via Command Prompt, you can try to fix that using PID as well as checking the Service dependencies. For more details, follow the given options below.

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

In case you don’t know, each running service or process has its own unique ID or PID and you can find it in the Task Manager. You can use it to stop the Windows Update service. How? Refer to these steps:
  • Tap the Ctrl + Shift + Esc keys to open the Task Manager.
  • Next, go to the Services tab and look for the service named “wuauserv” and get its PID.
  • After that, type “cmd” in the Windows Start search and right-click on Command Prompt from the search results and then select the “Run as administrator” option.
  • After opening Command Prompt with admin privileges, execute this command: taskkill /f /pid <PID>
Note: You need to replace “<PID>” with the PID of the “wuauserv” service. For instance, the PID is 6676, then this is how the command should be “taskkill /f /pid 6676”.
  • After you execute the command, you will this message on your screen, “SUCCESS: The process with PID 6676 has been terminated” which indicates that you have stopped the Windows Update service successfully.

Option 2 – Try to check the Service dependencies

Dependencies of a Windows Service in Windows 10 are when windows services depend on other services. Such is the case with the Windows Update service – it also depends on three different services such as the Remote Procedure Call or RPC service, DCOM Server Process Launcher, and the RPC Endpoint Mapper. Meaning to say, if two of these services are not working as expected, then the dependant service will also be affected. This could be the reason why the Windows Update service could not start.
  • Tap the Win + R keys to open the Run dialog box.
  • Next, type “services.msc” in the field and hit Enter to open Windows Services.
  • From the list of Services, look for the following services:
    • Remote Procedure Call (RPC) Service
    • DCOM Server Process Launcher
    • RPC Endpoint Mapper
  • After you find these services, double click on each one of them and check whether the Startup type for all is set to Automatic and the Service status is set to Running or not.
  • If the service status is not running, then click the Start button. Afterward, check if you can now run the Windows Update service.
Read More
Fix Windows Update Error 0x8007025D-0x2000C
Recently, a number of users reported getting an error code 0x8007025D-0x2000C while updating their Windows 10 computers using an ISO or the Media Creation tool. You will also see a detailed error message saying, “The installation failed in the SAFE_OS phase with an error during APPLY_IMAGE operation” together with the error code 0x8007025D-0x2000C. This kind of issue usually occurs when there is some problem with the installation files and when Windows Update fails to apply upgrade using the Media Creation Tool or ISO. To resolve this issue, you can use the troubleshooting options given below as a reference.

Option 1 – Try recreating the Windows 10 installation USB

Recreating the Windows 10 installation USB might help in fixing the problem. You can use a USB drive to do so but make sure that it has a great read-write speed. Follow the steps below to recreate Windows 10 installation USB”
  • Click this link and then click the Download Tool Now button.
  • Next, click the “Use the tool to create installation media (USB flash drive, DVD, or ISO file)…” option and follow the next given instructions on the screen.
  • Now select the ISO file option in step 5.
  • After that, you should now have an ISO file.
  • Next, go to the location where you’ve downloaded the ISO file.
  • Then right-click on the Windows 10 ISO file and select the Open with option and then select File Explorer.
  • Now click on “setup.exe” and follow the next instructions that appear on the screen. When asked, you have to select either Nothing (clean install) or Keep personal files only option. Take note that you must not select the “Keep personal files, apps, and Windows settings since it doesn’t really work.

Option 2 – Try running the Windows Update troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing Windows Update error code 0x8007025D-0x2000C. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 3 – Update the BIOS

Take note that you have to 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 4 – Try restarting the Background Intelligent Transfer Service

The Background Intelligent Transfer Service or BITS is a part of the Windows Update service and is the one that manages the background download of Windows Update, as well as scans for new updates and so on. And if Windows Update is experiencing some problems, you can try restarting BITS but make sure that you have admin privileges to do so.
  • Tap the Win + R keys to open the Run dialog box.
  • Next, type “services.msc” in the field and hit Enter to open Windows Services.
  • From the list of Services, look for the Background Intelligent Transfer Service and double-click on it to open Properties.
  • After that, you need to set the Startup type to “Automatic (Delayed Start) and click on Apply.
  • Now click the Stop button to stop BITS and then click the Start button to restart the service.
  • Click OK to save the changes made and then restart your PC.

Option 5 – Try to update Windows after a couple of minutes or an hour

There are times when the issue is from Microsoft’s end. It could be that there’s some issue with Microsoft’s server so it would be better if you give it a couple of minutes or an hour or so before trying to run Windows Update again.
Read More
Problem running preinstall.cmd scripts
Setting up the Windows operating system in a computer can be quite a complicated task since there are a couple of things that take place in the background to ensure a full and protected setup of the operating system which includes a number of programs, scripts, and so on. They work together in the background to guarantee the integrity of the Windows operating system. However, there are times when this piece of code could also go wrong. As a result, you might encounter errors like the “There was a problem running preinstall.cmd scripts” error. “Preinstall.cmd” is a type of CMD file associated with Applications & Drivers developed by Gateway for the Windows OS. To fix the “There was a problem running preinstall.cmd scripts” error, there are several things you can try. You can try to download a new Windows installation image or create a new bootable drive as well as uninstall conflicting or incompatible programs. In addition, you can also run the Windows Update troubleshooter or reset Windows 10.

Option 1 – Try to download a new Windows installation image

Your first option to fix the “There was a problem running preinstall.cmd scripts” error is to download a new Windows installation image. You can get the official ISO files for the latest release of Windows 10. After you’ve downloaded the ISO files, you can use them to upgrade to the latest Windows 10 version.

Option 2 – Try creating a new bootable drive

  • Insert your USB drive into your PC.
  • Tap the Win + R keys to open the Run dialog box and type in “cmd” and tap Enter to open the Command Prompt. Alternatively, you can also search for “cmd” in the Cortana search box to open Command Prompt.
  • Once you’ve opened CMD, type in this command to open the DISPART utility – diskpart
  • After that, you should see a new black and white window that would say, “DISKPART>”.
  • Next, type in “list disk” in the command line and tap Enter to see the list of all the Storage devices as well as your hard disk connected to your PC. Here, you have to identify your disk’s number.
  • Type in this command where “X” is the disk number you have identified and then tap Enter – disk X
  • Type in this command and hit Enter to clear the table records and all the visible data on the drive – clean
  • Now you have to recreate a new primary partition of the drive so you’ll have to type in this command and tap Enter right after – create part pri
  • A new primary partition has been created so you have to select it by typing this command and tapping Enter – select part 1
  • Now you have to format it to make it visible to normal users by typing – format fs=ntfs quick
Note: If your platform supports the Unified Extensible Firmware Interface or UEFI, replace the “NTFS” with “FAT32” in the command on Step 10.
  • After that, type in this command and tap Enter after – active
  • Finally, type this command and hit Enter to exit the utility – exit
  • After you prepare the image for the operating system, save it to the root of your USB Storage device.

Option 3 – Try to uninstall conflicting programs

If you are using a computer made by Dell and got Windows 10 preinstalled in it, then you can try to uninstall the programs listed below and see if it fixes the problem.
  • Dell Encryption Management service
  • Dell Digital Library service

Option 4 – Run the Windows Update Troubleshooter

You might also want to run the built-in Windows Update Troubleshooter in Windows that could help you in resolving the “There was a problem running preinstall.cmd scripts” error. All you have to do is go to Settings > Update& security > Troubleshoot > Windows Update. From there, click on the Run the troubleshooter button and follow the next one-screen instructions that appear. After that, restart your computer and check if the error is now fixed or not by trying to install the update once again.

Option 5 – Run Microsoft’s online troubleshooter

Running Microsoft’s online troubleshooter might also help you fix the error. This online troubleshooter is known to help in fixing Windows Update errors, it scans your computer for issues that might be causing the problem and then fixes them automatically.

Option 6 – Try to reset Windows 10

  • Tap the Win key or click on the Start button located in the Taskbar.
  • Then click on the Power button at the bottom right portion of the screen.
  • Next, press and hold the Shift key on your keyboard and then click on Restart. This will restart your Pc into the Advanced Startup options.
Note: Once you have access to the Advanced Startup options, you have to go to the setting which allows you to Reset your Windows 10 PC. All you have to do is select Troubleshoot > Reset this PC to reach the following screen Afterward, select either the “Keep my files” option and then proceed to the next on-screen instructions that follow to reset your Windows 10 computer without losing your files.
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status