A Patch for Windows Code 44 Error

File Transfer Protocol Server, also known as FTP Server, is a private or public service that can host files that can be accessed both locally and globally. It is a quick, flexible and seamless service that allows you to store any kind of files depending on the total size of the server. If you’ve always found an FTP server useful, then the good thing is you can now create your FTP server since Windows 10 now allows it. You can host this server locally and later on make it globally available via the internet. So if you are planning to set up an FTP server on your Windows 10 computer, read on as this post will guide you on how to do so.

To set up the FTP server, you need to configure it first and then configure the Windows Firewall for the connections to go through. For more details, refer to the following steps:

Step 1: You need to configure the FTP server on Windows 10.

• In the Search box, type in “Turn Windows Features On or Off” to search for it.
• Then click on the appropriate result which will open a mini window.
• From this mini window, scroll down to the list and expand “Internet Information Services where you have to expand the FTP Server section.
• Next, select all the checkboxes to enable all the entries under FTP Server and then click the OK button to apply the changes made.
• And now, since your computer is now allowed to host an FTP server, you need to configure it. To do so, type “Internet Information Services (IIS) Manager” in the Search box and click on the appropriate entry.
• Next, right-click on Sites under the navigation bar of Connections and select Add FTP Site. This will open a new window where you have to input some information about your FTP hosting.
• Now enter the details and click on Next.
• Upon clicking Next, you will be prompted to give some authentication details. Enter the following details in the screenshot below.
• Now click on Finish. After that, you will get an FTP Server being hosted on your Windows 10 PC.

And now that you’ve successfully configured the FTP Server, the next thing you have to do is to allow connections from and to the FTP server. Refer to the next step below. Step 2: Configure the Windows Firewall for FTP connections to pass-through

• In the Start Search, type “Allow an app or feature through Windows Firewall” and click on the related search result which will open a window with all the settings.
• From there, click on the Change Settings button. This will display a list where you have to mark all the checkboxes for the FTP server to enable them in both the Private and Public configurations.
• After that, click OK. This will allow you access to the FTP server on your local network.

Error Code 0x802400d - What is it?

The Error Code 0x802400d most often occurs when users attempt to use the Windows Update tool on their computers to move from one version of the software to another. In some cases, this error is more likely to appear on your computer during the process if you have not performed regular updates to the software as they have been available.

Common symptoms include:

• Inability to finish the download of the necessary update to Windows 10
• Incomplete installation of the desired Windows 10 update

While it can take additional time to deal with the issues that cause Error Code 0x802400d to appear on your computer, there are several steps that you can take to address the problem. These are fairly simple to perform and do not require advanced knowledge of the system to employ.

Solution

Error Causes

The most basic cause for Error Code 0x802400d is that there is a file or a process that is causing the update process to hiccup. In many cases, this error appears when a user attempts to begin the process of updating their computer if they have several stacked updates to perform. Computers that are several updates behind where they should be will display this error more often than computers that are kept on a schedule of recommended updates.

Further Information and Manual Repair

While there are multiple reasons why the Error Code 0x802400d may appear on your computer during the Windows Update process, there are several methods that can be used to attempt to resolve the problem on your own. These are generally easy to do and do not require advanced techniques. However, if you do not feel comfortable addressing the issue on your own, contact a qualified Windows repair technician.

Here are some of the best methods that users can employ to resolve Error Code 0x802400d:

Method 1:  Run the System Update Readiness Tool

There are a number of different processes, files, and settings that could cause Error Code 0x802400d to appear on your computer during the Windows 10 Update process. For this reason, the most efficient way to determine what the culprit is for your specific issue is to download and use the System Update Readiness function.

This tool is available directly from Windows. Although there are other tools available on the Internet that claim to be able to fix the problem, these can contain viruses and malware, so be cautious if you decide to employ these instead. There are also several versions of the tool on the Windows website, so be sure to download the version that matches the operating system and version of your computer.

