Users who upgraded to Windows 10 via the free offer from Microsoft have been greeted with a host of core apps preinstalled, which includes the highly addictive game Candy Crush Saga from King. It joins the ranks with Solitaire, Minesweeper and Hearts, games which are quite integral to the Windows platform.However, certain users are interested in figuring out a way to delete Candy Crush from their Windows 10. Deleting Candy Crush from the system might not be a simple right click and delete. Although some users are debating that Candy Crush Saga is not a pre-installed app and should be easily deleted by a simply right clicking the app in the Start Menu and choosing uninstall.If uninstalling the app through the Start Menu doesn’t work, then follow the procedure below for deleting Candy Crush Saga from Windows 10. This fix was first published in Superuser.
How To Remove Candy Crush Saga From Windows 10
Step 1: The go-to program to remove Candy Crush is “Windows Powershell.” Type powershell in the search box and a blue Command Prompt-like screen will appear.Step 2: Type the following command:Get-AppxPackage -Name king.com.CandyCrushSaga, copy/paste this command, copy it and in the PowerShell window right-click and select paste.Step 3: In the results that show up, look for the following: king.com.CandyCrushSaga_1.540.1.0_x86__khqwnzmzfus32 or a bit similar under the ‘PackageFullName’ line. Copy the complete ‘PackageFullName’ for the correct application.Step 4: Type ‘Remove-AppxPackage’ add space and paste or type the ‘PackageFullName’ that was extracted in step 3. Press Enter for the command to run.Step 5: Following that, the uninstallation process will be completed. To verify whether the process was successful, repeat step 2. This time the command will result in nothing. This will indicate that your Windows 10 is Candy Crush Saga free.Users can also check the Windows 10 Start Menu to find out whether the Candy Crush Saga app still exists or not. If the above fix worked for you then mention it in the comments or if there is another fix that solved the issue, mention that as well.
