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.
‘An error is preventing the photo or video from being displayed’ Error code 0x80010108
Error Causes
For anyone who is not aware, when Windows 11 was released if you wanted to switch to another browser you had to go into the settings app and choose the default browser for different types of file extensions like HTML, HTM, PDF for opening on the web, etc. Of course, this was completely unnecessary and it was not well received by users. So after some time, Microsoft backpedaled to standard one click, choose your default browser solution that existed in the previous version of Windows OS.
Altho sometimes Microsoft knows how to irritate its users base, it is good to know that they can also listen and fix things that are required. Code 32, a Device Manager error, pops up when a device driver and other required services related to the driver are disabled.
The error code 32 is usually displayed in the following format:
“A driver (service) for this device has been disabled. An alternate driver may be providing this functionality. Code 32”
When a driver experiences a problem, it is reported to the Device Manager. Though error Code 32 does not cause detrimental damage to your system, it can cause the loss of functionality of the hardware device whose driver is disabled.
Error CausesIf you come across error code 32 on your PC, then repair it immediately to ensure optimum PC performance. To resolve this error code, try the methods listed below. If you are not a computer programmer, don’t worry!
The listed solutions are easy to perform, require no technical background or expertise and more importantly, these solutions are very effective.
Simply follow the instructions to repair error code 32 on your system in just a few minutes.
Sometimes Device Manager error codes may appear due to temporary issues, which may be resolved simply by rebooting your system. If you are lucky, this might actually work.
By restarting your PC, you might be able to get rid of error code 32. However, if the error still persists, then try other methods given below.
To resolve error code 32, uninstall and then reinstall the driver. To uninstall the driver, simply follow these steps:
As discussed above, sometimes error code 32 may be triggered due to corruption of registry values.
If this is the underlying cause, then delete both the upper filters and lower filters registry values from the registry. This will take about 5 to 7 minutes. Here’s what you have to do:
This will hopefully resolve error code 32 on your system if the error was generated due to registry value corruption. However, if the error continues to appear, then resort to method 4.
Locate the problematic drivers and update them with the latest versions. This procedure is effective but time-consuming if performed manually.
It takes several minutes to identify problematic drivers and find the latest and compatible versions for each driver on the manufacturers’ website. And besides, you will have to perform updates continuously to ensure the error doesn’t occur again.
Method 5 - Download DriverFIX to Update Drivers Automatically
To avoid the hassle, download DriverFIX.
This is a cutting-edge and user-friendly software program embedded with intelligent system programming and intuitive technology that identifies problematic drivers and updates them with the latest and compatible driver versions in seconds, automatically and on a regular basis.
By installing it on your PC, you can update all the drivers and repair code 32 in no time.
Click here to download DriverFIX to resolve Device Manager error code 32 today!
After Plex, DoorDash, and LastPass, Samsung has also confirmed that they also have experienced a data breach and that some customer data has been stolen.
On Friday, September 2nd Samsung announced that an unauthorized third party gained access to some of the company's U.S. systems in late July and that Samsung learned in August that some personal information was affected. It was also stated that affected information is: names, contact information, demographics, dates of birth, and product registration information. Also so far it was said that no Social Security numbers nor credit card number information have been compromised.
For now, Samsung is sending an email directly to anyone that has been affected by this data breach, however, they did not state what service or product has experienced this breach, we just know that it has happened at Samsung Electronics America which sells everything, from smartphones to debit cards. Also keep an eye on your inbox if you are a Samsung user since it took them a whole month in order to go public with this information and there is no justification for this, if it was reported on time people could change their information and take other steps.
“There were problems installing some updates, but we’ll try again later, If you keep seeing this and want to search the web or contact support for information, this may help – 0xc1900403”The log files displayed in the error message may include, “0XC1900403 – MOSETUP_E_UA_CORRUPT_PAYLOAD_FILES”. This indicates that the payload files are corrupted which is why you’re getting the Windows Update Error 0xc1900403 and to fix it, you can try to restart your computer and install the updates again or reset the Windows Update-related folders. You could also run the Windows Update troubleshooter or use either the Standalone Installer or the Media Creation tool. For more details, refer to each one of the options provided below.
net stop wuauserv net start cryptSvc net start bits net start msiserver
net start wuauserv net start cryptSvc net start bits net start msiserver
Error Code 52 is a device driver problem that users experience on any Windows 2000 operating system and later Windows systems.
The error occurs when the operating system prevents the peripheral device connected to the computer from functioning properly and is usually displayed by the following message:
“Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)”
Error CausesError Code 52 is triggered by the following factors:
Error Code 52 can pose severe risks to the overall health of your PC and any negligence in fixing it can be disastrous for your computer.
However, since the error code is like other device driver errors, resolving the error is relatively straightforward. Here are a few methods to resolve the error code.
You can use system restore to roll back the system to a time when there was no error to eliminate the problem. Here is how you can use it:
By restoring the system via a last saved system checkpoint, you can obtain undamaged Windows system registry files that can help avert the error code.
If restarting your PC does not help, you will have to find the exact nature of the problem by running the troubleshooting wizard for the device and address the problem accordingly. To do this, proceed with the following steps:
After following the directions of the Troubleshooting wizard, make sure to restart your PC for the changes to take effect. Then check if your device is still causing problems.
Uninstalling and then reinstalling the device driver can help solve the error.
You can do this by firstly logging in as Administrator and open Device Manager. Select the device that is causing the problem and double click it and make sure that the peripheral is connected properly to the PC.
Upon opening, click on the ‘Driver’ tab and then select ‘Update Driver’. Make sure to refer to the system documentation that you received with your PC or computer to check for the motherboard details and driver specifics.
Manually uninstalling and reinstalling the driver will do the trick, however, it may be time-consuming especially when you would have to resort to your hardware user manual.
Therefore, using a program such as DriverFIX can save you a lot of time and frustration in having your device work properly on your computer.
DriverFIX, with its user-friendly approach to help you fix your PC issues, comes with an integrated database that detects which drivers you need to reconfigure within just a few seconds and downloads it automatically.
It further ensures that your drivers are installed in their entirety leaving no room for any incomplete files to remain that create Error Code 52.
It also has the added advantage of being able to backup and restores your files should there be the slightest possibility of system file damage. DriverFIX is the answer to fixing your PC error codes accurately and quickly.
Click here to download DriverFIX to fix Error Code 52 quickly and effectively!
Same as Windows 10, Windows 11 also keeps track of date and time using an internet time server. But in a case that you need to change the date or time for any kind of reason here is a guide for that process:
iWin is a self-published games platform that offers users to download and play free games. It is classified as potentially unwanted, primarily because it often comes bundled with the iWin Toolbar, which is an adware supported browser extension by Conduit. The iWin Toolbar is heavily flagged as malware or unwanted by numerous Antiviruses. iWin Games is not malicious in itself, though due to its bundling and common inclusion of the toolbar, many users wish to remove it.
Intel says that the remedy to the issue for these games is the scroll lock fix which can be done so by enabling Legacy Game Compatibility mode from the BIOS of your motherboard. When running the said games, you can press scroll lock to park the E-cores on Intel's Alder Lake Desktop CPUs to get rid of DRM issues.
Certain motherboard manufacturers such as MSI and Gigabyte have made this even easier through software tools with which you don't have to access the BIOS. All you need to do is select a button in the tool which works on both Windows 11 and Windows 10 operating systems and you will enable compatibility mode. 
The true cause is that there is no working Border Gateway Protocol (BGP) routes into Facebook's sites. BGP is the standardized exterior gateway protocol used to exchange routing and reachability information between the internet top-level autonomous systems (AS). Most people, indeed most network administrators, never need to deal with BGP.
Cloudflare VP Dane Knecht was the first to report the underlying BGP problem. This meant, as Kevin Beaumont, former Microsoft's Head of Security Operations Centre, tweeted,
"By not having BGP announcements for your DNS name servers, DNS falls apart = nobody can find you on the internet. Same with WhatsApp btw. Facebook has basically de-platformed themselves from their own platform."
Many people are very annoyed by this and with the fact that they cannot use their social media platforms but it seems that Facebook employees are in even bigger annoyance as it was reported that Facebook employees can't enter their buildings because their "smart" badges and doors were also disabled by this network failure. If true, Facebook's people literally can't enter the building to fix things.
Reddit user u/ramenporn, who claimed to be a Facebook employee working on bringing the social network back from the dead, reported, before he deleted his account and his messages:
"DNS for FB services has been affected and this is likely a symptom of the actual issue, and that's that BGP peering with Facebook peering routers has gone down, very likely due to a configuration change that went into effect shortly before the outages happened (started roughly 1540 UTC). There are people now trying to gain access to the peering routers to implement fixes, but the people with physical access is separate from the people with knowledge of how to actually authenticate to the systems and people who know what to actually do, so there is now a logistical challenge with getting all that knowledge unified. Part of this is also due to lower staffing in data centers due to pandemic measures."
Ramenporn also stated that it wasn't an attack, but a mistaken configuration change made via a web interface.
Both BGP and DNS are down, the "connection to the outside world is down, remote access to those tools don't exist anymore, so the emergency procedure is to gain physical access to the peering routers and do all the configuration locally."
Technicians on site don't know how to do that and senior network administrators aren't on site.
It seems that it will all be down for a couple of more hours before the issue is resolved. 