Logo

Windows 11 23H2 Update Details Revealed

Loving Windows 11 so far? We sure are. Microsoft has clearly decided to take its OS to the next level and keeps showing it through every update. It makes you wonder what’s next - and today, you’ll find out!

Tons of new features have been leaked, and we can probably expect them with the 23H2 update. Here’s everything you need to know so far.

What’s Windows 11 23H2 bringing?

Windows 11
Credit Windows on Unsplash

There are plenty of new features already confirmed for Windows 11. The only issue is we don’t know for sure if they’re coming with the 23H2 update or separately, at a different time. Whatever the case, a lot of them are pretty exciting.

Here’s an overview of what we might be getting this fall.

  • Windows Copilot. Microsoft wants to add this AI-powered feature based on chatbots like Bing Chat and ChatGPT to assist users with all kinds of actions and tasks on the platform. As part of this development, the integration of first- and third-party plugins and the Bing Chat AI will be enhanced. This is a pretty amazing addition to look forward to, if you ask us.
  • Dynamic Lighting. RGB lovers will rejoice upon this one! Dynamic Lighting will allow you to control your RGB-powered components directly through the Windows Settings, allowing smooth integration of your favorite peripherals with your OS. No need for third-party software anymore!
  • Taskbar enhancements. Microsoft has announced some neat improvements to the Windows 11 taskbar. For one, we’ll be able to hide the Time and Date now, which is extremely useful for focus, but also for clean screenshots. Another change is the ability to shut down programs directly from the Taskbar, without having to run the Task Manager.
  • Expanding native support for archive formats 7-zip, rar, gz and others on the libarchive open-source projects.
  • Microsoft Store AI features. The theme of AI power is clearly being taken up a notch, because the Microsoft Store seems to be getting several awesome features in this regard. One of them is AI hub, which “curate the best AI experiences built by the developer community and Microsoft” (Windows Developer Blog). We’re not sure what that means exactly, but we sure can’t wait to see.

Another is AI-generated keywords, designed to improve the discoverability of apps you’re searching for. Moreover, the AI-generated review summary is designed to give us a simpler experience looking at reviews. Huge numbers of reviews will be compiled into a summary that’s easy to scan and lets us discover new content faster.

  • Other Microsoft Store improvements. Business owners will be happy to hear that Microsoft Store ads will now reach 150+ regions worldwide, significantly increasing the audiences they can target. Furthermore, there will be enhancements to the Backup and Restore functionality to give users a more seamless experience in case they switch devices. 
  • File Explorer changes. Rumor has it that Microsoft is working on a Gallery to be embedded within the File Explorer. The addition of a Recommended section might be on the horizon as well. 
  • Widget Panel update. The introduction of the Widget Panel in itself was exciting for many. As a next step in the development of this feature, Microsoft is planning to make it possible to pin widgets to the desktop. 
  • Presence sensor. You might actually already have this one, as it was rolled out as part of Moment 3 for compatible devices. With the Presence sensing app, found in the Privacy settings, you can decide which (if any) apps use APIs to detect the state of your activity on Windows. This can significantly enhance privacy and security, as you can have apps containing sensitive data lock automatically when unattended. If you’re a laptop user, it can also be beneficial to your battery life.
  • Bluetooth LE. Microsoft is adding support for Bluetooth Low Energy, a functionality that allows reduced battery consumption when devices are connected.
  • Adding more languages to the Live Captions feature. This specification is only as powerful as the languages it supports. Microsoft is reportedly working on expanding the list with 10 more languages.

Summary

We’ve got some interesting stuff to look forward to with the next major Windows 11 update. And these are just the things the Internet’s actually heard of, so who knows what else Microsoft might be planning? It remains to be seen, hopefully just a few months from now. 23H2 has been released on October 31st.

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

Your Windows license will expire soon
If you suddenly get a message telling you that “Your Windows license will expire soon, You need to activate Windows in Settings” on your Windows 10 computer but you know that your Windows 10 is already activated. Worry not for this post will help you get rid of that error message right away. Before you get started, make sure that you have the Windows product key with you. If you don’t, you can get it by running the following command in an elevated Command Prompt:
wmic path SoftwareLicensingService get OA3xOriginalProductKey
Take note of the product key and then proceed to the options given below.

