Update cannot currently check for updates

Following a two-year investigation by the California Department of Fair Employment and Housing, the state has filed a lawsuit against Activision Blizzard for fostering a "frat boy" culture in which female employees are allegedly subjected to unequal pay and sexual harassment. As reported by Bloomberg, Activision Blizzard is being accused by the state of California of discriminating against female employees at nearly all levels of employment, including in regards to compensation, promotion, assignments, and termination. The state alleges Activision Blizzard’s leadership has failed to address any of these outstanding issues or prevent them from occurring within the workplace. You can read the full details of the lawsuit here. The suit, filed Tuesday in the Los Angeles Superior Court, says Activision Blizzard, which is made up of about 20 percent women, assigns women, and women of color, to "lower paid and lower opportunity levels" with lower starting pay for similar work as their male counterparts. The documents also accuse Activision Blizzard of fostering a "pervasive 'frat boy' workplace culture in the office. Male employees are said to drink "copious amounts of alcohol" as they make their way through cubicles and "often engage in inappropriate behavior toward female employees." Male employees are said to come to work hungover, play video games during work "while delegating their responsibilities to female employees, engage in banter about their sexual encounters, talk openly about female bodies, and joke about rape." The lawsuit also cites one particular incident where a female employee, who was already subjected to intense sexual harassment at the company, committed suicide during a work trip with a male supervisor who allegedly brought inappropriate, sexual items with him on the trip. The lawsuit is asking for an injunction that will force Activision Blizzard to comply with workplace protections, as well as deliver unpaid wages, pay adjustments, back pay, and lost wages and benefits for female employees.

An Activision Blizzard spokesperson sent the following statement in response to the allegations:

We value diversity and strive to foster a workplace that offers inclusivity for everyone. There is no place in our company or industry, or any industry, for sexual misconduct or harassment of any kind. We take every allegation seriously and investigate all claims. In cases related to misconduct, the action was taken to address the issue. The DFEH includes distorted, and in many cases false, descriptions of Blizzard’s past. We have been extremely cooperative with the DFEH throughout their investigation, including providing them with extensive data and ample documentation, but they refused to inform us what issues they perceived. They were required by law to adequately investigate and to have good faith discussions with us to better understand and to resolve any claims or concerns before going to litigation, but they failed to do so. Instead, they rushed to file an inaccurate complaint, as we will demonstrate in court. We are sickened by the reprehensible conduct of the DFEH to drag into the complaint the tragic suicide of an employee whose passing has no bearing whatsoever on this case and with no regard for her grieving family. While we find this behavior to be disgraceful and unprofessional, it is, unfortunately, an example of how they have conducted themselves throughout the course of their investigation. It is this type of irresponsible behavior from unaccountable State bureaucrats that are driving many of the State’s best businesses out of California. The picture the DFEH paints is not the Blizzard workplace of today. Over the past several years and continuing since the initial investigation started, we’ve made significant changes to address company culture and reflect more diversity within our leadership teams. We’ve updated our Code of Conduct to emphasize a strict non-retaliation focus, amplified internal programs and channels for employees to report violations, including the “ASK List” with a confidential integrity hotline, and introduced an Employee Relations team dedicated to investigating employee concerns. We have strengthened our commitment to diversity, equity, and inclusion and combined our Employee Networks at a global level, to provide additional support. Employees must also undergo regular anti-harassment training and have done so for many years. We put tremendous effort into creating fair and rewarding compensation packages and policies that reflect our culture and business, and we strive to pay all employees fairly for equal or substantially similar work. We take a variety of proactive steps to ensure that pay is driven by non-discriminatory factors. For example, we reward and compensate employees based on their performance, and we conduct extensive anti-discrimination training including for those who are part of the compensation process. We are confident in our ability to demonstrate our practices as an equal opportunity employer that fosters a supportive, diverse, and inclusive workplace for our people, and we are committed to continuing this effort in the years to come. It is a shame that the DFEH did not want to engage with us on what they thought they were seeing in their investigation.

Conclusion

We will see how things work out, but I am not too optimistic for Activision Blizzard, truth to be told these reports are really bringing up some disturbing news on the sunlight. I just hope that all responsible will be brought to justice.

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.

If you have received a BSOD error message that says, “Tcpip.sys”, read on as this post will show you how you can fix the problem. The “Tcpip.sys” means Transmission Control Protocol over Internet Protocol. It is a library of a set of rules that are used to interconnect different devices all over the internet. The Tcpip.sys file is a driver and if a BSOD error message includes this one, it could only mean that the driver file is corrupted or incompatible with your system or there are some conflicting programs installed in your computer. To fix this error, you can try the following workarounds. Make sure to carefully follow each one of them.

