How to reset TCI/IP stack in Windows

Error Code 0xC004C020 (Code 0xC004C020) – What is it?

Error code 0xC004C020 (Code 0xC004C020) is an error that occurs when you attempt to activate a copy of Windows 7 with a key, but the key has already been activated multiple times. When receiving this error code, it means that you are trying to exceed the number of times that the Windows 7 key is allowed to be activated. Common symptoms include:

• Attempting to install Windows 7 with a key and a dialog box with the code 0xC004C020 is displayed.
• The computer is unable to install Windows 7 with the key.
• Certain features will refrain from working until the correct key has been entered.

Solution

Error Causes

Error Code 0xC004C020 occurs when you are not able to install Windows 7 using a previously purchased key code that has been installed numerous times previously on the same computer.

• You are not able to use your previously used key to install Windows 7.
• You have used the Windows 7 key the maximum number of times allowed.

Error code 0xC004C020 simply means that the Windows 7 code that you are trying to use to install Windows 7 has already been used the maximum number of times allowed, even when installing it on the same computer that it was previously used on. This would indicate that the key is what is known as a volume key- meaning that there is a cap on the number of uses.

Further Information and Manual Repair

Many people encounter this problem when they are doing software development or testing and need to reinstall Windows 7. Some people might also encounter this error code when installing Windows 7 with a key that was used too many times previously. It should be noted that there are several ways to fix this problem, but if nothing is working, you should contact a computer repair technician.

Method One

Activate by phone- the long method.

1. Click the start button, right-click Computer, click Properties, and then click Activate Windows.  This will open Windows Activation.
2. Click on “Show me other ways to activate”.
3. Find and enter the Windows 7 key, then click Next.
4. Click on “Use the automated phone system”. If you are prompted for an administrator password or a confirmation, confirm or type the password now.
5. Select the location nearest to you and then click the Next button.
6. There will be a list of available phone numbers, choose one and call it. There will be an automated system that will guide the activation process.
7. Enter the installation ID when prompted, it will be listed on your computer screen.
8. The phone system will give you a confirmation ID, write this down.
9. Type this confirmation ID into the space that is provided by step 3. This will be in the activation dialogue. Then, click NEXT and follow the instruction.
10. If this is not successful, stay on the line and be transferred to a customer service representative that will assist you.

Method Two

Activate by phone- this is a much simpler method.

1. Click on Start, type: slui.exe 4 into the Search box
2. Press Enter on the keyboard.
3. Pick your country.
4. Choose the Phone Activation option; stay on hold to speak with a customer service representative.

Method Three

Error code 0xC004C020 occurs if you have used your Windows 7 activation key on multiple computers, or multiple times on the same computer. You are not allowed to exceed the uses of the key—you should consider purchasing a new key if this is the case. A Windows 7 key is available for purchase online through the Microsoft website, in the shop section. The new product key must then be activated within 30 days, or it becomes no longer valid. It can be activated online or through the telephone. If it is not activated on time, features will stop working until the new key has been activated. This should be the last resort method, as you should not have to purchase a new Windows 7 key code if it is not necessary. If you wish to always have at your disposal a utility tool to fix these Windows 10 and other related issues when they do arise, download and install a powerful automated tool.

Error Code 0x802400d - What is it?

The Error Code 0x802400d most often occurs when users attempt to use the Windows Update tool on their computers to move from one version of the software to another. In some cases, this error is more likely to appear on your computer during the process if you have not performed regular updates to the software as they have been available.

Common symptoms include:

• Inability to finish the download of the necessary update to Windows 10
• Incomplete installation of the desired Windows 10 update

While it can take additional time to deal with the issues that cause Error Code 0x802400d to appear on your computer, there are several steps that you can take to address the problem. These are fairly simple to perform and do not require advanced knowledge of the system to employ.

Solution

Error Causes

The most basic cause for Error Code 0x802400d is that there is a file or a process that is causing the update process to hiccup. In many cases, this error appears when a user attempts to begin the process of updating their computer if they have several stacked updates to perform. Computers that are several updates behind where they should be will display this error more often than computers that are kept on a schedule of recommended updates.

