Windows 8: Sorry there was a problem mounting the file
If you want to mount an ISO file in Windows 8 but you get the error Sorry there was a problem mounting the file try this
Updating Windows 8
1. Apparently, Microsoft patched this bug with the last update (November 2012)
2. Open the Control Panel and go to System and Security
3. Next, if you see a red box saying You need to check for updates now, it’s possible you don’t have the latest Windows 8 updates yet
4. Click the button Check for Updates
5. Alright, now reboot your PC and you should be set
6. Try mounting an ISO file
7. Copy the ISO file to your local drive, do NOT mount from an external or network drive
8. If you still get the error “Sorry there was a problem mounting the file” make sure the ISO file is valid
9. Still problems? Download an alternative mounting tool like PowerISO or Daemon Tools
We explained how to mount ISO files in Windows 7 here that guide may be of help to you if you continue to have problems mounting ISO files in Windows 8
Based on 1 votes
Last Modified: November 16, 2012
You love Windows, Gaming and everything digital? Great, we too! We have thousands of great Windows 7 themes, registry tweaks, tutorials, so please use our search box if you look for anything specific.
If you have some awesome desktop themes, tips or want to write for us, then drop us a mail!
Oliver is the founder and lead editor of this site. He is interested in finding new ways to break Windows, find common e.... Full Bio
Contact The Author: support@windows7themes.net 
Need help? Ask a question at our QA site, click the red button to get started:
Solution, at least here. Use regedit to set defaults for *.iso to explorer.exe, for current user in software Microsoft windows currentversion explorer fileexts
In our case, use of various other iso editors apparently confused the system…context menu /right click solutions did not help, but regedit and reboot did.
In my case, the Mount worked fine, the iso’s showed as yet another (virtual) dvd drive, but the system through the error anyway, and the user had to know to ignore it and to look for that virtual drive. no longer, at least here.
sometimes its because that iso copy is set to “sparse”, that’s a whole different thing, a fresh copy (even of the sparse-set one as far as I can tell) resolves it…