Option 1 – Check for conflicting or incompatible programs by putting your PC in a Clean Boot state

As mentioned, the “tcpip.sys” BSOD error might be caused by some problematic programs that clash with your existing operating system. Several users reported that numerous programs that are supposedly designed to enhance computer performance are causing conflict in the system instead. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.

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

After putting your PC in a Clean Boot State, try creating a system restore point and see if the problem still occurs. Clean Boot troubleshooting is designed to help you isolate the problem. For you to execute a clean boot troubleshooting, you must do a couple of actions (the steps are given above) and then restart your PC after every action. You might have to disable one third-party app after the other to really isolate the issue. And once you’ve narrowed down the problem, you can either disable the third-party app that’s causing the problem or remove it. Note that you must switch your PC back into the Normal Startup mode after you’re done troubleshooting the problem. Here’s how you can do it:

• From the “Start” menu, go to System Configuration.
• After that, switch to the General tab and click the option for “Normal Startup”.
• Next, go to the Services tab and clear the checkbox for “Hide all Microsoft services”.
• Then find and click “Enable all” and if prompted, you have to confirm.
• Afterward, go to the Task Manager and enable all the Startup programs and confirm the action.
• Restart your PC when prompted.

Option 2 – Disabling Antivirus Software

There are cases when the “tcpip.sys” BSOD error is caused by the antivirus program installed in your computer that’s blocking some essential operations. Because of this, the operating system fails which throws up the BSOD error. As you know, the antivirus program is designed to protect the computer and monitor every action in the system. However, there are instances when the antivirus program gives false positives and shuts down some modules even if it’s harmless. So this could be the case for the “tcpip.sys” error. To verify if the problem is indeed caused by the antivirus program in your computer, you need to temporarily disable it. After you’ve disabled it, restart your PC and then check if the problem’s fixed or not.

Option 3 – Try to update all your Drivers

From time to time, drivers get corrupted or outdated so it’s no surprise that they conflict with the operating system and cause errors like the “tcpip.sys” BSOD error. To fix the problem, you need to update all your drivers especially the network driver since the “tcpip.sys” error is closely related to this driver. Follow the steps below to update your 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. If you see a red or yellow sign that shows up against the driver, right-click on the driver’s name and select “Update Driver Software” or “Uninstall”. 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.
• Restart your PC.

Note: You also have the option to go directly to the website of your graphics card manufacturer and check if there’s a new update – if there is, download it. After that, you could also check if there’s a new update of the game you’re getting the issue of the black bar.

As you know, the Windows Media Creation Tool is a great utility in Windows that helps lots of users in installing Windows on their PCs. However, just like any other program in Windows, it also experiences a couple of issues every now and then. So in this post, you will be guided on how you can resolve a particular issue in the Media Creation Tool which is the error 0x80042405-0xA001A. You can encounter this error while creating a USB installation media used in installing Windows 10. When getting this kind of error in the Windows Media Creation Tool, you will see the following error message on your screen:

“We’re not sure what happened, but we’re unable to run this tool on your PC, Error code 0x80042405 – 0xA001A”

The error 0x80042405 – 0xA001A occurs while creating a bootable USB installation drive. This is a common error faced by many users and it has something to do with the USB hardware. To get this issue fixed, here are some suggestions you could check out.

Option 1 – Try to reformat the USB drive

Reformatting your USB drive might help in fixing error 0x80042405 – 0xA001A.

• Open This PC and right-click your USB drive from there then select Format.
• Next, select FAT32 as the drive type and uncheck the “Quick Format” option.
• After that, try to run the Windows Media Creation Tool again and check if the error is fixed or not. But hopefully, it should work since formatting the drive as FAT32 will give the driver a proper type and would resolve any minor issues in the drive.

Option 2 – Copy the Windows Media Creation Tool to the USB drive

If the first option didn’t work, you might want to copy the latest version of the Media Creation Tool to the USB drive. After you do that, you can run it from inside the drive. This is actually a working fix and can definitely get the USB drive to run with Windows inside it so it should resolve the error 0x80042405 – 0xA001A on the Windows Media Creation Tool.

Option 3 – Run CHKDSK to check the drive for errors

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. This error check utility can help with several issues in the system including the “Diskpart failed to clear disk attributes” error.