Further Information and Manual Repair

While there are multiple reasons why the Error Code 0x802400d may appear on your computer during the Windows Update process, there are several methods that can be used to attempt to resolve the problem on your own. These are generally easy to do and do not require advanced techniques. However, if you do not feel comfortable addressing the issue on your own, contact a qualified Windows repair technician.

Here are some of the best methods that users can employ to resolve Error Code 0x802400d:

Method 1:  Run the System Update Readiness Tool

There are a number of different processes, files, and settings that could cause Error Code 0x802400d to appear on your computer during the Windows 10 Update process. For this reason, the most efficient way to determine what the culprit is for your specific issue is to download and use the System Update Readiness function.

This tool is available directly from Windows. Although there are other tools available on the Internet that claim to be able to fix the problem, these can contain viruses and malware, so be cautious if you decide to employ these instead. There are also several versions of the tool on the Windows website, so be sure to download the version that matches the operating system and version of your computer.

Once you have downloaded the Readiness tool from the Windows website, allow it to run a scan on your system. At a minimum, this process will take about fifteen minutes to complete. Although you will see a progress bar at the bottom of the window, it does not always update effectively. Some users have reported that the update appears to stop when it is two-thirds complete. Continue to let the scan run if this happens, rather than canceling it out. Even if the progress bar doesn’t update, the scan is still running.

Method 2: Remove New Software and Re-Attempt the Update Process

If you have recently installed new software on your machine, it can sometimes cause problems with the update process. The best way to resolve this issue is to remove or uninstall the software, run the update process again, and then reinstall the software once the Windows system has been successfully updated.

If the above methods are not successful in resolving Error Code 0x802400d from your machine and you are still unable to complete the Windows 10 Update process or if you are not confident in your ability to complete these steps successfully on your own, get in touch with a qualified computer repair technician who is familiar with the issues surrounding Windows 10 in particular. Microsoft offers certifications for Windows repair technicians, so look for a professional who has the experience, skills, and knowledge necessary to adequately address Error Code 0x802400d on your machine.

If you wish to always have at your disposal a utility tool to fix these Windows 10 and other related issues when they do arise, download and install a powerful automated tool.

Can graphic cards wear out over a longer period of time? Recent studies and experience from crypto miners say no but they can die due to different reasons like improper use, low cleaning habits, factory mistakes, etc. Many gamers and people who use GPU intense applications tend to think that some glitches and hiccups in the software are a sign that graphic card is dying out and that it is time to be replaced. Altho this could be true in many cases these kinds of behavior are mostly due to old drivers and software issues. Older cards can produce these kinds of results due to their old age and new software is often more demanding than these cards can handle. So in order to diagnose and be sure that your GPU is indeed dying out lookout for these signs.

The Main Signs of a Dying GPU:

The Computer Crashes and Won’t Reboot

If your computer shutdown while working in the graphic application or while playing the game and the monitor loses signal there is a high chance the graphic card is soon going to be gone. Some motherboards have hardware detection failure and can signal immediate fail. If when turning your computer ON you are greeted with a blue screen with the message that the signal can not be found or you do not have picture at all it is most likely that GPU has failed.

Graphic Glitches While Playing Games

If you are playing the game and all of sudden you get off-color pixels, screen flickering, strange graphic behaviors, random artifacts, or similar and that keeps repeating in multiple games it is likely that GPU days are coming to an end.

Abnormal Fan Noise or Performance

Fans are an essential part of cooling the GPU and over time if they are intensively used they could wear out and need replacing. If however you have not noticed and have not replaced the fans card can sustain overheating damage. Many cards have cooling fans that are designed to spin at a higher RPM only when the GPU is under load. It prevents bearings in the fans from dying prematurely, so don’t worry if one of your fans is inactive while you are browsing the web. However, when you play games that utilize software that your card isn’t built to support, the bearings in the fans wear out faster. Once the fans stop working under load, the graphics card can quickly die.

How to Diagnose a Dying Graphics Card

Presented next are essential steps in order to recognize a dying graphic card.

Check Motherboard Error Codes

