
There are times when we delete a system files without meaning to on your Windows 10 computer. This happens a lot for users sometimes mistake a system file for a malware-laden file or junk file when it’s actually a system file from the System32 or SysWOW64 folder. In such cases, it could affect your computer. For instance, you might not be able to reboot your PC or open Settings.
If you have removed system files from any of these folders by accident and you desperately want to restore them, read on, as this post will guide you in resolving the problem. Restoring them isn’t actually hard, just make sure that you have system admin access.
The good thing is that there exists Windows Resource Protection which protects registry keys and folders and even critical system files. So if there are any detected changes to a protected system file, the modified file is restored from a cached copy located in the Windows folder. However, if the Windows Resource Protection program fails to restore these files, you need to check out the given fixes below.
To restore the system files you deleted, you can try running System File Checker or SFC scan. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:
The command will start a system scan which will take a few while before it finishes. Once it’s done, you could get the following results:
Aside from System File Checker, you can also run the DISM or Deployment Imaging and Servicing Management Tool as it could help in restoring the system files on your Windows 10 computer. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth” which could help you resolve the problem.
Running System Restore can also help you bring back the system files. 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.
Startup Repair, previously known as Automatic Repair, is an advanced tool in Windows that can help you diagnose various system issues, including this one. This tool will scan system files, configuration settings, registry settings, and so on in order to fix the problem on its own. To run Startup Repair, all you have to do is boot into the Advanced Startup Options and then go to Troubleshoot > Advanced option > Startup Repair and then run it. This will resolve the problem if you have deleted any system file that’s essential to your Windows 10 PC.
Note: Once you have access to the Advanced Startup options, you have to go to the setting which allows you to Reset your Windows 10 PC. All you have to do is select Troubleshoot > Reset this PC to reach the following screen
Afterward, select either the “Keep my files” option and then proceed to the next on-screen instructions that follow to reset your Windows 10 computer without losing your files.
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts] "Segoe UI (TrueType)"="" "Segoe UI Bold (TrueType)"="" "Segoe UI Bold Italic (TrueType)"="" "Segoe UI Italic (TrueType)"="" "Segoe UI Light (TrueType)"="" "Segoe UI Semibold (TrueType)"="" "Segoe UI Symbol (TrueType)"="" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes] "Segoe UI"="NEW_FONT"Where in "Segoe UI"="NEW_FONT" instead of NEW_FONT you need to write the exact name of the font that you wish to use as a system font. Once you have replaced the default system font with your desired one, go to File and save as, from file type drop-down menu, choose all files and save this file as .REG type giving it whatever name you wish. When the file is saved, close notepad, right-click on the saved file and choose the merge option. Confirm with YES and click on OK. Reboot your system and your Windows will now use the font of your choice as its default system font.
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts] "Segoe UI (TrueType)"="segoeui.ttf" "Segoe UI Black (TrueType)"="seguibl.ttf" "Segoe UI Black Italic (TrueType)"="seguibli.ttf" "Segoe UI Bold (TrueType)"="segoeuib.ttf" "Segoe UI Bold Italic (TrueType)"="segoeuiz.ttf" "Segoe UI Emoji (TrueType)"="seguiemj.ttf" "Segoe UI Historic (TrueType)"="seguihis.ttf" "Segoe UI Italic (TrueType)"="segoeuii.ttf" "Segoe UI Light (TrueType)"="segoeuil.ttf" "Segoe UI Light Italic (TrueType)"="seguili.ttf" "Segoe UI Semibold (TrueType)"="seguisb.ttf" "Segoe UI Semibold Italic (TrueType)"="seguisbi.ttf" "Segoe UI Semilight (TrueType)"="segoeuisl.ttf" "Segoe UI Semilight Italic (TrueType)"="seguisli.ttf" "Segoe UI Symbol (TrueType)"="seguisym.ttf" "Segoe MDL2 Assets (TrueType)"="segmdl2.ttf" "Segoe Print (TrueType)"="segoepr.ttf" "Segoe Print Bold (TrueType)"="segoeprb.ttf" "Segoe Script (TrueType)"="segoesc.ttf" "Segoe Script Bold (TrueType)"="segoescb.ttf" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes] "Segoe UI"=-Reboot your system and your Windows will now revert the font of your choice as its default system font.
Get-ExecutionPolicy –ListStep 3: After you execute the command, it will give you a list of the User Groups as well as their Execution Policy status, and under the Scope column, look for “LocalMachine”. Once you find its Execution Policy you will notice that it’s either set to Undefined or Restricted. Step 4: Now that you’ve determined the Execution Policy, you need to set it to Unrestricted if it is set to Restricted. To do that, you have to enter the following command in the very same PowerShell window.
Set-ExecutionPolicy UnrestrictedStep 5: After you execute the command, you will see a message that asks for various permissions for which you either have to tap Y to say Yes to each one of the messages individually or tap the A key to say Yes to all the messages to once. However, if the command throws another error, you can just force the Execution Policy to change by executing the following command.
Set-ExecutionPolicy Unrestricted -ForceStep 6: Once you’re done, it will finally set the Execution Policy for the Windows PowerShell scripts as well as cmdlets to be Unrestricted and fix the “File cannot be loaded because running scripts is disabled on this system” error.
Error code 0x8007267C is specific to Windows 10. This error is triggered when no DNS server is currently configured in your network settings during the Activation process. If you are fairly confident in your ability to address command-line tools and networking issues, you can follow the steps below to try to remedy the error code on your own. If not, you may need to contact a qualified technician in order to resolve the error successfully.
The cause of Error Code 0X8007267C within the Window 10 system is fairly straightforward. Windows Activation requires a valid DNS server to be configured in order to complete the Activation process; if one is not available or properly configured, then you may see this error code and Activation will fail.
The following methods may help you to resolve this error, but you’ll need to have some familiarity with command-line tools to complete the steps successfully. If these methods do not work or if you are uncomfortable in using the command prompt, you may need to consult a technician to fully resolve this particular error code on the Windows 10 system.
In order to resolve this error code, client connectivity to a DNS server must first be established. The following steps may help you to determine the root problem with your connectivity status:
ping <DNS Server IP address>
If basic connectivity to the DNS server in question is failing, then you will need to resolve that issue before going further in the process.
After troubleshooting the above basic connectivity issues to the DNS server, you can reattempt Windows Activation by using the command below from within an Elevated Command selection:
cscript windowssystem32slmgr.vbs -ato
If the steps above did not work for you, you may want to try the steps found in method 2.
If a DNS server is not connected to your network, you can use an alternative method to complete the Windows Activation process. Bypass Method 1 by using a MAK product key instead to activate the volume license installation. Certain MAK product key providers have a variation on the specific key numbers that you will need to use. If you are using TechNet media or MSDN media, you will have to change the product key listed to the product key provided. The product keys provided by either TechNet media or MSDN media for Windows Server 2008 or for Windows Vista Enterprise will be the MAK product key that you will enter in a later step.
Like the previous method, you will need to have some familiarity or confidence in your ability to operate Command Line tools before proceeding. Once you have found your MAK product key, you’ll need to open a command prompt and use the following command to change the product key to match the MAK product key, which should look something like the example below:
slmgr –ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
After completing the product key change, use the following command to initiate the phone activation wizard, thereby completing the activation of the system:
slui 04
The activation wizard should be able to walk you through the remainder of the process in a step-by-step manner. In addition to appearing as an error code in Windows 10, this particular error may apply to multiple versions of Windows, including:
Steps to address the error code may be different in any of these other versions of Windows. If you have difficulty in resolving the error effectively, seek professional technical help.