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.
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
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
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
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.
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.
If everything else fails, reinstall the Origin client

“This policy setting allows you to prevent Windows from installing removable devices. A device is considered removable when the driver for the device to which it is connected indicates that the device is removable. For example, a Universal Serial Bus (USB) device is reported to be removable by the drivers for the USB hub to which the device is connected. This policy setting takes precedence over any other policy setting that allows Windows to install a device. If you enable this policy setting, Windows is prevented from installing removable devices and existing removable devices cannot have their drivers updated. If you enable this policy setting on a remote desktop server, the policy setting affects redirection of removable devices from a remote desktop client to the remote desktop server. If you disable or do not configure this policy setting, Windows can install and update device drivers for removable devices as allowed or prevented by other policy settings.”
That being said, now when services are back we stopped and reflected on the platform itself and on its users. If Facebook is vulnerable so are its users, but sometimes users themselves are responsible for being a target. We step back and take a look at posts that manifest on Facebook and have come with some advice on what things you should never post on Facebook and on other social platforms.
“The scratch directory size might be insufficient to perform this operation”This kind of error in DISM occurs when the DISM command is executed from the Windows Recovery Environment due to the limited size permissions of a delivery where the operating is being performed. To fix this DISM error, you need to follow the instructions laid out below. Step 1: First, tap the Win + R keys to open the Run utility and then type “cmd” in the field and tap Enter to open Command Prompt. Step 2: Next, you have to specify a scratch directory that contains the Windows folder and to do that, you can either use the DIR command or the BCEDIT command. So in the elevated command prompt type and enter “dir” or “bcedit”. Step 3: After that, you will see a list of folders inside the C: partition. Now you have to create a folder named “scratch” inside the partition. To do so, execute the following command:
mkdir C:ScratchNote: The command you just entered will create a directory inside the root of the C: partition named Scratch. Step 4: Now that you’ve created the Scratch folder, note that each time you run any of the DISM commands, you have to enter the following code snippet in them:
/ScratchDir:C:ScratchNote: For instance, if you are using the DISM tool to repair the offline Windows image, instead of executing the “Dism /Online /Cleanup-Image /RestoreHealth” command, you now have to execute the “DISM /Image:C: /ScratchDir:C: Scratch /Cleanup-Image /Restorehealth” command. And if you want to remove a selected installed update package, you can use the “DISM /image:C: /ScratchDir:C:Scratch /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e75~amd64~~16299.196.4.9” command. Keep in mind that the mentioned package is only an example. And lastly, you also have to replace the drive letter in the new code snippet when you execute the commands given above.
Error Causes“We’re having trouble restarting to finish the install, Error 0x8024a11a, 0x8024a112, 0x80070005 or 0x80070032”And so to fix this problem, this post will give you a couple of possible solutions. Refer to the options given below to get started.
SC config trustedinstaller start=auto
Error Causes