• Tap the Win + S keys to open the Search box.
• Then type “command prompt” in the field and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
• After opening an elevated command prompt, copy and paste the following command and hit Enter:

CHKDSK [volume [[path] filename]] [/F] [/V] [/R] [/X] [/C] [: size]]

Note: In the command given above, “[/F]” will try to fix the system errors while “[/R]” will be the one to fix the bad sectors.

• Now if you are prompted to run CHKDSK after your reboot your PC, just tap Y and reboot your PC.
• If CHKDSK is not able to find any errors, tap the Win + E keys and navigate the access window. From there, right-click on the concerned drive and click on Properties.
• After opening Properties, click on the tab Tools and then click on the “Check” button under the Error-checking section.
• Wait until the process is completed and then restart your computer.

Option 4 – Try checking the hardware components

On the other hand, it is also possible that the issue has something to do with a hardware problem and so you need to check the hardware components on your computer to determine that.

Error 1753 - What is it?

Error 1753 is an RPC endpoint mapper error code. This code is typically displayed as "EPT_S_NOT_REGISTERED" or sometimes as the hexadecimal value 0x6D9.  Error 1735 indicates that there are no more endpoints available from the endpoint mapper. To understand this better, basically, RPC is an inter-process communication (IPC) method. This is used by clients and servers for communication purposes. RPC is used by programs to execute programs on a server computer. The perfect example of this is Microsoft Outlook. You communicate with Microsoft Exchange Server using RPC. This enables you to send and receive emails. When you use Microsoft Outlook to send emails, your computer sends a message to the server computer in an obscure coding. The server responds to your computer with another message that contains the results of the executed program. This is all being carried at the backend of the running program. Integral to this is the endpoint. The endpoint includes the name, port, or a group of ports on a computer that is monitored by the server for incoming client requests. This is a network-specific address to be precise. The endpoint mapper is the part of the RPC subsystem that is responsible for dynamically assigning endpoints to the server. When this function fails it leads to error 1753 message display. It shows that RPC service is not available.

Solution

Error Causes

The error code 1753 indicating RPC endpoint mapper service failure is triggered due to multiple reasons. These include:

• Windows registry damage and corruption
• Malfunctioning of the hardware
• Spyware intrusion or viral infections
• Device driver conflicts

Further Information and Manual Repair

This error code may cause a great deal of inconvenience to execute programs that are dependent on the server. It can lower your productivity and performance. To avoid the hassle, it is advisable to repair the error 1753 immediately. The best way to resolve this error 1753 in seconds is to download Restoro. By using this repair tool, you can fix the error right away for free without paying hundreds of dollars to a professional expert. Restoro is a new and innovative PC fixer integrated with an automated algorithm and intuitive technology that enables users to sit back and relax while Restoro runs on the system and detects all PC-related issues in the shortest time. In just a few clicks you can resolve even the mightiest PC issues like the error code 1753 RPC endpoint mapper problem and resume back to the program in no time.

Why Restoro

It is efficient and user-friendly. Restoro can be used by users of all levels so even if this is your first experience using a repair tool, you don’t have to worry. To operate it, you don’t have to be a computer programmer or have sound technical expertise. It is simple and very easy to use. The layout is simple and neat complimented nicely with easy navigation and a sophisticated user interface. Restoro is a high and multi-functional error tool embedded with powerful, performance-driven, and value-adding utilities, all in one. So, whether the error code 1753 is triggered due to a viral infection on your system or registry corruption, you don’t have to look for different tools to resolve the error, simply run Restoro to fix the issue right away. Restoro includes a dynamic registry cleaner that detects all registry issues and wipes out the clutter from the hard disk like junk files, internet history, and invalid entries which is by the way the number cause for registry corruption leading to error 1753. It clears up disk space and RAM and repairs the misconfigured system files and corrupt registry in seconds thus resolving error 1753. Restoro also functions as a system optimizer thus boosting the speed and performance of your PC massively and reducing boot time. In addition to this, it also has a backup feature.  This tool is embedded for safety purposes. This feature enables you to create backup files on your PC before you start system repair. This helps you recover data in the event of data loss during system repair. To get started:

• Click here to download and install Restoro on your system
• After installation, run it to scan for errors like 1753
• Now press the repair tab to resolve

