Win10XPE & Win10PESE mklink on X-Drive

Hello,

I don't know, I think it's my first post here, but I read here very often during the last years.

Introduction to myself, I use  Win*PE[SE] Projects from "theOven.org" a long time. But the last 5 years I was extremly satisfied with my 8.1 Multiboot USB Build, everything worked for me
up to now. My Build contains EFI-8.1 Boot/ BIOS Grub4DOS Boot with multiple PE Boo*.wim files (Minimal cmd boot, Win7RE x86/amd64, a nearly complete 8.1 x86/amd64 PESE), many ISO-files-Boot on a via BootICE partitioned USB stick. Via a disk imaging solution I distribute this stick to all our technicians at work.
The stick is used for installing, backup, data recovery, and has also many capabilites to be used as all day system, do Office work, configure devices, etc.
Most Programs are used "portable" from the second NTFS Partition. I also wrote some own extensions, that load e.g. additional Driver, if needed for Networking during startup from the NTFS Partition, create shortcuts for the portable programs, etc.

Now there is a big need to support M2-NVMe-SSDs, that leeds to Win10*PE*.

And I also store all data files, docs, on a special user folder on that NTFS partition. At this point I use MS "mklink /D link target" to redirect folders on the x-drive.
(e.g. Documents, Pictures, Music, but also folders where the program must resist on "%SystemDrive%\Program Files" and not beyond "Y:\Programs\"
This worked for me great on 7PESE, 8PESE, and 81PESE. But now I get "This device does not support symbolic links" with /D option or "incorrect [or forbidden #not sure my build is German] function" for /J option of mklink.

I already tried to replace "wimlib-image.exe" with MS "imagex.exe" in XPE build scripts (CreateISO.script), I tried imagex from 10, 8.1 and 7 with parameters from old projects as supported
by the used imagex versions. Builds are always booting and working, but symlinks or junctions still (I also tried junction.exe) not applicable on x-drive.
I also was not able to find some (for me) helpful documentation on creating symlinks in a RAM booted PE Wim on the net.

The mklink problem stays also with Win10PESE project.

Any hints on this topic would be very useful and appreciated.

Thanks in advance.

Win10PE from any project does not support junctions or symbolic links..

You will need to use Win8Embedded FBWF.sys in your Win10XPE or Win10PESE build to add support for junctions and symlinks, this can be unstable for certain applications but under controlled circumstances (not using the affected applications) it can be made to run well..  I know it affects Regshot2 and I think Runscanner if you use Win8Embedded fbwf.sys

Place the file in Windows\System32\Drivers

You will need to use Win8Embedded FBWF.sys in your Win10XPE

Win10XPE supports  /widows/system32/drivers/fbwf.sys  with a max WinPECacheThreshold of 2048mb supported on x64

Yes but it does not support mklink

mklink creates junctions or symbolic links:  https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/mklink

It appears @someone is trying to figure out why it isn't working in Win10PESE or XPE - the reason for this is because it has not been supported since Win8PE - Which is why using a Win8Embedded fbwf.sys instead of the Win10 fbwf.sys from the install media will solve the problem...

It is used for redirection of paths (fbwf.sys affects this as well as x: size)

BTW @someone, you can use the registry to redirect most paths outside of the WIM including desktop/documents/pictures/videos/downloads etc

Hi someone,

an idea to test:

create Test.vhd at x:
Mount Test.vhd to a drive letter, and create junction to the shortcut folder on your portable usb...
unumount Test.vhd
Mount Test.vhd to a folder -> ex: A sub folder Under StartMenu
-->
If this works, you have a working solution to StartMenu junction from your usb StartMenu to pe startmenu.

*
If this works share your .cmd .txt codes

*
If this works
You can use similar trick with X:\Program Files\
....

ps: I also use junction a lot on normal pc 

Yes but it does not support mklink

Thanks for info Bob.Omb

BTW @someone, you can use the registry to redirect most paths outside of the WIM including desktop/documents/pictures/videos/downloads etc

This sounds like a better way for StartMenu etc. 

ps: I use this for my pc. All StartMenu , Desktop  etc. at D:\ ... 

Hi,

thanks for all your answers in that short time!
Thanks for clearing out it is an internal driver problem with winPE, not with the build tools and I can stop to stick in building loops.

I think using FBWF.sys from my older Win81PESE Builds with Win10*PE will be the last attempt, that I will try only, if I can't get other workarounds do the job.
(Or is there a windows 10 based FBWF.sys that can do the job? But in the past even some programs like Libre Office didn't like my symlinks.)

For standard places (documents, pictures,..) I think I will use registry redirection. (Libre/Open Office didn't like the links either.)
For the few software folders I think I will write a program, that copies necessary folders on PE boot, start it, monitors the folder for changes and sync that back.

At the moment these are some on demand Antivirus scanners, that only will run from %ProgramFiles%, a tool from sophos and MacAfee Stinger.
concret Realprotect as a part of Stinger. Very handy to have a realtime Checker in PE in case some noobs are using my PE stick.

Again thanks for all your instand replies.
It was very impressive to me to get instant answers from the "who is who" of PE building.

Hi Bob.Omg

It appears @someone is trying to figure out why it isn't working in Win10PESE or XPE - the reason for this is because it has not been supported since Win8PE - Which is why using a Win8Embedded fbwf.sys instead of the Win10 fbwf.sys from the install media will solve the problem...

An idea:

I do not know this plugin well.
Is it good idea to add an option to plugin to provide custom fbwf.sys ?

See:
(not tested but It will give you the idea)
https://www.dropbox.com/s/dk183a9opf2pkdu/2-Config_Mod_201810271241.7z?dl=0

The only one I have tested is Win8Embedded fbwf.sys in Win10PE

@Lancelot, yes an option to add a custom(Win8Embedded) fbwf.sys would be useful..

I very much hope I will have time this weekend to help with this, I got called into an emergency at work last night (All night  ) and have to go back in now

@Lancelot, yes an option to add a custom(Win8Embedded) fbwf.sys would be useful..

I believe that is it
http-----s://www.microsoft.com/en-us/download/details.aspx?id=37019

I will improve codes (different architecture, version check with Win8Embedded etc.) and update plugin. 
Tomorrow I hope.. Limited free time ...

I very much hope I will have time this weekend to help with this, I got called into an emergency at work last night (All night  ) and have to go back in now

Yes I hoped same way too this weekend,
 but things came up again today.... and life goes....

Hi all,

Just updated 2 - Shell & Config

with "Provide Custom fbwf.sys" button.
...\x86\fbwf.sys
...\x64\fbwf.sys

Ps:
Bob.Omb mentioned Win8Embedded has fbwf.sys version 2.0.99.0 --> 2.0.99.0 is older which is still useful with Win10PESE ...
Windows 8 embedded have 6.3.9600.16384

Hi @Lancelot

Could you adapt this script for Win10XPE? To be able to prove it. I'm glad to see you in this forum again. I saw your comments a few days ago. You were always attentive and helping.
Thank you so much for everything.

Could you adapt this script for Win10XPE? To be able to prove it.

I will adapt in a way in some future. 

For now, you can manually add fbwf.sys to the folder:
...\Win10XPE\Custom\x64\Drivers\
Edit:
Or Better I guess:
Win10XPE\"Build Core" -> "Open Custom Folder"
...\W10XPE\Custom\x64\AdditionalFiles\Windows\System32\drivers\

Edit:
Or Better I guess:
Win10XPE\"Build Core" -> "Open Custom Folder"
...\W10XPE\Custom\x64\AdditionalFiles\Windows\System32\drivers\

Thank you so much @Lancelot. I wiil try it now. 

Thank you so much @Lancelot. I wiil try it now. 

All Credits to Bob.Omb,
I only follow Bob.Omb Reply 3 http://TheOven.org/index.php?topic=2613.msg28655#msg28655

Let us know the results.   

Hi,
I want to share my final solution .

I went back to mklink with Win 8 emb. FBWF.SYS Version on 10XPE, because I can't get folder redirection get to work during boot time changes. (Changing registry values from pecmd during subs preshell, loadshell and postshell.)
 

Folder redirection works when configured during build time hard coded in registry.
But because I use my boot.wim also for PXE boot, my intention is to switch folders during boot to folders on Y-drive on USB stick when booted locally.

Thanks again for your help.

Someone here tought me this 

JFX 

Hi all,

Just updated 2 - Shell & Config

with "Provide Custom fbwf.sys" button.
...\x86\fbwf.sys
...\x64\fbwf.sys

Ps:
Bob.Omb mentioned Win8Embedded has fbwf.sys version 2.0.99.0

I'm not able to find version 2.0.99.0
The file I extracted from Win8embedded (https://www.microsoft.com/en-us/download/details.aspx?id=37019) is version 6.2.9200.16384...
So I downloaded Windows 8.1 Embedded and extracted the file from there. The version is 6.3.9600.16384
Where the hell do I get the right files? Or can i just take these files?

Hi, M-M-C.
Look at this topic, there is a plugin with the necessary driver.