Windows 10: Can't mound ISO files after windows update.

Thank you for the plenty of information Cerberus and Kari.
But how we end from "Windows can't mount ISO problem" to "VM can/can't mount ISO" war xD

I'm not using a VM. It's the original windows main system.
Thank you.

 

Have you already tried to copy ISO to another folder as suggested by Fafhrd:

 

Yes stated that in my first post, if copied to any location even same folder, they can be mounted.

 

HMM - I have always had this issue in different VMS in different pcs. I cannot understand why I get it. I searched web and others stated it was a hyper-v issue. I have tried moving it to several locations - always same. I guess it is one of life's mysteries.

My VMS are NTFS and isos are mostly fat32.

No big deal as I can easily get round issue.

 

As I mentioned, I have never had any issues in mounting ISO images on virtual machines, on any host. That's for instance how I upgrade them. Think logically: why on earth would such a basic feature not work on a VM?

 

You are of course correct,but when was MS always logical .

One thing that has always annoyed me is the fact I cannot upgrade a build when it is in a vhd attached to host, but can when it is in a VM. OK, I get round this by attaching vhd to VM, upgrade, then reattach vhd to host, and because Windows 10 is good at sorting drivers, no need to sysprep.

 

As there's this easy workaround which works, the issue really is a minor one although somewhat annoying. If it is a certain Windows update causing this, you could try hiding that update permanently.

The best way to do it using PowerShell PSWindowsUpdate module, see this tutorial for setting up PSWindowsUpdate: Update and Upgrade Windows 10 using PowerShell Windows 10 Installation Upgrade Tutorials

Part Three in above mentioned tutorial shows how to hide unwanted updates.

 

Disk defagmenters do not always manage to defragment all individual files, especially when the files are multi-GB ones.

Windows defrag rarely can defrag large files in a single pass - because when Windows is running, many files are open and not able to be moved, defragmented or deleted - interfering with the consolidation of a large file that may be fragmented by the intercalation of active files.

A boot-time defragmenter will defrag all files usually because Windows has not loaded yet and the majority of files are not opened.

Puran Defrag is one such example and also can defragment individual files on demand from the right-click menu.

Individual file defragmenters are also available from Neosmart and are used in the EasyBCD utility for defragmenting ISO files and VHDs:

From: EasyBCD

UltraDefrag

UltraDefrag is an excellent individual file defragment utility that can be used to quickly group all clusters of a single file. EasyBCD relies on this feature to prepare disk images for booting.
The following files in the EasyBCD distribution are derived from this package and governed by its license:

• bin/udefrag.dll
• bin/udefrag.exe
• bin/udefrag-kernel.dll
• bin/zenwinx.dll

Site: UltraDefrag - An Open Source Defragmenter
License: GPL v2
Source Code: ultradefrag-4.4.0.src.7z

Another defragmenter that can defrag individual files is Contig from Microsoft Sysinternals:

Contig

 

Thanks Kari and Fafhrd
I might uninstall that update, because I'm still suffering form missing drives issue. Which I thought this update solved it.
Getting sick of windows errors/lose files after sleep/restart...

 

Sounds your issue is related to file permissions caused by the latest update.

The system does not have the correct permissions to access the images. As copying the files helps solve the issue, make a copy of any of the non working ISOs and then compare permissions on both. You should see some differences. For instance instead of seeing the System "user" or Administrators "group" as one of the entries in the security tab, you instead see a GUID (a long name consisting of numbers and letters separated by dashes). This means that that particular user/group with that particular GUID does not exist in your system anymore. This issue is caused by bad update/migration of the registry values during the windows update process.

This is a common issue that has happened to me multiple times when updating the system to latest builds/cumulative updates.

Of course the issue could be related to something completely different too.

 

Thought of that, it's something has to do with security preventing me from accessing those files.
I missed with permissions, no matter what change I do there, it didn't work.
But I see that it listed on Microsoft site by other users with certain update, I'm almost certain it's an update issue.
Since my update include that "certain update" causing the problem, but can't be removed since I installed my updates as one package.

Going to wait for another update, hopefully it will fix the problem, otherwise I will roll to older updates and remove this one.

Thank you for the reply *Smile

 

This issue can be manually fixed, but it's tricky. You need FULL permissions for SYSTEM group for your non working files. Those permissions can not be edited in GUI mode. You need to do this using Powershell or CMD.

Easier is to revert the update and see if it helped and then try to update the system to latest cumulative update, which should be newer than the one that caused the error for you.

 

Already messed with permissions nothing helped.
I downloaded and installed the latest update:
2017-07 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4025334)

Still problem persist, looks like Microsoft not bothered fixing their errors, just like Apple blame the users end.

Anyway, the above update merged with older one. Uninstalled the update as whole, now I can access to my files no problem, no need to copy them anymore *Smile
That's why I never use windows update since XP. They break more than fix.

Thank you all for helping me through this *Smile