Once you have downloaded the Readiness tool from the Windows website, allow it to run a scan on your system. At a minimum, this process will take about fifteen minutes to complete. Although you will see a progress bar at the bottom of the window, it does not always update effectively. Some users have reported that the update appears to stop when it is two-thirds complete. Continue to let the scan run if this happens, rather than canceling it out. Even if the progress bar doesn’t update, the scan is still running.

Method 2: Remove New Software and Re-Attempt the Update Process

If you have recently installed new software on your machine, it can sometimes cause problems with the update process. The best way to resolve this issue is to remove or uninstall the software, run the update process again, and then reinstall the software once the Windows system has been successfully updated.

If the above methods are not successful in resolving Error Code 0x802400d from your machine and you are still unable to complete the Windows 10 Update process or if you are not confident in your ability to complete these steps successfully on your own, get in touch with a qualified computer repair technician who is familiar with the issues surrounding Windows 10 in particular. Microsoft offers certifications for Windows repair technicians, so look for a professional who has the experience, skills, and knowledge necessary to adequately address Error Code 0x802400d on your machine.

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.

One of the primary packages that install the Windows Media Player is the Media Feature Pack among other related files that are needed by the associated software products. And one of the essential DLL files in that package is the mfplat.dll file which is needed by various games and streaming services. So if this DLL file goes missing, you will most likely encounter any of the following error messages:

• “mfplat.dll missing”
• “The application failed to start because mfplat.dll was not found.”
• “The program can’t start because mfplat.dll is missing from your computer.”

In other circumstances, the Media Feature Package does not come pre-installed with the main Windows package especially for those who use Windows N, thereby causing the error to pop up. The main cause of this problem is that users who use Windows 10 N do not have the Media Feature pack pre-installed with the installation package. Aside from that, the installation package could go missing after a few Windows Updates or if you have uninstalled it by accident. To resolve this problem, you need to check out each one of the given options below.

Option 1 – Try to enable Media Playback via Command Prompt

If you encounter the mfplat.dll missing error when you attempt to run PLEX or other similar streaming service and you’ve already verified that the Media Feature Pack is indeed installed, you might want to try enabling it using an elevated Command Prompt. There are cases when a particular Windows Update ends up disabling the feature and creates the grounds which results in the mfplat.dll missing error. Thus, you can have to enable the feature via Command Prompt.

• Tap the Win + R keys to open the Run dialog box.
• Then type “cmd” in the field and hit Enter to open an elevated Command Prompt.
• Next, click on Yes if a User Account Control prompt pops up.
• After opening Command Prompt, copy and paste the following command and hit Enter to execute it:

dism /online /enable-feature /featurename:MediaPlayback

• Close Command Prompt and then open the app once again to check if the problem is now fixed.

Option 2 – Try installing the Media Feature Pack for Windows 10 N version

As mentioned, the Windows 10 N version does not come with Windows Media Player. Meaning to say, the Media Feature Pack is also not installed by default or won’t be updated by the Windows Update component. So if you are not quite sure what Windows 10 version you currently have installed, refer to these steps:

• Tap the Windows key + S and then type “about” in the search box.
• From the search results, click on the “About your PC” to open the About tab of the Settings app.
• Afterward, scroll down to the Windows specifications and check your Windows version under Edition.

Note: If you have verified that your PC is using the Windows 10 N version, you need to install the appropriate Media Feature Pack for your computer. How? Refer to the steps below:

• Click this link to download and install the Media Feature Pack from Microsoft’s official website.
• Upon installation, select the edition you want to install using the drop-down menu and then click on Confirm. Take note that there are few reasons why you’d want to install the older version since most streaming services like PLEX and most games usually require version 1803.
• After that, wait until the request is validated. The download should begin in a few minutes automatically.
• Once the download is completed, open the installation executable file and follow the next on-screen instructions to install the Media Feature Pack on your computer.
• Restart your computer. After your computer has rebooted, open the application where you’re getting the mfplat.dll missing error and then check if the problem is now fixed.

Option 3 – Try to extract a copy of the mfplat.dll file from the windows.old directory