According to some reports, using RDP or Remote Desktop Protocol on recent versions of Windows 10 results in a black screen. One encounters this issue is when using the Remote Desktop Connection feature on Windows 10. The real causes of this black screen are either the display drivers or some misconfiguration with the Remote Desktop Connection utility. In most cases, the Remote Desktop in Windows 10 will display a black screen and then disconnects afterward. To fix this kind of issue on your Remote Desktop, there are two suggestions you need to check out. First, you can try to disable the persistent bitmap caching, and then you can also try to update your display driver. Follow the given options below for more troubleshooting instructions.

Option 1 – Try to disable Persistent Bitmap caching

The first thing you can do to resolve the black screen issue with the remote desktop is to disable the persistent bitmap caching. All you have to do is follow these steps:

• First, open the Remote Desktop Connection client.
• Next, click on the Show Options button to configure the Remote Desktop Connection.
• After that, go to the Experience tab and uncheck the Persistent bitmap caching option.
• Once done, you should now be able to connect to the remote computer without the black screen.

Option 2 – Try to update or rollback the Graphics driver

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

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. From there, look for the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

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

Option 3 – Try performing a System Restore

You might also want to perform a System Restore that might help you in fixing the error. 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.

If you suddenly encounter Error 0x80000003 while trying to execute a random file then read on as this post will show you how you can fix such an error. Obviously, it mostly happens on executable files or .exe files and is most likely caused by the conflict in the execution of some registry files or it could also be caused by missing drivers or it could also be due to some incompatible hardware which is why you’re unable to run the executable file. When you encounter this error, you will see the following error message on your screen:

“The exception Breakpoint, A breakpoint has been reached, (0x80000003) occurred in the application.”

As you can tell, the Windows Executive STATUS message is a warning and if you are given an option, you must select one of the options from the message box. So if you are running the application in an end-user environment rather than in a development environment, you must contact the supplier of the running application regarding this error message since this shouldn’t be happening when a finished program is running. Before you get started executing the troubleshooting guide given below, make sure that you create a System Restore Point first since you will be dealing with some critical settings in Windows. Having done this, proceed to the options provided below.

Option 1 – Try to run the CHKDSK utility

Running the CHKDSK utility might also help you resolve Error 0x80000003. 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 2 – Try to run a System File Checker scan

You can also try to run a System File Checker or SFC scan in order to scan your computer for corrupted files that might be the cause behind the Error 0x80000003. Once it finds any corrupted system files, it will automatically fix them. To run System File Checker, here’s what you have to do:

• 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 after the scan is completed.

Option 3 – Perform a Clean Boot

There are some instances that some conflicting programs installed in your computer might be the one that’s causing the Error 0x80000003 to appear. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.

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

Option 4 – Run the Memory Diagnostic Tool to check for Memory leaks

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

Option 5 – Try contacting the developer

If you find that you’re getting Error 0x80000003 on only one particular application, then you can try to contact the developer of the software that’s throwing up this error. All you have to do is search the web for the official support channel of the software and discuss the error from there.

As in previous Windows 10, inside Windows 11 also when you press the ALT + TAB key combination you will get a preview of all running applications along with all Browser tabs so you can go through them and pick the one you want to switch to. Alto, I personally am a big fan of alt-tabbing, I must admit that I am not a big fan of having multiple browsers tabs on screen when I do press key combo. Luckily there is a very easy way to turn this feature off. Turning browsers tabs thumbnails off

1. Press ⊞ WINDOWS + I to open settings
2. Click on System in the sidebar
3. Scroll down and select Multitasking
4. Find Alt + Tab section and click on the drop-down menu
5. Pick Open Windows Only
6. Close settings

Now when you press the ALT + TAB key combination you will still see your browser but only an active tab in it instead of all tabs as different preview thumbnails.

Upgrading your Windows computer may not always go as expected as you could end up getting some error messages along the way. One of the error messages you can encounter is the “STOP 0XC000021A or STATUS_SYSTEM_PROCESS_TERMINATED” error. This error indicates that is some security issue within the Windows operating system. It could be that the system files have an issue and they have been modified incorrectly. Although this does not necessarily mean that malware is behind the modification, one of the applications you installed recently might have something to do with the problem. The application might have modified or corrupted some of the core system files. When you encounter this error, you will see a blue screen along with the following error message:

“Your PC ran into a problem and needs to restart. We’re just collecting some error info, and then we’ll restart for you. (0% complete) If you’d like to know more, you can search online later for this error: 0xc000021a”

This error pops up when a user-mode subsystem like the WinLogon or the Client Server Run-Time Subsystem or CSRSS has been compromised fatally and security can no longer be guaranteed in the system. Thus, the operating system switches to kernel mode, and Windows won’t be able to run without the WinLogon or the Client Server Run-Time Subsystem. This is why it’s one of the few cases where the failure of a user-mode service can shut down the system. To resolve the issue, here are some fixes that might help.