Many motherboards today completely shut down a component that is no longer working. If your graphics card has died completely, this may be one of the easiest ways to tell. If your motherboard doesn’t have display codes, you can try testing the card in a new system.

• Open the computer case: Use your screwdriver to remove screws on the side panel and gently slide it back.
• Locate the error code display on your motherboard: If you have a motherboard with error codes, they should appear near an outer corner.
• Try to reboot your computer: Record each error number you see after you boot your computer.
• Consult the motherboard manufacturer manual for error codes: Open the manual and locate the list for your error codes. If the code matches a graphics processing unit error, your video card could have died.

Check Hardware for Damage or Debris

A graphics card that has damage or debris on the physical parts might quickly overheat and kill the card.

• Remove the screws holding the GPU in place: There are typically one or two screws holding the card to a bracket on the case.
• Unhook the power cords from the GPU and pull the release tab: Remove the power cords from your GPU by pushing in their tabs and gently rocking them out. Once you remove each cord, gently push or pull up on the release tab near the motherboard.
• Inspect the GPU for damage/debris: Check the card for any dirt or debris buildup and clean it out with a Q-tip. You can replace broken fan pieces from the manufacturer.

Test Your GPU Under Load

Download GPU stress-testing and heat-monitoring software.

• With the card installed, run a stress test.
• As you are running the stress test, run heat-monitoring software: With the stress test running, check your heat-monitoring software for GPU overheating. Any reading over 80 degrees Celsius is too hot.
• Check device manager for outdated drivers: If your GPU is clean, but still running too hot, your software drivers are not installed correctly. To check, type in “device manager” at the bottom of your desktop and click on Device Manager. Find your display adapter and right-click on it to see if it’s working. If your drivers are not working correctly, it is indicated here usually. However, the driver may appear to be functioning even if it says otherwise in the properties.

Keep your graphic card drivers updated

When you don’t have the right driver installed, graphics cards can quickly burn up, and their cooling components may fail faster. That’s why you should always keep drivers updated for each new game you install or play. Older games may also release new software patches, so your GPU drivers should be updated accordingly.

Windows 11 release date is closing in, some people have tried it via insider build, some have decided not to. It has come to our attention that there is a little website made by BlueEdge that offers a virtual Windows 11 desktop. Opening the Website will put you right inside Windows 11 desktop, now take note that this is not Windows 11, it is a simulation of Microsoft’s newest OS and therefore many things will not work like File Explorer, etc. One thing you can make sure it is working is UI itself, you can see how you do like the new Taskbar, start menu, widgets, and some other things. You can just pop up on the site and check how you do like the overall new look and feel of Windows 11 UI before installing it or trying it. We are sure that many more options will come in time but even now you can get a feel of the newest OS. Windows 11 BlueEdge site: https://win11.blueedge.me/

There are times when an IT admin has to set up multiple IP addresses to the same network adapter. Setting up multiple IP addresses in scenarios like hosting various SSL sites, speed up traffic exchanges can help in avoiding being blacklisted in the SPAM filters, and so on. So in this post, you will be guided on how exactly you can assign multiple IP addresses to the network adapter in your Windows 10 computer. There are several ways to assign multiple IP addresses in a network adapter. You can do it using the Network Adapter settings or using the Netsh utility, as well as the Windows PowerShell utility. To get started, refer to each one of the options provided below.

Option 1 – Assign multiple IP addresses via Network Adapter settings

• Go to Settings first and from there, select Network & Internet, and then click on the Change adapter options. This will show you a list of both the physical and virtual network adapters in your computer.
• Next, double click on the Ethernet adapter where you want to assign the multiple IP addresses and then click on the Properties button.
• After that, you should see the Ethernet properties where you have to select the “TCP/IPv4” or “TCP/IPv6”.
• Once done, click on the Properties button and then select the “Use the following IP address” option under the General tab.
• Now you have to add an IP address, subnet, and default gateway to the network adapter and then click on the Advanced button.
• This will open the Advanced TCP/IP settings where you have to click on the Add button so you can add an IP address. From here, you can keep adding multiple IP addresses to the network adapter. You also have the option to add multiple gateways or DNS IP addresses.
• Once done, if you execute the “ipconfig” command, you should see all the secondary IP addresses listed.