If you encounter the error shortly after you just upgraded to Windows 10 from an older version, the best thing you can do to resolve the problem is to use windows.old directory to fetch an old copy of the mfplat.dll file. To do so, follow the steps below.

• Go to the Windows drive and then look for the windows.old directory where it preserves a copy of your old operating system as well as associated files in case something goes out of hand during the upgrade process.
• After that, open the windows.old folder and then go to the syswow64 folder.
• Next, from the syswow64 folder, copy the mfplat.dll file and paste it to C:/windows/syswow64.
• Restart your computer and check if the error is now resolved or not.

As you know, the Windows 10 operating system has support for a dedicated high-end graphics processor that brings in capabilities inside to support Graphics Cards from NVIDIA or AMD. This helps the operating system to function in a much better way by segregating the graphics-intensive operations from the CPU to a dedicated processor. However, there are times when it also experiences some issues that lead to some errors like the “Failed to create a graphics device” error. It is possible that your computer has more than one screen or graphics card which is why you’re getting this error. To fix it, you need to try reinstalling DirectX or reinstall the Graphics Card driver. You could also try to manually check the hardware or power cycle of your computer. To start troubleshooting the “Failed to create a graphics device” error, follow the given suggestions below.

Option 1 – Try running the DirectX Diagnostic Tool

Since the error has something to do with the DirectX Graphics APIs, you can run the DirectX Diagnostic tool to resolve the problem.

Option 2 – Try updating or re-installing DirectX

If the DirectX Diagnostic tool didn’t work, you can try to update or reinstall DirectX instead. This can help in fixing the problem because when you reinstall or update DirectX, it will replace the incompatible or corrupted components of DirectX from your computer.

Option 3 – Update or reinstall the Graphics card drivers

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in 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: You also have the option to 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.

Option 4 – Try to physically check the hardware of your computer

You might also want to check the physical status of the hardware in your computer. You can clean the dust off the hardware components like the Graphics Card of the computer. In doing so, you have to use a small blower or you could also use a soft cloth and run the components gently. Make sure that you don’t damage any parts with moisture or cause harm to any circuits while you carry out this task.

Option 5 – Try to power cycle your computer

You could also try to power cycle your computer to fix the error. To do that, you have to turn off your computer in a way that the power is completely cut off and all the fresh configurations of files are loaded when your computer is booted up. The first thing you have to do is to shut down your computer and if you are using a laptop with a removable battery, you must remove the battery for a couple of minutes before you plug it back in and boot your laptop. On the other hand, if you are using a desktop computer, press and hold the power button until the CPU goes off and take out the power cable for a minute or so and then plug it back in. Boot your computer and see if the error has been resolved.

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.

Even with the new Groove Music in Windows 10, a lot of users still prefer to use the old Windows Media Player. This isn’t surprising since Windows Media Player still remains to be one of the best players you can find. However, that does not mean that it is without flaws as it could still encounter some issues from time to time. One of the issues you might encounter when using the Windows Media Player is when you try to burn DVDs or CDs but end up failing due to an error that pops up that says, Windows Media Player cannot detect the length of the file. At the time of writing, it isn’t clear yet what the real cause of the error is. However, there are several fixes that are provided in this post for you to check out so you can resolve the problem. You can try to get rid of any unsupported files from the burning list or you could also try running the Windows Media Player troubleshooters. Aside from that, you could also try to drag and drop music or change the burning speed. For more details, refer to the following options.

Option 1 – Get rid of the unsupported files from the burning list

You must get rid of the unsupported files from the list of files to burn. This list can be found on the right-hand side of the Windows Media Player. One of the indications that a file is causing problems is when there is a white cross in a red circle next to the file. You can simply click on that icon to remove the file from the burning list. Once you’ve gotten rid of all the unsupported files, try to burn your files to the CD or disk once more.

Option 2 – Try running the Windows Media Player troubleshooters

