After so many years World of Warcraft is still among the most played MMORPG games in the world. It is still constantly updated with new content and tweak graphically in order to be relevant and fresh. But even the best or most popular ones can still have some minor issues and bugs from time to time. CAS System Was Unable to Initialize is the error that was reported lately by WOW players all around the globe and it happens in multiple Windows systems.
In this guide, we will take with this issue and provide you with solutions on how to fix it so you can get back to enjoying the game itself.
In battle.NET launcher select WOW and click on Options
Click on Scan and Repair
Let the process finish and then launch the game again
Windows cleaning registry operation is a complex task and we will not cover each possible scenario here, instead of trying manually to find issues and clean registry download and install third party registry cleaner software.
One of the solutions for this particular error is to run WOW with a specific command line switch:
Run battle.NET client as administrator by right-clicking on it and choosing run as administrator
If you are not signed in, sign in now
Click on World of Warcraft to select it
Click on options
Click on Game settings
Check the box associated with Additional command-line arguments
When the box is selected you should've able to add inline argument or switch, add -uid wow_engb and confirm
Run World of Warcraft
It was reported that enabling this service can fix the issue.
Press ⊞ WINDOWS + R to open the run dialog
Inside run dialog type in services.msc to open services windows
Locate the Secondary Logon service
Right-click on Properties from the context menu
Inside the properties, screen click on the general tab
Change the Startup type to Automatic and hit Apply to save the changes
Run World of Warcraft
Both indices and cache folder needs to be deleted in order to reset corrupted data. Make sure that both World of Warcraft and battle.NET are fully closed
For this step to work, you will need to go into the folder where you have installed the World of Warcraft game. By default this is in C:/Program Files/World of Warcraft/ but if you have used another folder go there via file explorer.
Once you are inside the folder locate the indices folder and delete it
After that locate and delete the cache folder as well
Restart your computer and start battle.NET
Another reason for CAS System Was Unable to Initialize error is because the World of Warcraft folder has been set to read-only and since the client does not have write privileges it will throw this error. To remove the read-only attribute from the folder go to your World of Warcraft installation folder but do not enter it
Right-click on it instead and choose properties
Under properties uncheck the read-only box and confirm.
Run World of Warcraft
The docking station was promised upon release of the Deck but it was pushed back and now the official statement is that it is delayed again.
Valve said in an announcement on June 1:
“Due to parts shortages and COVID closures at our manufacturing facilities, the official Steam Deck Docking Station is delayed. We’re working on improving the situation and will share more info when we have it.”
Valve
The docking station was presented at the same time as Deck itself and the whole idea was to make Steam Deck work like a laptop docking station. It has ports for USB devices, displays, and network connections that became functional the moment Deck is placed on it. Docking supports a mouse, keyboard, and external display making it an almost full PC station if needed.
Valve confirmed that its official dock station will not improve performance so while you wait for its release you can use another docking station with a USB Type-C connector.
“System Restore did not complete successfully. Your computer’s system files and settings were not changed. Details: System Restore failed while scanning the file system on the drive <Partition Letter> The drive might be corrupt. You might want to retry System Restore after running chkdsk /R on this disk. An unspecified error occurred during System Restore. (0x80070013) You can try System Restore again and choose a different restore point. If you continue to see this error, you can try an advanced recovery method.”Whereas in Windows Backup, it states:
“Check your backup, Windows Backup failed while trying to read from this shadow copy on one of the volumes being backed up. Please check in the event logs for any relevant errors. The backup failed, The media is write protected (0x80070013).”On the other hand, you will see the following error message in Windows Update:
“There were some problems installing updates, but we’ll try again later. If you keep seeing this and want to search the web or contact the support for information, this may help: (0x80070013).”There are several suggestions you can check out to fix the error depending on where you encountered it. If you encountered it while running Windows Updates, then you can try to reset the Windows Update components or run the Windows Update Troubleshooter. And if you got the error when running System Restore, you can try to run a System File Checker scan or the DISM tool as well as the CHKDSK utility. Lastly, if you got this error when running the Windows Backup service, you can try to check its status in the Services Manager. Error 0x80070013 in Windows Updates:
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
net stop wuauserv net stop bits
net start wuauserv net start bitsSince the folder has already been flushed, it will be populated afresh the instant your restart your computer and open Windows Update.
bcdedit /set recoveryenabled NO
chkdsk /r /f