NVIDIA driver keeps crashing in Windows

If you suddenly encountered Error Code 0xc1900130 while trying to update your Windows 10 computer, read on for this post will help you fix the problem. This kind of Windows Update error may occur when the network connection between the Windows Update server and the client machine is interrupted and the install can’t continue since the instance hash was not found. In such cases, you will see the following error message in Settings:

“Failed install attempt – 0xc1900130”

Here are the technical details of the error:

“Error Code: 0XC1900130 Message: MOSETUP_E_INSTALL_HASH_MISSING Description: The install cannot continue because the instance hash was not found.”

If you are currently facing this problem when you tried to install a Feature Update, you might have to check your internet connection and then try to install the Windows Update again. However, if it didn’t work, then you can refer to each one of the given options below to fix the error.

Option 1 – Reset the Windows Update components

If by any chance that the second option didn’t work, resetting the Windows Update components could also help you resolve the problem. How? Refer to the following steps:

• Open Command Prompt with admin privileges.
• After that, type each one of the following commands and hit Enter after you key in one after the other.
  • net stop wuauserv
  • net stop cryptsvc
  • net stop bits
  • net stop msiserver

Note: The commands you entered will stop the Windows Update components such as Windows Update service, Cryptographic services, BITS, and MSI Installer.

• After disabling WU components, you need to rename both the SoftwareDistribution and Catroot2 folders. To do that, type each one of the following commands below, and don’t forget to hit Enter after you type one command after the other.
  • ren C:WindowsSoftwareDistribution SoftwareDistribution.old
  • ren C:WindowsSystem32catroot2 Catroot2.old
• Next, restart the services you’ve stopped by entering another series of commands. Don’t forget to hit Enter after you key in one command after the other.
  • net start wuauserv
  • net start cryptsvc
  • net start bits
  • net start msiserver
• Close Command Prompt and reboot your PC.

Option 2 – Try configuring the Windows Update-related Services

• Tap the Win + R keys to open the Run dialog box.
• Then type “cmd” in the field and tap Enter to open an elevated Command Prompt.
• Next, execute the following commands. Note that you have to type and enter each command one after the other.
  • SC config wuauserv start= auto
  • SC config bits start= auto
  • SC config cryptsvc start= auto
  • SC config trustedinstaller start= auto
• The commands you executed will make sure that the Windows Update-related services are available. Once it’s done, restart your computer and see if the Windows Update error is now fixed.

Option 3 – Try downloading and installing the Windows Updates manually

Windows Upgrade Error Code 0xc1900130 might be due to a Windows Update that has failed. So if it is not a feature update and only a cumulative update, you can download the Windows Update and install it manually. But first, you need to find out which update has failed, and to do so, refer to the following steps:

• Go to Settings and from there go to Update and Security > View Update History.
• Next, check which particular update has failed. Note that Updates that have failed to install will be displayed under the Status column which has a label of “Failed”.
• After that, go to the Microsoft Download Center and look for that update using its KB number and once you find it, download and then install it manually.

Note: You can also use the Microsoft Update Catalog, a service from Microsoft that provides a list of software updates that can be distributed over a corporate network. With the help of this service, it can be easier for you to find Microsoft software updates, drivers as well as fixes.

Option 4 – Try to run the Windows Update troubleshooter

Windows 10 have various troubleshooters that can help you resolve many system issues. So if you’re dealing with Windows Update errors like Error Code 0xc1900130, you can run the Windows Update troubleshooter to resolve it. 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 5 – Try to flush the DNS cache

You could also try to flush the DNS cache as it might fix the problem. To do so, follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute the following command to flush the DNS cache

ipconfig /flushdns

• Next, restart your PC and check if the problem’s fixed.

Note: You might also check your internet connection or reboot your router or plug out and then plug in your Ethernet connection manually to verify the reliability of your internet connection since intermittent connection could also cause Windows Update errors like Error Code 0xc1900130.

Error 2738 - What is it?

Error 2738 is associated with the VBScript engine. VBScript is the abbreviation for Visual Basic Scripting. It is an Active Scripting programming language developed by Microsoft and modeled on Visual Basic. It is used with a fast interpreter in a large variety of Microsoft environments. Error 2738 indicates that the VBScript engine is not registered properly on your PC. It occurs when you try to install or uninstall VBScript-supported applications on your system. The error message is displayed in the following format:

"Error 2738. Could not access VBScript run time for custom action."

Solution

Error Causes

There are several reasons for the error 2738 message pop up. These include: Incorrect or corrupt registry entries on your system. These entries interfere with VBScript support in Windows thereby generating such error codes.