The next thing you can do to fix the error is to run the built-in troubleshooters for the Windows Media Player. Windows 10 actually comes pre-packed with three troubleshooters designed for Windows Media Player. They can help in fixing the “Windows Media Player cannot detect the length of the file” error. To run these troubleshooters, simply tap the Win + R keys to open the Run dialog box and type “msdt.exe -id WindowsMediaPlayerConfigurationDiagnostic” for the Windows Media Player Settings troubleshooter or type “msdt.exe -id WindowsMediaPlayerLibraryDiagnostic” for the Windows Media Player Library troubleshooter, or type “msdt.exe -id WindowsMediaPlayerDVDDiagnostic” for the Windows Media Player DVD troubleshooter.

Option 3 – Try to drag and drop music

Another thing you can check out is to drag and drop all the tracks into the Windows Media Player before you burn them. All you have to do is open the folder where the tracks are located and highlight all of them and then drag them to the Windows Media Player. It should now be able to detect the length of each one of the tracks without any errors.

Option 4 – Try to change the burning speed

Since the burning speed is set to fastest by default, you can try to change the burning speed to resolve the problem. Just open the Options window and then go to the Burn tab. From there, select either Medium or Slow burning speed and save the changes made. Now try to burn your files to the CD or disk once again.

If your Windows PC encounters an error, it will display a Blue Screen of Death or BSOD error which usually comes up for a fraction of second and creates some logs or Dumps Files as what other user prefers to call it and then boots your PC suddenly. This process usually takes place quickly that most users find it hard to get the error code and won’t probably be able to check what really went wrong with their PCs. This is where the dump files come in. They are stored internally in your computer and can only be accessed by an administrator. They are classified into 4 main types and in Windows 10 they are either:

1. Complete Memory Dump
2. Kernel Memory Dump
3. Small Memory Dump (256 KB)
4. Active Memory Dumps

Dump Files are useful as they could help you in resolving the problem and so you need to configure your Windows 10 PC to create them but first, you need to make a system restore point. This is essential as you are about to modify some system files as well as critical Windows 10 settings. There are two ways you can create Dump files – first is by modifying the settings in the Startup and Recovery and lastly is via the WMIC command line. Refer to the instructions prepared below to be guided on how you can create Dump files after any BSOD error using these options.

Option 1 – via Startup and Recovery

• Type in “control panel” in the Cortana Search box and then click on Control Panel from the search results to open it.
• After opening Control Panel, you need to make sure that you view the contents by their Category then click on the header link which is labeled “System and Security” or you could also right-click on the This PC icon and then click on Properties.
• Next, select the Advanced system settings from the left panel. Once you do, a new and small window will pop up.
• Under the newly opened window, look for the section called Startup and Recovery and then click on the Settings button.
• And from the System Failure section, you can choose any option from the drop-down for Write debugging information such as:
  • None – this means that there is no dump file created by Windows
  • Small Memory Dump – this means that Windows will create a Minidump file on BSOD
  • Complete Memory Dump – this means that Windows will create a Complete Memory Dump file on BSOD
  • Automatic Memory Dump – this means that Windows will create an Automatic Memory Dump file on BSOD
  • Active Memory Dump – this means that Windows will create an Active Memory Dump file on BSOD

Note: The complete dump needs a page file that is allowed to be the size of the physical memory installed in your PC with a dedicated 1 MB of space for just the page header.

• Now once you have selected the most suitable option for you, just click on OK/Apply and then exit.
• Restart your PC to successfully apply the changes made.

Option 2 – via the WMIC command line

• The first thing you need to do to create Dump files via the WMIC command line is to tap the Win + X keys combination or simply right-click on the Start button and then select the Command Prompt (Admin) option. You could also type in “cmd” in the Cortana search box and then right-click on Command Prompt from the results and select Run as administrator.
• After that, type in any of the commands given below depending on your preferences so that your Windows 10 PC will be configured to create Dump Files:
  • No dump file: wmic RECOVEROS set DebugInfoType = 0
  • Small Memory Dump: wmic RECOVEROS set DebugInfoType = 3
  • Kernel Memory Dump: wmic RECOVEROS set DebugInfoType = 2
  • Complete Memory Dump: wmic RECOVEROS set DebugInfoType = 1
  • Automatic Memory Dump: wmic RECOVEROS set DebugInfoType = 7
  • Active Memory Dump: wmic RECOVEROS set DebugInfoType = 1