Option 2 – Assign multiple IP addresses using the Netsh command

Another way to assign multiple IP addresses to your network adapter is via the Netsh command.

• In the Start Search, type “command prompt” and from the search results that appear, right-click on Command Prompt and then select the “Run as administrator” to open it with admin privileges.
• If a User Account Control or UAC prompt pops up, just click on Yes.
• After that, run this command: Netsh int ipv4 add address name="Local Area Connection" 192.168.100.100 255.255.255.0 SkipAsSource=True

Note: You have the option to set “SkepAsSource” since it depends on your needs using the Netsh command. When it is configured as true, the IP address won’t be used by the OS for outbound connections.

Option 3 – Assign multiple IP addresses via Windows PowerShell

• Tap the Win + X key combination and click on the “Windows PowerShell (Admin)” option.
• After opening Windows PowerShell as admin, use the NetIPAddress command so you can add more IP addresses. Execute this command: Get-NetIPAddress | ft IPAddress, InterfaceAlias, SkipAsSource
• Next, assign an IP address to a network adapter by executing this command: New-NetIPAddress –IPAddress 192.168.100.100 –PrefixLength 24 –InterfaceAlias “vEthernet” –SkipAsSource $True
• Now to modify the “SkipAsSource” parameter, use this command: Get-NetIPAddress 192.168.100.100 | Set-NetIPAddress -SkipAsSource $False

There are times when you encounter some issues while your Windows 10 computer. One of the errors you can encounter in the update process is the “Something went wrong, error code 0x8007042B”. This kind of error might be caused by several reasons and it could also pop up in lots of cases like upgrading to a new feature update or a new build using the Media Creation tool or Windows Update Assistant. There are times when the Windows Update error code 0x8007042B is followed by another error code like 0x2000d. Whatever the extra error code that follows, the core issue still remains the same. To resolve the problem, here are some options that could help. And while going over these troubleshooting tips, you have to keep clicking the Update button right after you carry out a troubleshooting option.

Option 1 – Try to restart 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 2 – Try creating Windows 10 ISO media

In this option, you will have to create a Windows 10 bootable media and use it to install the latest Windows 10 version. The most user reported that this option works and the reason why it does have something to do with the Windows Update client since the Windows Updates downloaded from the regular Windows Update client seems to create issues such as the Windows Update error code 0x8007042B. However, issues like this one don’t occur when the very same Windows Updates are downloaded and installed via an ISO file. Take note that when using a Windows ISO file, you will be asked to choose what you want to do with the previous settings and apps. A lot of users opted for the “Not to keep the old Windows settings” option which has resolved the issue. So if you want to keep the previous settings then you must try to update Windows first while keeping the old settings. However, if it doesn’t work, you have to try installing the latest version of Windows without keeping the previous settings.

• 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 the Nothing (clean install) or the 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 3 – Run the DISM tool

You can run the DISM tool as well to help fix the error code 0x8007042B during Windows Update. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

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

Option 4 – Perform a System File Checker scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the Windows Update Error 0x8007042B to appear. 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. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow and hit Enter.

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

Option 5 – Run the Windows Update Troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing Windows Update Error 0x8007042B. 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 6 – Contact Microsoft Support for assistance

If you’re at your wits’ end in trying to update your Windows 10 computer, you should consider contacting Microsoft Support for help as they can offer you various options that would make fixing Windows Update Error 0x8007042B a lot easier and faster.

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 are trying to install Office but got an error saying, “Something went wrong, Sorry we ran into a problem” with error codes 12002-4, 12007-4, or 12152-4 instead, this indicates that you have a problem with your internet connection. Aside from internet connection issues, the problem could also be due to some programs that block the installation files to be downloaded so when they time out, you get these error codes. There are several options you can try to fix the 12002-4, 12007-4, or 12152-4 error codes. You can try to install Office offline or turn off the proxy server or VPN (if you’re using one). You can also try to temporarily disable your antivirus program or Firewall. Refer to the given potential fixes below to troubleshoot and fix the problem.