• Removal of McAfee Antivirus
• Windows registry values are not updated accurately during the uninstallation of McAfee Software
• The Visual Basic Script is registered in the registry under the local user instead of the local machine

No matter what the cause of the error may be, it is recommended that you resolve the issue immediately without any delay.

Further Information and Manual Repair

Here are some of the easy and proven DIY methods to repair error 2738 on your PC:

Method 1

If the error 2738 occurs because the VBScript is not registered correctly, then follow these steps to resolve.

1. Go to the start menu, open Run, and type RegEdit in the box and then press OK. This will open the Windows Registry Editor.
2. Now type KEY_LOCAL_MACHINESOFTWAREClassesCLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}InprocServer32, if the key does not have a data value of C:\Windows\System32\vbscript.dll then simply add it.
3. Now go to the All programs option and then Accessories.
4. Here right-click on Command Prompt and then ‘Run as Administrator’.
5. Now type egsvr32 vbscript.dll then press enter. After that type regsvr32 jscript.dll and then press enter.
6. Restart your PC to activate changes.

Method 2

Sometimes error 2738 may occur when you uninstall preinstalled MacAfee antivirus software on your system. Un-installation usually leaves some trace components in the registry. These components must be removed completely otherwise error codes like 2738 may keep occurring on your computer screen. In such an event, the best way to resolve it is to download the McAfee Consumer Product Removal utility from McAfee's official website. Save this file on your desktop. Double click the file and follow the steps to remove this software completely and successfully from your PC. Proper removal of the McAfee program will resolve error 2738 right away. But if the error still persists then try other methods illustrated below.

Method 3

Download Restoro to remove incorrect and corrupt registry entries on your system that may be interfering with VBScript support. Restoro is a new and easy-to-use PC Repair Tool deployed with an intuitive interface and a powerful registry cleaner. The registry cleaner removes all entries corrupting the registry, cleans it, and resumes it to its normal state. Click here to download Restoro.

It is a fact that Blue Screen of Death errors can give you a headache for you will have a hard time fixing it as it is one of the most difficult errors you can encounter on your Windows computer. One of these BSOD errors is the UNEXPECTED KERNEL MODE TRAP error. If you receive this kind of error then it means that the operating system was not able to catch a trap or an exception generated by the CPU. This BSOD error has an error code 0x00000007F and indicates that the Intel CPU generated a trap that the kernel failed to catch. One of the most likely causes is hardware failure due to faulty memory. Aside from this cause, you also have to track down other probable causes for this problem like corrupted system files, incompatible drivers or programs, faulty hardware, and even dusty components, and so on. To fix the UNEXPECTED KERNEL MODE TRAP BSOD error, here are some suggestions that might help.

Option 1 – Uninstall the programs you installed recently

Chances are, some programs that you just installed might be the one that’s causing the BSOD error. Thus, you need to uninstall the program to resolve the problem.

• In the search box, type in “control” and then click on Control Panel (desktop app) among the search results.
• After that, select Programs and Features from the list which will give you a list of all the programs installed on your computer.
• From there, look for the concerned program and select it and then uninstall it.

Note: If you have downloaded the app from the Windows Store, you can simply right-click on it from the application list and then uninstall it. In addition, you might also want to check the hardware components of your computer that might not support the operating system itself. You can disconnect all the external devices like USB drives, scanners, printers, etc., and then reboot your PC. After that, add the devices again one after the other and check if the BSOD error is now fixed or not. Moreover, you can also perform a clean boot to make things easier for you.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” checkbox and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” checkbox.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)

Option 2 – Update your device drivers

• Tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. Look for the device driver you and then select either “Update driver” or “Uninstall device”. And if you find any “Unknown device”, you need to update it as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• If you have chosen to uninstall the driver, follow the screen options to complete the process and then restart your PC.
• Connect the device and Scan for hardware changes – you can see this option under Device Manager > Action.

Option 3 – Use the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like UNEXPECTED KERNEL MODE TRAP. 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 4 – Run the Windows Memory Diagnostic tool

You can use the Memory Diagnostic tool in Windows to check RAM. Before you use this tool, make sure you save all your important work.

• Tap the Win + R keys to open the Run dialog box.
• Next, type in “mdsched.exe” in the field and hit Enter to open Memory Diagnostic.
• After that, the Windows Memory Diagnostic will give out two options such as:

1. Restart now and check for problems (recommended)
2. Check for problems the next time I start my computer

• Select any of the given options. After that, your computer will restart and check for memory-based issues upon the restart. If there are any issues, it will automatically them.

Option 5 – Disable Memory caching in the BIOS

You can also disable memory caching in the BIOS to fix the UNEXPECTED KERNEL MODE TRAP error.