Note: A complete dump has to have a Page file which is allowed to be the size of the physical memory installed on your PC accompanied by a 1 MB space for just the page header.

• Now type in “exit” in the Command Prompt to exit it.
• Restart your PC to apply the changes made successfully.

Today we will be solving the Device not found 3F0 error which is a common error, especially among HP (HP Pavilion G6), Lenovo, Acer, and Dell laptops/desktops. This error occurs when the computer is turned ON and when the system is about to boot. It can happen on windows 7,  8, or 10. When a mentioned error occurs one of the following messages will be displayed on your screen:

• “No bootable device – insert boot disk and press any key”
• “No Boot Device Found. Press any key to reboot the machine”
• “Boot Device Not Found. Please install an operating system on your hard disk. Hard Disk (3FO)”
• “No boot device is available”

The most common reasons for 3F0 error to occur is:

• Using the unbootable device or disk to boot from.
• If the bootable hard drive you are using might have corrupted or damaged somehow.
• MBR or boot sector is damaged on the bootable hard drive.
• If your system has gone through a virus or malware attack.
• The wrong boot order in the BIOS.
• Hard disk connection problem.
• System files or boot files unknowingly damaged.
• Corrupt hard drive partitions.

This is well, the most simple solution and the easiest one, try to change the boot sequence in the BIOS settings of your motherboard. Sometimes most easier solutions can provide great results and solve our problems. If sadly this fails and the issue persists move to the next solution.

2: Perform a Hard Reset

---

Performing hard reset can often solve issues, to perform a hard reset do the following:

• Turn off the computer and unplug the power adapter. If there is a removable battery, it should also be removed.
• Then disconnect all peripherals, including the removable hard drive, etc.

then

• Press and hold the power button for 15 seconds to drain all remaining power.
• Insert the battery, and then re-plug the AC adapter into the laptop.
• Press the power button to turn on the computer.
• Once the computer starts up properly and the startup menu appears, use the arrow keys to select “Start Windows normally” and then press Enter.

Reconnect everything back of your peripherals. If by any chance problem still persists follow the next step:

3: Test Hard Drive Using HP Diagnostic Tool

---

Use the built-in tool in the Hp device to solve the issue:

• Turn on your computer and keep pressing the Esc key until the menu appears on the screen.
• Next, press the F2 key.
• Choose the Components Tests option from the HP PC Hardware Diagnostics menu.
• Select Hard Drive from the Component Tests menu.
• Click on the Quick Test, then click on the Run once button.
• If there are still any issues with your hard drive, then run the Extensive Test.

4: Restore BIOS Default Settings

---

• Press the Power button to start the computer, and immediately after this, repeatedly press the F10 key to enter the BIOS setup menu.
• To load and restore BIOS Setup Default settings, press F9 on the BIOS setup menu.
• Once loaded, press F10 to Save and Exit.
• Select yes, and then press Enter when it says Exit Saving Changes.

5: Reconnect Your Hard Drive

---

• Turn the computer off and remove the power cable.
• If you have a removable battery, take it out
• Disconnect your hard drive and then connect it back.
• Reassemble your computer and turn the computer on to see if it fixed the issue.

6: Fix and Rebuild Damaged MBR

---

• Boot from the original installation DVD (or the recovery USB)
• At the Welcome screen, click Repair your computer.
• Choose Troubleshoot.
• Choose Command Prompt.
• When the Command Prompt loads, type the following commands: bootrec /FixMbr bootrec /FixBoot bootrec /ScanOs bootrec /RebuildBcd.

7: Fix Operating System

---

• Prepare a Windows installation disc, CD/DVD or USB flash drive and connect it to your PC.
• During the installation process, launch Command Prompt.
• In Windows 7, under the System Recovery Options tab, click Startup Repair.
• In Windows 8 and Windows 10, click Repair your computer, then select Troubleshoot > Advanced options > Automatic Repair (Windows 8) or Startup Repair (Windows 10).