Option 1 – Try activating Windows 10 again or use another product key

  • If you’re sure that you have the correct product key, click the Go to the Settings button.
  • After that, click the Activate button once again.
  • If you have another license key, you can also use that as well, just simply click on the Change product key.
  • Then enter the new product key and click on Activate. That should fix the problem, if it doesn’t, refer to the next option below.

Option 2 – Try to reset the licensing status

  • Click the Start button and then type “cmd” in the Search box and then tap Ctrl + Shift + Enter to open an elevated Command Prompt.
  • Next, type the “slmgr –rearm” and hit Enter to reset the licensing status.
  • Restart your computer and check if the error is now gone or not.

Option 3 – Try uninstalling the product key and re-enter it once more.

  • The first thing you have to do to uninstall the product key is to know the Activation ID of your Windows installation. To do so, open an elevated Command Prompt and type this command, and hit Enter – vbs /dlv
  • After you enter the command, you should see the licensing status and Activation ID. And to get all the Activation IDs of all the installed Windows versions, key in this command and hit Enter – vbs /dlv all
Note: The “/dlv” parameter will give you the license information for the installed operating system.
  • After you enter the second command, you should see a Windows Script Host window with all the Windows licensing and activation status. Take note of the Activation ID.
  • Next, in the same elevated Command Prompt, type this command – slmgr /upk <Activation ID>
Note: In the third given command, “/upk” stands for “uninstall product key”. This parameter uninstalls the product key of the current Windows edition.
  • Restart your PC. After that, your computer will be in an unlicensed state so you need to re-enter the product key again.

Option 4 – Try rebuilding the Tokens.dat file.

The issue might be caused by a corrupted Tokens.dat file. The Tokens.dat file is a digitally signed file that stores most of the Windows Activation files so if it is corrupted then no wonder you’re having activation issues. To rebuild the Tokens.dat file, refer to these steps:
  • From the WinX Menu, open an elevated Command Prompt.
  • After opening Command Prompt, you need to type each one of the following commands and after you type each command, hit Enter.
    • net stop sppsvc
    • cd %windir%ServiceProfilesLocalServiceAppDataLocalMicrosoftWSLicense
    • ren tokens.dat tokens.bar
    • net start sppsvc
    • exe %windir%system32slmgr.vbs /rilc
  • Now restart your computer.

Option 5 – Try running the Windows 10 Activation Troubleshooter

  • Go to Settings and then select Activation.
  • After that, click on the Windows Activation and then troubleshoot. This will help you address most of the commonly found activation issues in Windows devices.

Option 6 – Try activating Windows 10 via mobile phone

Activating Windows 10 can also be done using your phone. Just note that you have to call Microsoft to do so.
  • In the Start Search box, type in “Slui 4” and tap Enter.
  • Next, select your country and click on Next.
  • Keep the window open and call the toll-free number of the country you’re from.
  • Afterward, a confirmation ID should be given by the automated system which you must take a note of.
  • Finally, in the box on the window, type in the confirmation ID and click on the Activate button. That should do it.
Read More
Fix Remote Desktop: Your credentials ...
Experiencing issues while using Remote Desktop connections is not uncommon. One of the issues that users encountered recently while trying to connect to their Remote Desktop network is the error saying, “Your credentials did not work, The login attempt failed”. If you are one of these users, then you’ve come to the right place as this post will walk you through fixing the problem. When facing this kind of problem, the first thing you can try before you do some troubleshooting steps is to verify the credentials. But if you are certain that you’ve entered the correct credentials just like what other users reported, then it’s completely a different matter. Based on the reports, this error is common on newly installed versions of Windows 10 or after reinstalling the operating system which could mean that the problem might be due to the Windows security policies or the username might have been recently modified. The latter case is a possibility especially if you’ve reinstalled Windows 10 and had entered a new username. In such a case, you will really have a difficult time connecting to your Remote Desktop connection since its credentials do not really automatically change. If you’ve verified that your credentials are correct, then now’s the time you troubleshoot the problem with the help of the potential fixes provided below. Just make sure that you follow each one of them in sequence.

