armond I do not have any problem with the computer. For some reason, the system does not allow some action if the image is mounted on a system disk. When you change the mount path to another drive (not system), this problem does not exist. This may be due to account restrictions with administrator privileges (an embedded Administrator account has more rights than regular)
I always use my C:\ drive = systemdisk for mounting wim's ("c:\mount" to be specific for manual mounts, and the default one of the script when using it), by using the W10UI script or manually, never have any problem. It must be something local on your system that's causing the problems.
Are you using more than 1 hard drive? or all your partitions are on just one hard drive? Don't think so. I can create a folder in my C: drive, copy stuff in it, and do the rest. No problems at all.
Can anyone give me a list of updates needed to be integrated for en_windows_10_enterprise_2016_ltsb_n_x64_dvd_9057894? Thanks in advance.
Well that's a blunder, update installed and prompted for a restart so since the last few updates have somehow asked for a restart even after finishing installation until updates are paused and then resumed so the OS forcefully re-checks and finds everything OK I decide to pause updates after it's done with the initial step before reboot. So the OS then finds the already installed update and decides to start the entire process over, fails and on reboot it complaints the update couldn't be installed because the system was powered off and it's time to just start over from the beginning. Well at least I know not to do that again. Oops. Seems to be some minor fixes going by the Windows 10 update history page, being cumulative though it still takes a while to process since it has to compare against some thousand or so files. Going to be a longer night than I thought though it's a learning experience if nothing else.
Yeah. I'm on the release preview branch so the first cumulative and then the first public update to .42 I think it was had the issue where it listed as still pending. I see now that this is fixed and this entire little attempt to be smart and get that out of the way early since a pause and resume prompts for a immediate update check well that could have been avoided. Didn't expect that to bug the entire process, at least it worked fine during the second attempt and it's now up to date to version 17134.82 EDIT: Well I'm probably not explaining very well, everything is working now but that caught me by surprise. EDIT: Or am I confusing it with 17133.x and it getting a update, well it's after midnight so I'm pretty tired but I wanted to get this out of the way, really hadn't expected a update outside of the usual patch Tuesday once a month routine and even release preview updates are not too frequent anymore.