8: Replace the Hard Disk

The euphoria around Windows 11 is not dying and reveal that Android apps will work natively inside Windows 11 has raised many emotions and questions. So, Microsoft has announced that Android apps will run natively inside Windows 11 OS and that they will reside alongside your other installed ones as icons, etc. It is no secret that many users have been using emulation software to run Android apps inside Windows so far, so what is the difference?

It is still emulation

Whatever you would like to believe it is still emulation and Android apps are at the end of the day still Android apps running inside emulated environment. This time we will not need third-party emulation software running inside Windows, we will have third-party emulation services running inside Windows. Intel has teamed up with Microsoft in order to integrate Intel bridge algorithms in order to run Android apps, meaning that yea, pretty much we have emulation services running in order to run the application. The problem with this kind of approach is that well emulation software is running and consuming system resources only when we start it, this kind of service is always running and always consuming resources and for someone who really does not care about Android apps at all, this is just a waste of resources.

Android store

The store is another issue here, instead of the Google play store we will have the Amazon app store integrated inside the new Microsoft store. This means that any kind of for example game progress or login information from Google store cannot be transferred into Windows 11, add to that information that in the Amazon app store there are tons of missing applications like SLACK, TRELLO, BitWarden, etc and we might have a serious question here about the use of this feature.

Android apps that do not use Android services

If you even look past that it is still emulation and that it is available on the Amazon app store there is still concern about applications not using Google services for their running. Many Android apps are relying on Google services like location or optimize their use of on-device resources, handle in-app purchases, etc. that cannot be found on this system. Uber is a prime example that uses Google location service to determine your location and for its mapping data, with that application, is useless. Other like Guardian will even pop up message that says Google play service is required in order to even work.

Android apps without Eero system

Amazon Eero system for enhanced internet access is not even yet available in its own app store which brings us to missing some key players like Bank of America, Chase mobile, Bueller, etc. And across the board, the apps that are present in the Amazon Appstore are often as good as abandoned. Lots of titles are numerous versions behind their up-to-date Play Store counterparts, and plenty of programs you encounter in the Amazon environment clearly haven't been touched in years.

Conclusion

Many new Windows 11 features are quality features that I personally consider good but although this one seems innovative and good I simply cannot stand back it up. Android apps were already inside Windows with emulation software which used google services and was working just fine, this was not needed in my opinion.

Lately on EA forums question has appeared on what to do when Origin client does not load library. It seems that the latest update for the Origin client has brought some issues as not properly showing one library which appears empty. Do not worry, we have a solution for you, several to be precise and it will fix the issue guaranteed. It is advisable to try solutions in order how they are presented since they go from the most simple and fastest and most common ones.

1. Delete the cache

   Close origin client completely Press ⊞ WINDOWS + R to bring the run dialog In the run dialog type in %ProgramData%/Origin and press ENTER Go into the Origin folder Delete all files and folders except the LocalContent folder Press ⊞ WINDOWS + R to bring the run dialog In the run dialog type in %AppData% and press ENTER Delete the Origin folder In the address bar click on AppData Go into the local folder Delete Origin folder Reboot your PC

2. Clear the temporary files

   Press ⊞ WINDOWS + R to bring the run dialog In the run dialog type in %AppData% and press ENTER Go into the roaming folder Delete Origin folder Go to the AppData folder and delete the Origin folder from there also Reboot system

3. Try Windows built-in tools to check compatibility

   Locate where Origin is installed and right-click on the executable file Click on properties Go to the compatibility tab Click on Run the compatibility troubleshooter and follow on-screen instructions

4. Update Origin

   Rarely this is the case but check manually to see if you can update your Origin client. Sometimes due to network issues client does not update automatically and can cause this strange behavior.

5. Add origin as an exception to antivirus and firewall

   Not rarely game clients can be detected as some form of malicious software and antivirus along with firewall can automatically block it. Go to your security software settings and add it as the exception.

6. Reinstall Origin

   If everything else fails, reinstall the Origin client