Option 1 – Uninstall programs you installed lately

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

Option 2 – Perform System Restore

Performing System Restore can also help you fix the “STOP 0XC000021A or STATUS_SYSTEM_PROCESS_TERMINATED” error. 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.

Option 3 – Run the System File Checker or SFC 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 to good system files that might be the cause why you’re getting the “STOP 0XC000021A or STATUS_SYSTEM_PROCESS_TERMINATED” error. 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.

Option 4 – Rebuild the BCD and fix MBR

Rebuilding the BCD can help you in fixing the “STOP 0XC000021A or STATUS_SYSTEM_PROCESS_TERMINATED” error.

• You can start by booting into the installation environment for Windows 10 from an installation media.
• After that, click on Repair your computer and on the blue screen, select Troubleshoot and then select the Advanced options menu.
• Next, select Command Prompt and type in the commands below one by one, and tap Enter right after you do so.
• exe /FixMbr
• exe /FixBoot
  • exe /RebuildBcd

The commands you entered should rebuild the BCD and repair MBR.

Option 5 – Run the CHKDSK utility

You can also run the Chkdsk utility to resolve the problem. 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 commands listed below, and don’t forget to hit Enter right after you type in each one of them.
• chkntfs /t
• chkntfs /t:10

You might be familiar with the Encryption File System or EFS algorithm if you rather keep your files and folders encrypted. Encryption File System is a built-in feature in Windows 10 which allows users to secure their important files. Although there is an alternative way for you to secure your data on your Windows 10 computer, you can’t ignore the fact that the main advantage of an Encryption File System over BitLocker is that the former can help you encrypt a particular folder rather than encrypting the whole hard drive partition. If you move a file inside a folder encrypted with the Encrypting File System it will automatically get encrypted. There are some users who like this feature but unsurprisingly, there are some that don’t. So if whether you want your files encrypted when you place them in an encrypted folder or if you want to keep it as it is, read on as to how you can do it either way. You can enable or disable automatic encryption of files moved to encrypted folders in Windows 10 using the Registry Editor or the Group Policy Editor. Before you proceed, make sure to create a System Restore Point first because the modifications you’re about to make in your computer might affect its overall functioning so if anything goes wrong, you can always undo the changes. Once you have that covered, refer to the options given below to enable or disable automatic encryption in Windows 10.

Option 1 – Enable or disable automatic encryption using Registry Editor

• Press the Win key + R key at the same time to open the Run dialog box.
• Then type “Regedit” in the field and press Enter to open the Registry Editor and if a User Account Control or UAC prompt appears, just click Yes to proceed.
• After opening the Registry Editor, navigate to this key location: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesExplorer
• Next, right-click on Explorer and select New > DWORD (32-bit) Value and then name the newly create DWORD to “NoEncryptOnMove” and press Enter to save it.
• After that, double click on the NoEncryptOnMove DWORD and set its value to the following preferences:
  • 1 – Disable Auto Encryption of files moved to encrypted folders.
  • 0 – Enable Auto Encryption of files moved to encrypted folders.

• Now close the Registry Editor and restart your computer to successfully apply the changes made.

Option 2 – Enable or disable automatic encryption using the Group Policy Editor

• Press the Win + R keys to open the Run box and type “gpedit.msc” in the field and press Enter to open the Group Policy Editor.
• After that, navigate to this path: Computer ConfigurationAdministrative TemplatesSystem
• Next, look for the “Do not automatically encrypt files moved to encrypted folders” option and double click on it to set the policy. From there, you will see the following description:

“This policy setting prevents File Explorer from encrypting files that are moved to an encrypted folder. If you enable this policy setting, File Explorer will not automatically encrypt files that are moved to an encrypted folder. If you disable or do not configure this policy setting, File Explorer automatically encrypts files that are moved to an encrypted folder. This setting applies only to files moved within a volume. When files are moved to other volumes, or if you create a new file in an encrypted folder, File Explorer encrypts those files automatically.”

• Now select one of the radio buttons below depending on your preference:
  • Not Configured or Disabled: Enable Auto Encrypt of files moved to EFS Encrypted folders.
  • Enabled: Disable Auto Encrypt of files moved to EFS Encrypted folders.
• Then click on the Apply and OK buttons to save the changes made.
• Exit the Group Policy Editor and restart your computer.