• Open the BIOS Setup screen.
• Next, go to Advanced > Cache Memory and then disable it.
• Tap the F10 key to save the changes made and restart your computer.

Option 6 – Run System File Checker

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow
• Restart your computer once the scan is completed.

Option 7 – Clean your hardware components for dust

Cleaning your computer’s hardware components for dust might also help in resolving the UNEXPECTED KERNEL MODE TRAP error. Make sure to use a soft cloth in cleaning the hardware as well as a small blower. Moreover, ensure that you do not damage any parts with moisture or cause harm to any circuits while you’re at it.

Keeping your system updated is a must and Windows updates are definitely a great way to do that. These updates are essential since they provide important security and various fixes for bugs in your Windows 10 computer. However, there are plenty of instances when you encounter issues with Windows Updates and one of them is when the Windows Updates turn off automatically at random times. Some users reported that they saw a notification about Windows Updates being turned off. Note that the issue is not with the update itself since many users turned on the Windows Update and the system was properly updated. The issue is that the Windows Updates turned off all by itself. There could be several reasons why the Windows Updates turned off by themselves. It could be due to the antivirus program installed on your computer. Antivirus programs are known to cause issues with other programs, Windows updates components included. This can occur due to false positives as well as odd compatibility issues. Aside from antivirus programs, the Windows Update service itself could also be the root cause of the problem. There could be a corrupted file in the Windows Update folder or it could be that the Windows Update service wasn’t started properly. Any of these issues can be resolved by following the troubleshooting options given below. Make sure to follow each one of them carefully for better results.

Option 1 – Try to disable your antivirus program

Disabling the antivirus program or any security software installed in your computer is always a good idea you can try when the Windows Update process does not go smoothly. So before you try updating your computer again, make sure to disable the antivirus or security program and once the Windows Update is done, don’t forget to enable the antivirus program back again.

Option 2 – Try to make some changes in the Registry

• Tap the Wins key once and type in “command prompt” in the field.
• From the search results, right-click on Command Prompt and select the “Run as administrator” option to run it with admin privileges.
• Next, type the following command and tap Enter:

reg add "HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWindowsUpdateAuto Update" /v AUOptions /t REG_DWORD /d 0 /f

• After that, type the following command and hit Enter again:

sc config wuauserv start= auto

 The command you entered will set the Windows Update to auto so you should be good to go.

Option 3 – Try to reset the Windows Update components

If by any chance that the second option didn’t work, resetting the Windows Update components could also help you resolve the problem. How? Refer to the following steps:

• Open Command Prompt with admin privileges.
• After that, type each one of the following commands and hit Enter after you key in one after the other.
  • net stop wuauserv
  • net stop cryptsvc
  • net stop bits
  • net stop msiserver

Note: The commands you entered will stop the Windows Update components such as Windows Update service, Cryptographic services, BITS, and MSI Installer.

• After disabling WU components, you need to rename both the SoftwareDistribution and Catroot2 folders. To do that, type each one of the following commands below, and don’t forget to hit Enter after you type one command after the other.
  • ren C:WindowsSoftwareDistribution SoftwareDistribution.old
  • ren C:WindowsSystem32catroot2 Catroot2.old
• Next, restart the services you’ve stopped by entering another series of commands. Don’t forget to hit Enter after you key in one command after the other.
  • net start wuauserv
  • net start cryptsvc
  • net start bits
  • net start msiserver
• Close Command Prompt and reboot your PC.

Option 4 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter is one of the things you can first check out as it is known to automatically resolve any Windows Update errors. 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.

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.

22H2 update for Windows 11 will arrive later this year and although Microsoft is not releasing anything big there will be some interesting improvements and fixes. We take a look at some that caught our attention.

Phishing protection

One of the most interesting upcoming features is enhanced phishing protection. Microsoft Defender SmartScreen will be upgraded to alert users when they try to store passwords in plain text files and also if they accidentally type in a Microsoft account password on phishing sites.

"These enhancements will make Windows the world's first operating system with phishing safeguards built directly into the platform and shipped out of the box to help users stay productive and secure without having to learn to be their own IT department,"

Microsoft

File Explorer gets tabs, a modern sidebar, and contextual suggestions

Finally, Windows File explorer is getting tabs that will allow much easier management of folders and files inside it.

It is confirmed that Microsoft is also working on a new 'HOME' sidebar that should be modern in design and in features including OneDrive so you can find everything in one place.

Pinning of favorite files was also mentioned so you can easily pin favorites for quick access.

Full-screen widgets