Option 1 –Try to run the Network Adapter troubleshooter

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

Option 2 – Try to change the network profile from public to private

According to some reports, this error occurs on systems where the network profile was set to public. Thus, you need to change the network profile to private to resolve the problem. How? Refer to these steps:
  • Go to Start and from there click on Settings > Network & Internet > Status.
  • Next, click on the “Change connection properties” option.
  • After that, set the radio button of Network Profile from Public to Private.
  • Wait for a couple of seconds until the system is done applying the changes you’ve made and then see if you can now connect to the Remote Desktop connection.

Option 3 – Try changing the account username

As mentioned, one of the possible causes for this error is the reinstallation of the operating system. You might have changed the username for the system but it does not really change the username of the Remote Desktop connection as well. Thus, you have to change the username back to what it was before you’ve reinstalled Windows 10.

Option 4 – Try modifying the Windows Security Policy

You can also try to edit the Windows Security Policy as it could help in resolving the error. This Windows Security Policy, when enabled, will not allow non-admin users to log on to the Remote Desktop connection. So if you want to allow non-admin users to use the Remote Desktop connection, then you need to modify this policy. Note that you can only do that if you are the admin of the system yourself.
  • Tap the Win + R keys to open the Run utility.
  • Then type “secpol.msc” in the field and tap Enter or click OK to open the Local Security Policy.
  • After opening the Local Security Policy window, select Local Policies > User Rights Agreement located on the left pane.
  • Next, double click on “Allow log on through Remote Desktop Services” located in the right pane.
  • And in the next window that appears, select Add user or group.
  • After that, type in the username of the intended non-admin user under the “Enter the object names to select” column.
  • Once done, click on the Check Names button to fix the username and then click OK to save the changes made.
  • Restart your computer.

