If you already created the ISO, build a boot UFD. Format the UFD with FAT32, mount the ISO (in Windows 10, double click), copy-paste the ISO contents to the UFD.
Phylock is an early VSS type FileSystem lock that guarantees a locked FileSystem when IFW images your System. What is it that you need to know...?
The link I gave went to a post I made earlier about phylock refusing to lock. I cannot even uninstall it. I read the terabyte wiki, but that did nothing. That's what wanted an opinion on.
Nate, Use VSS if PHYLock doesn't get a lock. You can try Sysinternals Procmon.exe as it might show what is writing to the partition and preventing a lock. I recently resolved why a test computer couldn't get a PHYLock lock. It was a WiFi app constantly writing to the partition. My son's laptop can't use PHYLock and I haven't resolved what is happening. He uses VSS. You can restore a UFD partition image to unallocated Free Space and boot the partition.
Your active VSS is a much better option anyway, especially if it works. Phylock doesn't really provide anything more than VSS does for imaging purposes. If Phylock bothers you being on the System, it can be "stopped" (made inactive) and/or removed via Windows System commands.
Like you, I also built a Win 10 pro system with UEFI, although I confess I really don't know if UEFI is even enabled, as I don't see it under Advanced Options under the advanced Startup menu. All I did was use the TBwinPe builder using defaults to create a recovery USB, so I chose VSS, and I boot from it fine using the legacy USB options from the Windows boot menu F8. Sorry, not a helpful post regarding your phylock issue.
@wat0114 - just so you know... when you image from a Recovery Media, the only LOCKED partition in use will be the RAM-based WinPE environment. All others are not in use, unlocked, and require no locking (via Phylock or VSS) when imaging them from a Recovery Media. Those options only come into play when trying to image under a LIVE Windows System and especially when imaging the Windows partition itself.
There are two interesting things going on here: 1) It seems that phylock isn't even attempting to "run", because it throws up that locking error warning immediately, and 2) Even with VSS it takes IFW more that five minutes to get a lock. This is with nothing writing excessively to the drive, since writing cannot be completely stopped. I don't believe this to be a vss issue since macrium reflect gets a lock right away. Also, does anyone know how to add an entry to the windows bootloader? I want to add a Terabyte option (a la macrium reflect). My MB supports legacy + UEFI, but adding to the BCD doesn't work.
Do these help? https://www.wilderssecurity.com/threads/running-tbwinre-tbwinpe-on-uefi-without-a-boot-disk.383866/ https://www.wilderssecurity.com/threads/running-ifl-on-uefi-without-a-boot-disk.389002/ https://www.wilderssecurity.com/threads/running-ifl-on-bios-without-a-boot-disk.383647/
Thanks Brian. I'll keep trying to re-read those. But I'm pretty confused. It sound like what I want is in the second link; IFL on UEFI. But right of the bat it starts talking about scripts and UDF (what is UDF?). So I'm not sure that's what I'm looking for. That script, it seems to me, aims to provide automation of image creation and restores. That's not what I need. I just need IFL to be a boot option. Or maybe I'm wrong. Can you provide a little context to that thread?
Nate, UFD is USB flash drive. The second link is for you but you don't need scripts if you just want to run IFL from the SSD (or HD). Basically you create a UFD with the Boot Settings you desire. Probably Normal/Normal for you. Then boot the UFD and use Partition Work to create 100 MB of Free Space on your SSD by resizing a partition. Then use IFL to Copy the UFD IFL partition to the 100 MB of Free Space. Almost done. Restart and have a look at your "BIOS" Boot Menu. Do you have a boot item that corresponds to your IFL partition? If so then try it. If not then we'll need to discuss EasyUEFI.
I think you guys are getting some crossed wires here. Nate is referring to UFD which is a new standard (well, not that new) for BOOTable media, usually in the form of CD/DVD... it's not referring to UFD (USB Flash drives).
Thanks Brian. That worked like a charm!! Awesomeness. Now I just need to rename the entry. How would I do that?
Nate, you can rename the entry with EasyUEFI (Free)... http://www.easyuefi.com/index-us.html It's worth having as you can select to boot IFL (on next boot) while in Windows.
Nate, you can remove the IFL drive letter in Windows if you like. I prefer not to have the drive letter. You can use the same method to add a TBWinRE partition to the SSD if that is of interest. Use 450 MB of Free Space.
It was? I just wanted to know the context of that thread (link #2). Regardless, thanks Brian and TRF. I have a lot to learn still. One thing I find curious is that EasyUEFI doesn't seem to save it's settings. If I edit an entry. The changes are not seen in the boot menu. I can even edt the entry within EasyUEFI and refresh it and it reverts. Once it even duplicated the entry with the original name.
You typed UDF instead of UFD. Mine does. My EasyUEFI "Description" in the Edit menu is reflected in the "BIOS" boot menu.
Brian... quick question. I vaguely remember you mentioning that the restored partition positions made no difference when it came to the "active" SYSTEM RESERVED PARTITION, the Windows C:\ partition and the Windows RECOVERY PARTITION (and with UEFI, the EFI, I think). Is this a fact, and if so, does it apply to Legacy-MBR configurations? I ask, primarily, because the upcoming W10 CREATOR'S UPDATE is carving up my Windows C:\ partition to make room for yet another Windows RECOVERY partition at the end of the old C:\. This makes my resizing/repositioning options limited in some cases unless I can break them all up again and re-stack them during an image restoration.
