And here is the preview of them
































If you are using Windows PowerShell and it suddenly throws an error message saying, “File cannot be loaded because running scripts is disabled on this system”, then read on as this post will guide you on how you can fix this issue your Windows 10 computer. This kind of error in PowerShell is most likely due to the fact that your user account does not have the required permissions to execute the script. Although this does not mean that you need to have administrator-level permissions as it could also indicate that you have to be unrestricted to run these types of PowerShell scripts or cmdlets. Thus, to fix the error and carry out the task, you have to set the execution policy to be unrestricted. And to do that, you need to use the steps provided below as a reference.
Step 1: To get started, you have to check what policies are set for the individual user groups on your computer by tapping the Win + X key combination or by right-clicking on the Start button and clicking on Windows PowerShell (Admin). You can also search for PowerShell in the Start Search and then right-click on Windows PowerShell and select Run as administrator.
Step 2: If a User Account Control or UAC prompt appears, just click Yes to proceed. Once you’ve pulled up Windows PowerShell, type the following command to get the List of Execution Policy for all the scopes on your computer.
Get-ExecutionPolicy –List
Step 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 Unrestricted
Step 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 -Force
Step 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.
One of the most common errors encountered by Microsoft users upgrading from Windows 7 or Windows 8/8.1 to Windows 10 is the Error Code 0xc1900106. Microsoft users experience a failure in the installation process. Either they will be notified that the installation process was ended but failed or that Windows is not able to install the update.
More and more Windows users are having trouble upgrading their operating system to Windows 10. There are a lot of errors being encountered by users and one of them is the Error Code 0xc1900106. This error is normally due to the misconfigured system files. If a Windows user encounters this error, most likely their device has some registry problems.
Fixing error code-related issues could be best resolved to do manual repair methods. Applying repair methods manually can help Windows users address the root causes of the errors they encounter, as well as apply definite solutions to rectify the issue.
Most Windows users can be able to implement manual repair methods themselves but there are some cases where help from a Windows professional is needed. If you’re not a very tech-savvy person and not confident performing the manual repair methods yourself, it would be advisable to seek help from a professional Windows technician who is knowledgeable enough to address the errors or problems you are encountering. However, if you don’t want to resort to seeking help from a professional, you can also consider using a powerful automated tool.
In trying to fix Error Code 0xc1900106, here are the following manual repair methods you can take:
net stop wuauserv net stop cryptSvc net stop bits net stop msiserver ren C:WindowsSoftwareDistribution SoftwareDistribution.old ren C:WindowsSystem32catroot2 catroot2.old net start wuauserv net start cryptSvc net start bits net start msiserver pause
-file "C:/Users/Ayush/Desktop/Powershell Script Sample.ps1"Step 8: Once done, click on OK to save the changes made and see if the task is still giving you an error or not. On the other hand, if you are still getting the same error, you can try to repair the Task Scheduler by deleting corrupted tasks. Note that a single corrupted file can cause big problems so this option is quite important. And for you to delete a corrupted task or any task from the Task Scheduler, you have to use the Registry Editor if you are not able to use the Task Scheduler interface. To do so, follow these steps:
“Socket.error: [Errno 10013] an attempt was made to access a socket in a way forbidden by its access permissions”
"Windows cannot start new hardware devices because the system hive is too large (exceeds the Registry Size Limit). (Code 49)”The error causes unattached devices to be displayed on the system hive list.