Option 5 – Use the Group Policy Editor

  • Tap the Win + R keys to open the Run dialog box and then type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
  • Next, navigate to this path: Computer Configuration > Administrative Templates > System > Credentials Delegation.
  • Double click on the “Allow delegating default credentials with NTLM-only server authentication” policy setting located on the right pane to edit it.
  • After that, shift its radio button to Enabled and click on Show.
  • Then type “TERMSRV/*” in the Value box and click OK.
  • Now repeat the same for the following policy settings:
    • “Allow delegating default credentials”
    • “Allow delegating saved credentials”
    • “Allow delegating saved credentials with NTLM-only server authentication”
  • Once you’re done, restart your computer and see if the problem is fixed.
Read More
How to Fix Windows 8 Error Code 0x80070422

Error Code 0x80070422 - What is it?

Error Code 0x80070422 can be found on many versions of the Windows operating system including Windows 7, Windows 8, and 8.1, and Windows 10. The reason for its occurrence may vary, however, depending on the version of the operating system that you use.

In the case of error code 0x80070422 in Windows 8, it often occurs when users attempt to update their firewall or download apps from the Windows store. When this error occurs the user is unable to complete the updates and will need to apply different solutions to correct the issue.

Solution

Restoro box imageError Causes

Whenever error code 0x80070422 is encountered on Windows 8 or 8.1, it might be a result of various factors. These error codes include:

  • Registry errors – This occurs when new programs are installed over old ones
  • Malicious software such as adware, spyware, and or viruses

Further Information and Manual Repair

You do not need to be a Windows expert to attempt to solve errors like the 0x80070422 Windows 8 error code. Simply try the solutions below. If however, you feel you need a professional’s help, contact a certified Windows technician.

  • Check for any viruses or malicious software

Viruses and other malicious software are often the cause of various issues within the PC. For this reason, be sure to check your machine for a possible virus infestation. If you are unable to use your anti-virus software or if none is present you might need to download an automated tool that offers overall repair and other solutions.

  • Disable third-party security apps

Another step you can take is to disable third-party security apps. When these apps are downloaded onto your device, it can lead to the disabling of your Firewall and the inability of your device to download other apps. If this is the source of the 0x80070422 error code on your machine, the issue will be resolved after you disable the third-party apps and reboot your computer.

  • Disable Firewall

If error code 0x80070422 in Windows 8 or 8.1 occurred while you attempted to update Windows firewall, one of the best solutions you can try is to disable the firewall. Note however that disabling your firewall should be temporary as it protects your computer from worms as well as hackers that might infect or compromise your PC. Access the firewall by swiping right on the screen then searching for “firewall”. Click “Windows firewall” then select “Turn off Windows firewall”.

  • Performs a clean boot

Another option is for you to perform a clean boot. This simply refers to a reboot in Windows where only a minimum set of drivers and programs are used. A clean boot can help resolve issues related to software conflict which can occur when Windows users install programs or updates or simply run a program. Note that you must log on to the computer as an administrator. Otherwise, you will not be able to perform the clean boot.

  • Clean registry

The source of many errors related to Windows can lie within the registry. This is because the registry is involved in every aspect of a Windows computer’s operation. If there is an issue in the files of the registry or if it has been hacked, your computer will not function. For this reason, begin by cleaning the registry regularly. To clean our registry, use a powerful tool that is both reputable and user-friendly. Research your option before you make a selection as choosing the wrong tool could lead to even more errors or computer malfunctions.

  • Set Windows Update to Automatic

Another important method to solve issues related to error code 0x80070422 in Windows 8 or 8.1 is your Windows Update service. Though you may have never noticed this feature before now, the Windows Update services allow PC owners to access updates to their operating system automatically. This leads to a properly functioning PC as your machine will always have the latest features and tools available. However, if the setting is not correct, your computer may end up experiencing error code 0x80070422. Check if this is the source of your problems by verifying if your Windows Update settings are automatic. Once the settings are on automatic, reboot your machine to ensure your computer responds to the changes.

  • Download an Automate Tool

Always be prepared for the possibility of other errors. You can do this by downloading powerful software. This enables users to regularly check for issues that may cause errors on their Windows device.

Read More
Finding out which GPU is in your computer
Every computer has to have a graphic card, it is one of the essential components in order for the computer to work. If you have a second-hand computer, got one as a gift, or similar, there is a high chance that you do not really know which components are inside. Luckily finding out which graphic card you have inside is quite easy. Right-click the taskbar and select Task Manager Click the Performance tab at the top of the window, if you don’t see the tabs, click “More Info.” Select “GPU 0” in the sidebar. The GPU’s manufacturer and model names are displayed at the top right corner of the window. You’ll also see other information, such as the amount of dedicated memory on your GPU, in this window. Windows 10’s Task Manager displays your GPU usage here, and you can also view GPU usage by application. If your system has multiple GPUs, you’ll also see “GPU 1” and so on here. Each represents a different physical GPU.
Read More
How to Fix Windows 10 Error Code 0x80072F8F

Error Code 0x80072F8F - What is it?

Error Code 0x80072F8F manifests in one main way. It is known to appear as early as Windows 7, and mainly deals with an error that occurs in the update process, or when the computer is trying to connect to the online activation service. It can appear when the activation fails to verify the product key. The error code will present itself when the system realizes that the PC's date and time are incorrect. Error Code 0x80072F8F will also appear if the computer has determined that the time zone settings on the computer are not accurate.

When Windows is going through the installation process and is verifying all of the information associated with the computer, Error Code 0x80072F8F will arise, indicating that the information in the computer's settings is not valid. Correct times and dates are necessary when using serial validation keys to install Windows. When these settings are outside of the tolerated window, the problem will arise.

Error Causes

There is only one main symptom to look out for, and it will manifest during a Windows installation. In the midst of the installation, the computer will not be able to proceed with the installation if Error Code 0x80072F8F has popped up. Because the information cannot be verified, Windows will not be able to continue the installation process when the time settings are not accurate. This interrupts the process, causing the need to edit the settings, restart the computer, and try again. It is imperative to be sure that the date and time on the computer are inside of the tolerated window for the serial key.

  • This error code will not give any information on how to correct it.
  • Windows Error 0x80072F8F is displayed on the screen.
  • The error code appears when typing the Windows serial key and proceeding.

Further Information and Manual Repair

When experiencing Error Code 0x80072F8F, the date and time need to be corrected in the computer settings menu, and then verify the correct time zone settings.  There are a few different ways to edit the time and date settings, and one may need to even edit the time zone settings. After this, restarting the computer may be needed. When booting into Windows, the validation code should be activated within 30 days of obtaining the serial number.

  • Method One

Check the time and date settings.

  1. Open the Start menu.
  2. Select Settings, then Time and Language, then Date and Time.
  3. Check and make sure that the PC is operating at the correct time and date.
  • Method Two

Ensure that the computer is connected to the internet.

  1. Enter “network troubleshooter” into the search box located on the taskbar.
  2. Select “Identify and Repair Network Problems”.
  3. Follow the instructions that are given on-screen. This will fix any problems that the network is experiencing.
  • Method Three

Review the timezone.

  1. Open the Start menu.
  2. Select Settings, then Time and Language, then Date and Time.
  3. Check to make sure that the correct timezone is selected from the drop-down menu.
  • Method Four

Reboot the PC and check if that fixes the problem. This may help in the event that the network troubleshooter does not detect a problem.

After completing these steps to edit the time, date, and time zone settings, it may be necessary to restart the computer. This is to ensure that the computer will save and recognize the new settings. After restarting, continue the process as intended and enter the product key. The computer will now be able to verify the product key since the time and date will be recognizable. The Windows installation should proceed as normal and complete successfully when the time, date, and time zone are inside of the parameters for the Windows product key.

In short, if it is not, the computer will not be able to recognize the product key, thus will not be able to install the Windows product. Generally, the fix is quite simple and does not take much time at all, but it is very important.

Read More
Ordinal not found, dynamic link library Error
If you encounter an error message saying, “The ordinal xxx could not be located in the dynamic link library C:/Program Files (x86)/Microsoft VS Code Insiderscode – insiders.exe“ and you see a reference of a missing DLL file, then this indicates that the software is trying to locate the related DLL file, however, it is missing, hence the error. The error mentioned “Ordinal” which refers to the order of a number mathematically, e.g. 1st, 2nd, etc. And in this error message, the ordinal is referring to an Xth file of an XX.DLL file which is missing which is why you’re getting this kind of error. When you get this particular error, it means that your computer is missing the Microsoft Visual C++ Redistributable program. As per the error message, XXX is a number that in turn is the Ordinal. There is also another common error related to Ordinal which says, “The ordinal 12404 could not be located in the dynamic link library mfc90u.dl”. The error message could be referring to any DLL in the message. And since all these DLL files are part of the package, the error changes quite a bit as the Visual Studio looks for that DLL file. To fix this error, here are some suggestions that might be of help.

Option 1 – Try installing Microsoft Visual C++ Redistributable

As pointed out earlier, the error pops up when the Microsoft Visual C++ Redistributable program is missing on your computer. Thus, you need to download it from the official website of Microsoft. Once you’ve downloaded the Microsoft Visual C++ Feature Pack Redistributable Package, install it and then check if the error is now fixed.

Option 2 – Try to install OpenSSL

If you encounter the same error message but it points out that the LIBEAY32.DLL file is missing, then you have to install OpenSSL. In such a case, you will see the following error message:
“Ordinal not found. The Ordinal [Xxxx] could not be located in the Dynamic Link Library Libeay32.dll.”
 Make sure that when you install OpenSSL, you do it into the Windows system directory since the Libeay32.dll file is related to security.

Option 3 – Try to check Windows Updates

There are instances when Microsoft rolls out the framework and related updates via Windows Updates. It could be that an update related to DLL is still pending which is why you need to check Windows Updates. To do so, go to Settings > Update and Security and from there check if there is any pending update. If there is, you need to install that update and then restart your computer if needed.
Read More
Fix volsnap.sys failed BSOD Error in Windows
The Volsnap.sys is a Windows operating system file that is related to the Volume Shadow Copy Service or VSS. It is known to cause a Blue Screen of Death error. The main cause of the Volsnap.sys Blue Screen errors include conflicts with the RAM, issues with the hard disk, incompatible firmware, corrupted drivers, malware infection, and many more. Despite its many possible causes, its fixes are quite straightforward so won’t have any problem following them. The Blue Screen errors that are related to the Volsnap.sys file are:
  • KMODE EXCEPTION NOT HANDLED
  • PAGE FAULT IN A NONPAGED AREA
  • SYSTEM THREAD EXCEPTION NOT HANDLED
  • IRQL NOT LESS OR EQUAL
You might want to try performing System Restore as it could resolve Blue Screen errors like the ones related to the Volsnap.sys before you proceed with the troubleshooting tips given below. To run System Restore, follow these steps:
  • Tap the Win + R keys to open the Run dialog box.
  • After that, type in “sysdm.cpl” in the field and tap Enter.
  • Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
  • After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.
If System Restore didn’t help in fixing the Blue Screen error, now’s the time for you to resort to the troubleshooting tips provided below but before you get started, make sure that you create a System Restore point first.

Option 1 – Check if the Volume Shadow Copy service is running and restart it

The first thing you need to do is check if the Volume Shadow Copy service. To do that, refer to the following steps:
  • Click on Start and type “cmd” and right-click on Command Prompt from the search results.
  • Then select the “Run as administrator” option to open Command Prompt with admin privileges.
  • After that, type “net stop sdrsvc” and hit Enter to execute the command in stopping the Volume Shadow Copy service.
  • Next, type the “net start sdrsvc” command and hit Enter to start the service again.
Note: You can also restart the service using the Windows Services Manager.
  • In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “services.msc” in the field and hit Enter to open the Services Manager.
  • From there, look for the Volume Shadow Service (sdrsv) from the list of services. Its Startup type should be set to Manual by default.
  • Restart the service and if you don’t encounter any error while you turn it on, re-run the backup service and see if the backup process runs successfully.

Option 2 – Try checking the Memory for the Errors using Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the Volsnap.sys Blue Screen error by checking and automatically fixing any memory-based issues. To run it, refer to these steps:
  • Tap the Win + R keys to open Run and type mdsched.exe and hit Enter to open the Windows Memory Diagnostic Tool.
  • After that, it will give two options such as:
    • Restart now and check for problems (Recommended)
    • Check for problems the next time I start my computer
  • Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.
Note: After you select your preferred option, your computer will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 3 – Try to update or rollback your device drivers

If the first option didn’t work for you, then it’s time to either update or rollback the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.
  • Open the Devices Manager from the Win X Menu.
  • Then go to the section of IDE ATA/ATAPI controllers as well as Storage Controllers and right-click on them to open the Properties.
  • After that, switch to the Driver tab and click on the Uninstall Device button.
  • Follow the screen option to completely uninstall it.
  • Finally, restart your computer. It will just reinstall the device drivers automatically.
Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 4 – Try to run the CHKDSK utility

Running the CHKDSK utility might also help you resolve the Volsnap.sys Blue Screen error. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.
  • Open Command Prompt with admin privileges.
  • After opening Command Prompt, execute the following command and hit Enter:
chkdsk /f /r
  • Wait for the process to be completed and then restart your computer.

Option 5 – Run the System File Checker Scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. 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
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.
  • Restart your computer.

Option 6 – 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 Volsnap.sys. 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.
Read More
Software Licensing Service 0xC004F009 Error
A copy of Windows gets into a grace period when it is installed on a computer which means that you can use your Windows computer without any constraints on its feature. However, if you suddenly encounter an error code 0xC004F009 then this means that the grace period has already expired. In such cases, you will see the following error message on your screen:
“Error Code 0xC004F009, The Software Licensing Service reported that the grace period expired.”
One of the possible causes of this error is that it could be that the grace period has already expired way before the system was activated which is a result of which the system is in the Notifications state at this moment. The error code 0xC004F009 has something to do with MAK-enabled computers in an enterprise when it comes to Volume Licensing. One of the reasons that this error pops up is due to the possibility that the computer was not activated yet even when it was already connected to the Enterprise. Another most likely cause of the error is when the system was never connected with the Enterprise at all and the given grace period has expired before your computer system is activated. Whatever the real cause of this error, this post will guide you in fixing it. Just refer to the instructions given below to fix it.

Option 1 – Try activating Windows using the command-line tool

  • First, you need to obtain your MAK key from the IT administrator.
  • Once you have it, tap the Win + R keys on your keyboard and then type “cmd” in the field and hit Enter to open an elevated Command Prompt.
  • After that, type this command and hit Enter to install the product key or replace the existing one: Slmgr.vbs –ipk <your mak key>
  • Next, type another command and hit Enter: slmgr.vbs –ato
  • Once you’ve executed the given commands, Windows should be activated after it connects to Microsoft servers and then gives it some time and try to check if error code 0xC004F009 is now fixed or not.

Option 2 – Try activating Windows using your mobile phone

Activating Windows 10 can also be done using your phone. Just note that you have to call Microsoft to do so.
  • In the Start Search box, type in “Slui 4” and tap Enter.
  • Next, select your country and click on Next.
  • Keep the window open and call the toll-free number of the country you’re from.
  • Afterward, a confirmation ID should be given by the automated system which you must take a note of.
  • Finally, in the box on the window, type in the confirmation ID and click on the Activate button. That should do it.

Option 3 – Try to prolong the grace period

On the other hand, it is also possible for you to prolong the grace period but you might have to get another genuine Windows key for that. Before you proceed, you need to create a System Restore point first afterwards, refer to the steps given below to increase the grace period of the Software Licensing Service on your Windows 10 computer.
  • Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field then hit Enter to open the Registry Editor.
  • After that, navigate to this registry key: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionSetupOOBEmediabootinstall
  • Next, change the value of the “mediabootinstall” key to “0”.
  • Now open Command Prompt with admin privileges and then type this command and hit Enter: slmgr –rearm
  • The command you just entered will add another grace period to your system activation. After that, you have to obtain a new key and then activate Windows.

Option 4 – Try running the Windows 10 Activation Troubleshooter

You can also try to run the Windows 10 Activation troubleshooter to help resolve the error code 0xC004F009.
  • Go to Settings and then select Activation.
  • After that, click on the Windows Activation and then troubleshoot. This will help you address most of the commonly found activation issues in Windows devices.
Read More
Could not connect to the System Event
Could not connect to the System Event explanation: Although logging into a Windows 10 computer may seem like a simple process, it’s actually not since the Windows operating system has built a mechanism in a way that any third party or malware intervention would not compromise access to the system. This mechanism is supported by numerous services, functions, and DLL files. And Microsoft has been taking this security to a whole new level with the introduction of Windows Hello. Recently, a number of users reported getting the “Windows could not connect to the System Event Notification Service service. Please consult your system administrator” error when logging into their computers. While some users also reported that although they can log in, they encounter the same error message from the Notification area. There are several options you can check out to resolve the error. You have to check the status of several Windows Services and make sure that they are running. You also have to reset Winsock as well as run the System File Checker scan.

Option 1 – Check for certain Windows Services

  • First, you need to tap the Win + R keys on your keyboard to open the Run dialog box.
  • Next, type “services.msc” in the field and click OK or tap Enter to open the Windows Services Manager.
  • After that, you will see a list of services and from there, look for the following Windows Services:
    • DHCP Client
    • System Event Notification Service
    • Windows Font Cache Service
  • Now make sure that the Startup Type of each service is started and running.

Option 2 – Try resetting the Winsock drivers

  • In the Start Search, type “command prompt” and right-click on Command Prompt from the search results, and then select the “Run as administrator” option.
  • After opening Command Prompt, execute this command: netsh winsock reset
Note: If you are using IPv4, execute the “netsh int ipv4 reset” instead. On the other hand, if you are using IPv6, execute the “netsh int ipv6 reset
  • Now exit Command Prompt and see if the error is now fixed.

Option 3 – Try running System File Checker or SFC scan

You could also run System File Checker or SFC scan to fix the BSOD error. It 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
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.
  • Reboot your PC.
Read More
DisplayLink in Windows 10 is not working
This post will guide you in what to do if the DisplayLink in Windows 10 is not working. There are several users who reported that their DisplayLink device has stopped working with the Windows 20 Anniversary or the Creators update all of a sudden. According to users, this issue occurs right after they finish installing a big Windows Update like the Anniversary Update or the Creators Update or right when the DisplayLink driver is updated using Windows Update. DisplayLink is a graphics transport technology that allows users to connect to any computer that supports USB or Wi-Fi. Aside from that, it is also an excellent universal docking solution to any platform which makes it a great solution for enabling multiple displays. Thus, it can be quite annoying when DisplayLink suddenly stops working. There really is no actual error message when it happens. The only telltale sign is that all the devices that use the DisplayLink technology will also stop functioning. There could be tons of reasons why DisplayLink stopped working. It could be due to an incompatible driver, or the DisplayLink driver itself is corrupted or is connected to a USB 2.0 port. In addition, the problem could also be due to the Nvidia Share (ShadowPlay) that conflicts with DisplayLink or that the Universal Serial Bus is broken. To resolve the issue, refer to the following options laid out below.

Option 1 – Run the Hardware and Devices troubleshooter

As you know, Windows comes with a built-in tool that you can use to troubleshoot the problem with DisplayLink. You can find it in Settings > Update & Security > Troubleshoot. For further instructions, follow these steps:
  • The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
  • After opening Settings, look for the Update and Security option and select it.
  • From there, go to the Troubleshoot option located on the left-hand side of the list.
  • Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
  • After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

Option 2 – Try to uninstall DisplayLink and reconnect the docking station

If the Hardware and Device troubleshooter is of no help, you can try uninstalling DisplayLink and reconnecting the docking station. To do so, follow these steps:
  • Disconnect the docking station or any other device that uses DisplayLink.
  • Tap the Win + R keys to open the Run dialog box.
  • Then type “cpl” and hit Enter to open Programs and Features.
  • From there, look for DisplayLink, right-click on it and click Uninstall.
  • After that, follow the next on-screen instructions that appear on your screen to completely remove DisplayLink from your computer.
  • Once you’ve uninstalled DisplayLink, click this link to download and install DisplayLink again.
  • Now reconnect the docking station as well as other devices that use DisplayLink and follow the next on-screen instructions to reinstall the required drivers in your computer.
  • Restart your computer and then check if DisplayLink is now working fine or not.

Option 3 – Try using a USB 3.0 port

If you are experiencing this issue with DisplayLink with a monitor that you’re trying to connect using DisplayLink, then you have to make sure that you are using a USB 3.0 port. Based on some reports, there are certain monitors that will not work with DisplayLink while connected to a USB 2.0 port since they have insufficient power to run the monitor. Like pointed out earlier, the problem with DisplayLink might have something to do with the Nvidia ShadowPlay. This streaming feature was often reported to crash the DisplayLink monitors which is why you might want to try disabling it for a while to check if it’s really true. Once you’ve disabled Nvidia ShadowPlay, restart your computer and check if your DisplayLink monitor now works.

Option 5 – Reinstall the Universal Serial Bus controller

You can also reinstall the Universal Serial Bus controller to fix DisplayLink since a malfunctioning USB port can sometimes cause issues with DisplayLink.
  • Tap the Win + R keys to open the Run dialog box.
  • Then type “msc” in the field and hit Enter to open the Device Manager.
  • From there, look for the Universal Serial Bus controllers and expand its drop-down menu.
  • Next, right-click on every Host Controller and then click on Uninstall Device.
  • After uninstalling every entry, restart your computer to force your system to reinstall the drivers you’ve just uninstalled.
  • Once your computer has rebooted, wait until the drivers are reinstalled and then try opening DisplayLink again.

Option 5 – Reinstall the Universal Serial Bus controller

You can also try to perform a System Restore as it can also help you fix DisplayLink. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.
  • Tap the Win + R keys to open the Run dialog box.
  • After that, type in “sysdm.cpl” in the field and tap Enter.
  • Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
  • After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.
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