Option 1 – Try to install Office offline

The first thing you can do if you encounter the error codes 12002-4, 12007-4, or 12152-4 when installing Office is to download an offline copy of Office especially when you’re certain that your internet connection is slow. Once you’ve downloaded it, install it again. The offline installer will download both the 32 and 64-bit versions of Office. Keep in mind that you must download the correct version.

Option 2 – Disable the Proxy server

The first thing you can do is to try disabling the Proxy server as it might be the reason why you’re getting error 0x80244022 for Windows Updates. To disable the proxy server, refer to the steps below.

• 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. In addition, if you are also using a VPN, you can try to disable it as well.

Option 3 – Temporarily disable the Antivirus and Firewall

As mentioned earlier, the downloading of the installation files could be blocked by either the antivirus program or Firewall or it could be both especially when the link seems suspicious. To fix this problem, you have to disable both the antivirus like Windows Defender and the Firewall or any third-party software you might be used temporarily and then download the installation files again. Once the download is completed, make sure to turn on the antivirus program and the Firewall again. On the other hand, you can also try downloading in a different location which also means that you have to try a different network. It could be that the load on the current system is too high which is why it’s not able to offer enough bandwidth to download the installation files of Microsoft Office.

If you suddenly encountered an error when you try to run the Windows Sandbox that says, “Windows Sandbox failed to start, Error 0xc030106, The virtual machine or container exited unexpectedly”, read on as this post will guide you on what you can do to resolve the problem. According to security experts, this kind of error in Windows Sandbox is due to some issues with the supporting virtualization component. It could also be caused by other factors and to fix it, there are several potential fixes you need to check out. You can try running the Windows Sandbox as an administrator. You should also make sure that all the supporting processes are running properly, as well as try to install any pending Windows Updates.

Option 1– Try to run Windows Sandbox as an admin

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

Option 2 – Ensure that all the supporting processes and services are running properly

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

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

Option 3 – Try to install any pending Windows Updates

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

If you are trying to copy a folder or a file but encountered an error that says, “An unexpected error is keeping you from copying the folder. If you continue to receive this error, you can use the error code to search for help with this problem”, read on as this post will guide you on how you can fix this error. This kind of error is a CHKDSK error. It is the “Volume is dirty” error message with error code 0x80071AC3 which indicates that the CHKDSK operation on your computer did not go through due to some corrupted sector of your hard drive, data corruption, corrupted system files, malware infection, as well as improper installation of an application that left some residual folders and files and many more. To fix the Error 0x80071AC3, here are some potential fixes you can check out to resolve it:

Option 1 – Run the Check Disk utility

You can also run the Check Disk utility to fix the error when you connect your USB or external device.

• In the Windows Search box, type “command prompt” and from the search results, right-click on Command Prompt and select “Run as administrator”.
• After opening Command Prompt, type this command and tap Enter: chkdsk /r /f <PARTITION LETTER>
• The command you entered will start to check for errors and fix them automatically. Else, it will throw an error message saying, “Chkdsk cannot run because the volume is in use by another process. Would you like the schedule this volume to be checked the next time the system restarts? (Y/N)”.
• Tap the Y key to schedule Disk Check the next time your computer restarts.

Option 2 – Try to check if a particular volume is dirty and exclude it

The next thing you can do to fix the problem is to check if the particular volume is dirty and exclude it. To do so, follow these steps:

• In the Start Search, type “command prompt” in the field 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: fsutil dirty query <PARTITION LETTER>
• After that, you will see either of the following results of the command you just executed:
  • “Volume <PARTITION LETTER> is dirty”
  • “Volume <PARTITION LETTER> is not dirty”
• If you see the “Volume <PARTITION LETTER> is dirty” message, then you can just skip checking the drive for errors by executing this command: CHKNTFS /X <PARTITION LETTER>

Option 3 – Try to format the destination drive

If the first two options above didn’t work, then you might want to try formatting the drive can also help you resolve the error. To format it, follow these steps:

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