Guide to building a 64 Bit UEFI Secure Boot WinPE 5.0 CD or USB Flash Drive running TIHome 2014 with or without Disk Director 12

- Anmelden, um Kommentare verfassen zu können

Success :).
THanks for posting the shortcut. I created one easily enough with a spare partition but that will be simple to keep to build a new USB installer with further modifications.
Now I have a working ISO I can start adding the other functions I want.
Still a little curious as to why the network plugin isn't mapping drives based on the cfg file but NET USE works easily enough. I'll just have to see if the gateway details etc are being applied properly so I can use opera for net access.
I might post a quick summary of what I had to change to get this working with windows 7. Some of the ini files needed altering for paths and obviously a couple of other steps were a little different.
I appreciate the help along the way....
- Anmelden, um Kommentare verfassen zu können

Good day :).
I am having to rebuild my WinPE media (had some issues and lost it).
For some reason I was having the same issues as earlier in the thread so I went back to basics.
- reinstalled Win 10 dev kit (not 10.1)
- Extracted install.wim from the Win 10 Pro install advised
- Install of TI 2014 Premium and reinstalled the Media add-on.
- copied the 2 .sys files to \bartPE\x64 as directed from \windows\system32\drivers.
(I note there is a x64 dir that contains these 2 already under \trueimagehome and also copies of them in BartPE\files\drivers)
- adjusted the ini files for 32bit, TI2014 etc as needed.
- added launcher shortcut for TI.
MustangPEbuilder creates the USB just fine. It boots in ok. When I run Acronis I am getting an error code stating that it "cannot Initialise the computer" with the error stating it cannot launch the snapshot library manager.
I can only assume I am seeing some sort of issue with the .sys drivers I am using or snapman.dll (I dont have disk director)??
Any ideas?
Worst case can some kind soul upload the .sys files I require to run this and clarify which files (from what source) should be used to overwrite which locations?
Cheers :)
- Anmelden, um Kommentare verfassen zu können

Here are the file versions and locations you need:
....\TIHome2014\Files\Drivers
snapapi.dll v 4.5.0.2231 419 KB
snapapint.bin 206 KB
snapapint.64.bin 338 KB
....\TIHome2014\Files\Drivers\x64
fltsrv.sys v 1.3.0.2231 114 KB
snapapi.sys v 4.5.0.2231 264 KB
- Anmelden, um Kommentare verfassen zu können

Thanks Mustang.
Those paths you placed.... are they not under the ..\BartPE directory that the Acronis Media add-on creates?
I think you mean Snapman.sys too.... not snapapi?
My file versions are:
snapman.sys 4.50.2231
fltsrv.sys 1.302133
Install.wim is from Win 10 Pro 10240 x64.iso
win 10 ADK ver 10.026624.0
I'm back to getting the "incorrect subsystem" error /sigh.
Incidentally, I used the AcronisPE builder and it works fine. I have to enter in the "NET USE ....." to map my backup network share each time. If I want to have a batch file to run or for that to be performed on boot from the USB what file do I need to edit (or do I enter it as a command line modifier in the Acronis PE builder?)
Ulitmately as long as I can run Acronis and access my shares I'm ok :).
The reason this all came up was I got hit with a cryptolocker.... and with my WinPE USB not working properly I couldn't get at my networked backups (the Acronis rescue DVD doesn't see my network).
- Anmelden, um Kommentare verfassen zu können

Well this is odd.
I now have Acronis working on the WinPE media again.
Changes I made:
1. reinstalled the acronis media add-on
2. moved install.wim to C:\temp instead of mt G:\
3. uninstalled and reinstalled the ADK using the same web install .exe
All of these I had done previously.
New change:
4. changed sequence of plugin activation so PENEt is after the AcronisTI plugin
Incidentally, I now find PENet will not work. Generates an error stating [Unable to Start "TCP/IP registration Compatibility" Service required to work under PE 2.0 environment].
I'm mapping drives using NET command through the start command but I did have PENET working previously.
- Anmelden, um Kommentare verfassen zu können