Windows 11 has brought back widgets in a new way and from all the feedback users are loving them. Currently, you have a widget sidebar on the left part of the screen where you have your chosen store widgets but from the Microsoft teaser, we will have soon the option to have them in full screen.

If you are using a widget for reading news, blogs, etc. this feature will be very good since you will be able to use your whole screen for information and not just a part of it.

Suggested actions

Another new feature is 'suggested actions' which is going to be particularly useful in apps like Microsoft Teams. With this new feature, you can highlight a date in a Teams message and Windows will suggest actions.

For example, if you highlight a date, you'll see a recommendation to create an event in Microsoft Calendar for that day.

Error Code 0x8000ffff - What is it?

Error Code 0x8000ffff is an error that is often experienced while attempting to install updates on a Windows machine. It has been found in Windows 10, although the error has been present in the Windows operating systems dating back to Windows Vista.

Common symptoms include:

• Inability to download updates for the operating system
• Inability to successfully run updates for the operating system through to completion

There are several basic Windows tools that can be used to attempt to resolve Error Code 0x8000ffff on your machine. While some of these tools may be familiar for basic users, others may require advanced competency in order to be used correctly. If you are unsure of your ability to complete the methods listed below in order to resolve this error code on your system, you may need to get in touch with a computer repair technician who is competent in dealing with Windows Update repairs.

Solution

Error Causes

The most common cause of Error Code 0x8000ffff is that there is a problem within one of the system files or the registry entries on the computer. There are a number of reasons why a device could have an error in these places, from conflicting software commands to updates that were not installed correctly, to bugs within the system, to viruses or malware that have corrupted the necessary files.

Further Information and Manual Repair

There are several common ways that users can attempt to resolve the appearance of Error Code 0x8000ffff on their Windows devices. If you are not sure that you can follow these steps through to completion, you would be well advised to get in touch with a qualified computer repair technician to help you to finish out the repair process.

Here are the best methods to resolve Error Code 0x8000ffff on your Windows machine:

Method One:  Restart Your Computer

It may sound obvious, but one of the most effective ways to resolve Error Code 0x8000ffff on your machine is to simply reboot your computer. In some cases, the error shows up because there are processes that the system believes are still running when they really aren’t. Restarting your machine also allows your system to apply any previous changes that have been made and to mark any installations that have been undertaken as being complete.

Reattempt your update installations after you have restarted your computer to see if you are able to finish them out successfully.

Method Two:  Run the Windows Registry Repair Tool

The Windows Registry Repair tool is an asset that can make it easy for your system to scan for potential problems in the registry and notify you as to their status. In many cases, the Registry Repair tool can fix the problems that it finds all on its own, although in some cases, you may receive a message that states an error was found that could not be resolved through the program.

The simplest way to access the Windows Registry Repair tool is to do a search for it within the search bar in the Start menu. Once you begin to run the Registry Repair tool, it can take a while to complete its scan, so be prepared to wait for some time once you start it.

Once the tool has completed its scan of your system, it’s always a good idea to reboot your computer so that all of the changes that have been made to the system can be applied successfully to the operating system.

Method Three:  Run the Windows Fix It Tool

Another great tool to help in the resolution is the Windows Fix It tool. You can download it directly from the Microsoft website. Once you run it, it will complete a scan of your system to find any potential hang-ups and to attempt to resolve them. After you run the scan, it is a good idea to reboot your computer to allow all changes to be recognized and applied properly.

Method Four: Use An Automated Tool

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.

In case you don’t know, Windows contains a feedback mechanism that generates error reports from hardware and software problems. These reports are temporarily stored in the system and send them back to Microsoft so that it can find solutions to the reported problems and fix them in the upcoming updates.  However, as time goes by, these reports actually take a lot of space in your computer which is why end-users like you are free to delete them with the help of the new Free Up Space feature in Windows 10. As useful the Free Up Space feature may be, there are times when you won’t be able to use it for some reason which is why in this post, you will be guided on how to use alternative ways in deleting very large System queued Windows Error Reporting file, some of which may run in Gigabytes. Every time the Windows Error Reporting or WER sends out an error file and looks for a solution, the WER server at Microsoft sends out a solution instantly. And if the solution is under investigation or is unknown, then you will be notified about it right away and will be asked for more details. As mentioned, even though the Free Up Space feature in Settings will be able to clear the error reporting files, there are instances when it won’t be able to delete very large System queued Windows Error Reporting files. Alternatively, there is an option to delete these files using the Disk Cleanup Utility. Feel free to select which option you’d like to use to get rid of Windows Error Reporting Files.

Option 1 – Delete Windows Error Reporting Files via Settings

• Go to Settings.
• From there, go to System > Storage > Free Up Space and then click on it to launch it.
• Afterward, give it some time to populate all the files and folders. Once it’s done, select “System created Windows Error Reporting files” to mark its checkbox while leaving the other options unchecked.
• Next, click on the Remove files button to delete all the Windows Error Reporting files from your computer.

Option 2 – Manually delete the Windows Error Reporting Files

• Tap the Win + E keys to open File Explorer.
• Next, enable the Hidden Files view from the menu.
• Then go to C:/ProgramData/MicrosoftWindowsWER.
• From there, you will see various folders like LocalReportArchive, ReportArchive, ReportQueue, and Temp.
• Open each one of the aforementioned folders and delete the archive files. Note that these files will have names similar to “00c58c1f-b836-4703-9bcf-c699ca24d285”.

Note: If you are not able to delete any of these files, you have to take ownership of the folder. To do so, refer to these steps:

• Right-click on the folder and then select Properties.
• Next, click on the Edit button in the Properties window and click OK to confirm if you got a User Account Control elevation request.
• After that, select user/group from the permission windows or click on the Add button to add another user or group. It would be best if you add “Everyone” to give permission.
• Then check “Full Control” under the “Allow” column to assign full access rights control permissions.
• Now edit the permission to Full Control for “Everyone”.
• Click OK to save the changes made and then exit.

On the other hand, if you do not want to go through all these troubles in deleting the Windows Error Reporting files, you can just disable it especially if it already becomes a daily annoyance as the files generate every day and their sizes are mostly gigabytes. And besides, there are times when these files do not make it to the Microsoft WER server and end up only occupying a lot of space for nothing.

One of the most common hardware issues with any PC usually has something to do with the hard drive so if your hard drive experiences some errors, you could end up losing a lot of important information that’s stored in your computer. This is why Windows provided users with the CHKDSK utility which helps in looking for bad sectors on the drive. However, there are times when the CHKDSK utility could also face issues like the following error:

“Failed to transfer logged messages to the log event with status 50.”

According to security experts, this error is most likely due to the hard drive or RAM being in a “Read-only” state. It could also be due to some physical issues with the hard drive. On the other hand, it could be that the system is prevented from creating logs by some drive, service, or malware. To fix this error, you have to check if the hard disk is writable. You could also try to run the CHKDSK utility in Safe Mode or you could also check the physical status of your hard disk or external drive.

Option 1 – Check if the hard disk is writable

Although the CHKDSK utility checks for bad sectors in the hard drive, it also has to create logs of the result. And as states in the error message, the CHKDSK utility is not able to log the logged messages. This kind of error occurs when the log can’t be written to an installation disk. You can find the log in this location, “C:WindowsSystem32LogfilesSrtSrtTrail.txt”. Now you have to check if the drive writable by following these steps:

• Log in as administrator and right-click on the system drive.
• Select Properties and then go to the Security tab. Here, check if you are allowed to modify the drive. If not, click on Edit (as an administrator).
• Now edit the permissions for the SYSTEM and Administrators group. Note that these are the only default settings for these two groups or usernames.
• Then click on the Apply button save the changes made and exit.

Option 2 – Run the CHKDSK utility in Safe Mode

You could also try to run the CHKDSK utility in Safe Mode as this might solve the error.

• Boot your computer in Safe Mode.
• Next, open Command Prompt with admin privileges.
• Then type and enter this command to execute it: chkdsk c: /f /r
• Wait until the process is completed and boot your computer normally and then run the CHKDSK utility again and check if the “Failed to transfer logged messages to the log event with status 50” error is now fixed.

Option 3 – Try to check the hard disk or external drive physically

If the first two options didn’t work, you might want to check the physical status of your hard disk or external drive as the problem could root from there. You can try to tighten the wires that connect the hard disk to the motherboard. However, if it doesn’t help, you should seek out assistance from a hardware technician.

A few days ago we celebrated fixing of months-long PrintNightmare vulnerability by Microsoft, sadly a new bug and issue have been found. Firstly discovered Microsoft stated:

A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged file operations. An attacker who successfully exploited this vulnerability could run arbitrary code with SYSTEM privileges. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

A few days ago, Microsoft officially released a patch that was supposed to finally fix it. As you might recall this vulnerability was present for quite some time, Microsoft's solution after a long struggle was to elevate certain privileges to administrator account only and remove user accounts from managing printers. It complicated things a little bit but it was stated payoff was worth it. The new issue now is that on a system that already had accounts created and set, old accounts still can hijack the system, patch issues address only accounts that are created after the fix is administrated, old ones can still do whatever they want. Once again of course Microsoft has stated that until it is again resolved you should again disable the Print Spooler service as a temporary workaround.