Kullenen_Ask
Content Type
Profiles
Forums
Events
Posts posted by Kullenen_Ask
-
-
Actually the best thing would be to use the original non-PE SYSTEM hive for WinPE, which contains system services and more. I tried tweaking that in almost any imaginable way, but did not completely boot. It just froze with a black screen after all boot drivers where loaded.
If it is possible (i know how much it is difficult because i need to change lots of stuff sometimes) can you write what did you change at non-PE SYSTEM hive. For me only [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services] can be enough too. Because i couldn't achive it too start all services. I disabled almost all services that can be problematic with to change start-up type. Always blue-screen. I know the problem is there because it can boot with other services stuff.
It just froze with a black screen after all boot drivers where loaded
Try to clean everything under [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Lsa\Audit].
1 tip when working with hives like that. Sometimes it's easier to export separate parts from the original hive into reg files. Unload the original and load up a new empty hive where you can import all the reg files. This way you don't have to fight with permissions, which can be a pain in the back, and you can delete anything you want.
Yes. There is 2 way to make such a system. First is to export all hives as reg file and after import to a empty hive and clean all permissions. Second way is to use all hives without loosing permissions. If deleting is problem, you can delete keys with special registry softwares. Forexample deleting something from ENUM key is very difficult. I use "Registrar Registry Manager". There are advantages and disadvantages of both ways.
0 -
I forgot where was the winload.exe patching manuals of you for to use different hives in same wim. Probably they were at sanbarrow joakim section. It was surprising for me that to see differences very small. Also system.hiv difference is not so much big. I do not have much knowledge about hardlinks but also i didn't see any problem in normal windows and winpe file structure because of hardlinks. And what is first impression about if it booted as winpe with all software.hiv and all files of a normal setup? What works and what not?
0 -
If it can successfull pass that phase and you can see mouse cursor without bsod (if all services start) and it freeze there. It means it need security,sam hives of winpe. Need change windows 7 ones with winpe ones. I do not think winload or explorer.exe will care your registry entries without wpeutil, wpeshell,wininit files.
0 -
Normally your system.hiv should have X: locations. Did you changed all that to C: locations too? Did you removed fbwf services (as i understand you do not load to ram). I think also you added winpe specific files???
Try to rename or remove "oobe,panther" folders from your windows. as it already working system you will not loose anything i think.
0 -
what is the bsod, crash or reboot? i spend lots of time on it and know a few reasons. wim in your hands has all the windows 7 hives that the problematic keys removed and all C: changed to X: If do not change it will be same like you do.
be sure to remove or disable all prefetch, readyboost,hybernation.
As i understand your winload lets you select windows 7 system.hiv and winpe system.hiv. When you select winpe it use normal windows 7 software.hiv. and winpe system.hiv to boot?
0 -
I found this source code when i was surfing in a chineese forum. Maybe it can be usefull for add/change something. To make a loader. We can run more services and load much drivers with custom WinPeShl.exe. I do not have coding knowledge. Ideas wellcome.
WinPeShl.exe,WpeInit.exe,WpeUtil.Dll:
------------------------------------------------------------------------------------------------------------
WinPeShl.exe:
wWinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPWSTR lpCmdLine, int nShowCmd)
{
if ( QueryRegValue(HKEY_LOCAL_MACHINE, L"SOFTWARE\\microsoft\\windows nt\\currentversion\\WinPE", L"ShellLogPath") )
CreateLogFile( );
else
CreateLogFile(L"winpeshl.log");
Message("Windows PE Shell beginning execution");
SetCursors();
InitSys();
LoadExec(L"%SystemRoot%\\system32\\winpeshl.ini")
}
InitSys()
{
LoadLocalFonts();
QueryRegValue(HKEY_LOCAL_MACHINE, L"Software\\Microsoft\\Windows NT\\CurrentVersion\\WinPE", L"CustomBackground") )
SystemParametersInfoW();
WpeInstallServicePrivileges();
WpeInstallServicesSecurityTemplate();
hObject = CreateEventW((LPSECURITY_ATTRIBUTES)v9, 1, v9, L"Global\\EVENT_WINPE_REMSTOR");
hHandle = CreateThread((LPSECURITY_ATTRIBUTES)v9, v9, StartAddress, (LPVOID)v9, v9, &ThreadId);
result = (void *)QueryRegValue01(
HKEY_LOCAL_MACHINE,
L"SYSTEM\\CurrentControlSet\\Control\\WMI\\Autologger\\WinPEFileTrace",
L"Start");
if ( result )
{
v30 = v9;
sub_1006847(67108864, L"Profiling is enabled; initializing run-time profiler.", ST18_4_0);
result = CreateThread((LPSECURITY_ATTRIBUTES)v9, v9, SerializeAppProfile, (LPVOID)v9, v9, &v30);
dword_100B040 = (int)result;
}
}
-----------------------------------------------------------------------------------------------------------------------
WpeInit.exe:
int wWinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPWSTR lpCmdLine, int nShowCmd)
{
if ( lpCmdLine )
UnattendFindFileFromCmdLine();
else
{
wttime = GetTickCount();
WpeWaitForRemovableStorage();
Waitime = GetTickCount() - wttime;
hLogFile = XLOG(L"wpeinit.log");
if (UnattendFindAnswerFile()){
//Checkit;
}
else
WriteLog(hLogFile,"No unattend file was found; WPEINIT is using default settings to initialize WinPE" );
if ( Waitime )
WriteLog(hLogFile, "Spent Waitime%ums initializing removable media before unattend search" );
}
result = WpeActuateUnattendSettings();
//CleanUp
return result;
}
-----------------------------------------------------------------------------------------------------------------------
WpeUtil.Dll:
WpeActuateUnattendSettings()
{
UnattendDisplay();
UnattendCompterName();
UnattendPageFile();
UnattendOC();
UnattendNet();
UnattendFireWall();
UnattendRunSynchronous();
UnattendRunASyncs();
UnattendRestart();
}
UnattendNet()
{
if(NetNotEnable == WpeQueryNetworkStatus()
MyInitNetWork();
}
MyInitNetWork()
{
WpeInitializeNetworkComponents();
WpeInitializeNetworkDrivers();
}
WpeInitializeNetworkComponents()
{
Install MS_MSCLIENT
Install MS_NETBIOS
Install MS_SMB
Install MS_TCPIP6
Install MS_TCPIP
StartService dhcp
StartService lmhosts
StartService ikeext
StartService mpssvc
//lanmanStation...
}
WpeInitializeNetworkDrivers()
{
WpeInitializeDriversOfClass();
}
WpeInitializeDriversOfClass(int a1, int a2)
{
//EnumDevice then DiInstallDevice();
}0 -
i did not understand any what you talk about. it this a wim that boot? or you try to boot windows install as winpe? is it boots to ram? how can it will not write hives anything?
0 -
Directory structure.
Directory of D:\DS\
D:\DS\boot
D:\DS\boot\fonts
D:\DS\boot\tr-tr
D:\DS\efi
D:\DS\efi\microsoft
D:\DS\efi\microsoft\boot
D:\DS\efi\microsoft\boot\fonts
D:\DS\sources
D:\DS\
=====
bootmgr 374 KB
Total 1 file(s); Size: 383562 Byte(s)
D:\DS\boot
=========
bcd 256 KB
boot.sdi 3096 KB
bootfix.bin 1 KB
bootsect.exe 95 KB
etfsboot.com 4 KB
memtest.exe 474 KB
Total 6 file(s); Size: 4020288 Byte(s)
D:\DS\boot\fonts
===============
wgl4_boot.ttf 46 KB
Total 1 file(s); Size: 47452 Byte(s)
D:\DS\boot\tr-tr
===============
bootsect.exe.mui 15 KB
Total 1 file(s); Size: 15872 Byte(s)
D:\DS\efi
========
Total 0 file(s); Size: 0 Byte(s)
D:\DS\efi\microsoft
==================
Total 0 file(s); Size: 0 Byte(s)
D:\DS\efi\microsoft\boot
=======================
bcd 256 KB
Total 1 file(s); Size: 262144 Byte(s)
D:\DS\efi\microsoft\boot\fonts
=============================
wgl4_boot.ttf 46 KB
Total 1 file(s); Size: 47452 Byte(s)
D:\DS\sources
============
boot.wim 140919 KB
install.wim 426805 KB
Setup.exe 238 KB
Total 3 file(s); Size: 581594533 Byte(s)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Total 8 folder(s); 14 file(s)
Total files size: 573 MB; 572628 KB; 586371303 Bytes
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^Fundemantaly;
*Take boot.wim of normal install. Put Embedded License directories inside boot.wim. Change a few related files (product.ini,setup.cfg... as i remember) with embedded. Also need to put setup.exe inside sources folder. If you can see embedded eula at setup and it continue with disk partitioning everything ok until here.
*My packages integrated.
pause
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\lp.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Application-UX.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-AppSupport-ComBase.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-AppSupport-ComPlus.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-AppSupport-Legacy.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-AV-Core.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-BootEnv.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Branding-Embedded-Neutral-Package.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-DeviceFoundation.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Diagnostics-Common.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-DirectoryServices-AD.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-DriverFoundation.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-File-Compression.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Font-Western-Required.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-FS-Advanced.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-FS-Core.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-FS-SMB.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Graphics-Platform.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-IE-Core.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-IE-Explorer.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-IE-Foundation.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-61883.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-acpipmi.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-adp94xx.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-adpahci.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-adpu320.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-amdsata.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-amdsbs.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-arc.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-arcsas.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-atiilhag.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-brmfport.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-bth.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-bthmtpenum.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-bthpan.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-bthspp.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-circlass.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-compositebus.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-digitalmediadevice.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-djsvs.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-dot4.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-dot4prt.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ehstorcertdrv.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-elxstor.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-gameport.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-hdaudio.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-hdaudss.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-hidbth.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-hidir.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-hidirkbd.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-hpsamd.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-iastorv.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-igdlh.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-iirsp.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-image.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-iscsi.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ks.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-kscaptur.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ksfilter.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-lsi_fc.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-lsi_sas.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-lsi_sas2.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-lsi_scsi.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdm3com.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmagrm.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmagrs.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmbtmdm.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmcodex.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmcpq.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmcxav3.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmcxpv3.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmgl001.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmgl002.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmgl003.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmgl004.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmgl005.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmgl006.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmgl007.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmgl009.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmgl010.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmgsm.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmirmdm.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmmoto1.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmnokia.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmrock.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmrock3.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmusrgl.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmusrk1.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmwhql0.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmzyxel.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-megasas.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-megasr.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mf.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-msclmd.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-msdv.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-multiprt.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-net1k32.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-net1q32.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-net1y32.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-net8187bv32.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-net8187se86.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netbc6.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netbxndx.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netgb6.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netimm.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netirda.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netk57x.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netl160x.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netl1c86.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netl1e86.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netl260x.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netmyk01.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netnvmx.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netr28.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netr28u.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netr73.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-nettun.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netvfx86.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netvg62.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netvwifibus.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netw5v32.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netxe32.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-nfrd960.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ntprint.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-nvraid.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-nv_lh.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-pcmcia.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-prnge001.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-qd3x86.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ql2300.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ql40xx.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-rawsilo.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-rndiscmp.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-scrawpdo.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-sdbus.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-sensorsalsdriver.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-sffdisk.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-sisraid2.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-sisraid4.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-stexstor.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-sti.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-tape.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-tdibth.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-tpm.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-transfercable.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-tsprint.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ts_generic.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ts_wpdmtp.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-umpass.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-usbvideo.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-vhdmp.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-vsmraid.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-v_mscdsc.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wave.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wceisvista.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wdmaudio.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wdma_usb.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-windowssideshowenhanceddriver.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-winusb.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wnetvsc.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wpdcomp.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wpdfs.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wpdmtp.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wpdmtphw.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ws3cap.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wsdprint.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wstorflt.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wstorvsc.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wudfusbcciddriver.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wvmbus.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wvmic.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Installers-MSI.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Interface-Explorer.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Lpk-Setup.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-MDAC.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Media-Support.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-MediaPlayer.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-MobilePC.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-NetFx20.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-NetFx20Client.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-Base.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-BITS.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-Bluetooth.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-Devices.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-EAP.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-Foundation.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-IAS.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-NASC.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-QoS.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-RAS.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-Services.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Peer-To-Peer-Networking.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Photos-Viewer.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-PowerManagement.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-PremiumCodecs-MPEG2-Decoder.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-PremiumCodecs-MPEG2andDolbyDecoder.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-PremiumCodecs-MPEG3.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-PremiumCodecs-MPEG4.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-PremiumCodecs-WMV.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Printing.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Search-Indexing.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Security-Base.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Security-Credentials.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Security-SecureStartUp.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Security-TPM.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Servicing-UI.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Servicing-WUSA.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Shell-Accessories.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Shell-Core.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Shell-Foundation.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-SystemControlPanel.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-SystemManagement-AdminTools.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-SystemManagement-MMC.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-SystemManagement-Utilities.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-SystemManagement-WMI.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-TapiClient.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-TerminalServicesClient.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-usb.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-VSS-Foundation.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-VSS-Service.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Wireless.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Device-UX.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-Diagnostics.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-RemoteAssistance.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-RPC.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Security-ForApplications.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-SensorAndLocation.cab"
Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-SystemManagement-GroupPolicy.cab"
pause*I used predefined template (ie,mediaplayer,remote desktop) with embedded image manager. Added my desired driver packages for most wide range hadware support. Added a few more feature packages for to give full desktop experience. Checked dependencies. Found my natural language lp.cab (i think it was only a lip because i had lots of mui missing added manually. English users will be very lucky at this part.
*There is embedded setup.exe inside install.wim windows\system32\oobe folder. I changed that folder with normal ultimate files. Maybe do not need i don't know.
*If you change windows\branding with ultimate files you will have complately ultimate customized screens at setup.
*At setup at the end of finish (maybe %98) it was suddenly crashing and do not continue. I tried the trick shift + f10 manually run oobe with no luck. It was look like same problem with extreme vlite setups. I investigated long logs I was hopeless because so many complex stuff there and want to use my luck. Main errors was ndis_wan, mspppoe errors. From my winpe experiences i fixed them with copy rasman, pppoe, files (telephony.cpl,dialer, tapiui.dll, some inf and sys files.) Most of stuf was only mui missing.
THE MAIN REASON was i saw in log file that (*lprprinting* advanced installer failed ) error. I copied 3 folders and 3 manifests to winsxs folder and wadaaaa. Now setup complates successfully. It means after vlite extreme removal some neeeded winsxs files missing makes setup unfinishable. Missing folders writes inside windows\panther\unattend-gc\setup.log.
*I saw that embedded has windows\system32\spp\tokens\pkeyconfig_embedded.xrms and ultimate only uses pkeycpnfig.xrms. I copied ultimate xrms to there too. Alsa other ultimate license files under that spp folders.
At the end. All setup it writes ultimate edition. At system control panel writes ultimate ed. But when checked updates it founds embedded updates
Also that problem maybe solved but i do not want to spend time for it. Good part it accept embedded serials and also ultimate edition serials same time. Only problem for me i can change background and use themes when it is unactivated and embedded trial but when i fully activate as ultimate ed. it says i do not have license for personalization and it shows blank screen to anytime upgrade. Also when it is ultimate edition it can search for updates but it says there is no update for my system Updates no important for me because i am not fun of updates and i am glad it doesnt find any for me. But need to solve personalization license issue. Ultimate editions how can need extra license for themes as starter edition i do not know.Now it is more small then a xp cd. and works normal with very small problems. I can not run eudcedit and charmap. Eventviewer there are only small errors that are acceptable (eventwiever works normal with everything) and everything looks normal like it should be.
I made everything to stay it servicable. I did not tested but it should work. It means i can integrate .net 3.0 and have that support in 3 minutes in my install.wim with dism. Also any other packages.
Just add and use your own custom system without hard works with vlite. spending lots of time removing components.0 -
my image size is install.wim=416mb
vlite never used. i started from windows embedded standart 7 base install.wim. added my desired packages. converted it to work with windows 7 setup.exe (most difficult part was this, because embedded setup is componentized my install.wim can used with windows 7 normal setup
And there is lots of stuff ready to remove !!!! (Really)
This wim doesn't have .net3.0,3.5 but eventviewer, all mmc snapins, taskscheduler, aero (with transparency) works. Homegroup wireless, bitlocker all stays.
0 -
I tested and it doesn't show your web page. As wiki says
As of April 2010[update], Internet Explorer, up to and including IE8, the latest release, is the only current major browser not to provide native SVG support, although native support is partially available in Internet Explorer 9 Platform Preview[53]: Current IE versions require a plug-in to render SVG content.
I didn't try to download and install a plug-in. It can not show also nature ie8 doesn't support it without using 3rd party plug-ins.
0 -
I arrenged everything to work x64bit only. Also x64 bit of mediaplayer works and default player. Program Files x86 complately empty. For flash support i installed flashplayer_square_p2_64bit_activex_092710.exe. I don't know what you mean with SVG? What is it's long name or meaning?
It was very difficult way for me to build everything x64. Because when you investigate registry deeply also you see that Microsoft doesn't support x64 environment much. It is designed to use iex86 and mpx86 mostly. I think it is a middle operating sytem between x86 to x64 transpassing until everybody decide to use x64 environments and x64 software supoort gets enough level. If i decided to build on x86 programs it would be much easy. I am not used to use x64 operating systems.
Before i decide i thought "If i build x64 why not everything be x64?" Maybe it could get me rid of lots of x86 files and smaller size. Because when i use iex86 and mpx86 i will need to put all mediafoundation, image system, codecs of x86 inside it too. Also now forexample media player uses some files from x86 folder but i think enough less amount. But understand that when somebody wants to use mostly x86 programs in a x64 winpe he should better prefer to use x86 winpe.
I think only aim of the people that desire to use x64 winpe is they want to get rid of more then 4gb ram limitation. For such people better thing is to use core x64 files and design winpe to work on x86 files mostly. But if somebody needs only specific x64 programs to run under winpe it is better to have full x64 support one.
In this winpe forexample i can not see eula screens. First i thouht i have got some missing x86 msthml.dll, mshta.dll, vbscript, jscript, ... files but i get bored to work only for it.
There is twice of everything in x64 environment. As well as files also there is a complate mirror of registry for x86 bit. Probably also 2 regsvr files should exist. One of it should be under system32 folder and other one should be under syswow64 folder. If you write regsvr32 probably it will use x64 one default and it will not let you register a x86 file. Did you try to write regsvr command with path spesific? Foreample "X:\windows\syswow64\regsvr32.exe file.ocx" But you should know that also x86 Flash.ocx can not be registered under x86 environment. Flash.ocx do not accept to be registered manually. Because of that i use installer always.
Maybe you can use a way i use sometimes. Install or register what you want on your own machine, track registry difference and add your winpe manually.
0 -
Anybody knows how to run device manager "refresh" button by command line. I need something like "RunDll32.exe Syssetup.dll,UpdatePnpDeviceDrivers" for to force PnP Enumeration but it doesn't work on windows 7.
0 -
Yes i solved but i don't know how. Now i have a 321mb base iso. It has all the files from 120mb base boot.wim plus all the files for wireless,networking,explorer shell etc... I didn't delete anything from boot.wim because i want it stay optimizable. Now this 321mb base wim is optimizable. It means i can add as much as want, boot, run the desired feature, take the profilling list and have the minimal file list for that function. From this 321mb wim i added .net2.0 +intel,nvdia,ati drivers, directx/opengl (game functionality) and nearly all mmc stuff and it is 380mb now.
i didn't do anything for iefix & wmvfix. just it was working. When you boot you will see my network error. Maybe you can solve and find the reason
0 -
Investigate this Procmon log file. I made remote desktop from inside winpe to same winpe. You will have idea some of registry and all needed files. It will probably not help DameWare MiniRemote Control. It is another software that will probably not need all microsoft remote desktop registry and files. Different things.
http://www.megaupload.com/?d=F72JQJJ0
Procmon.exe /OpenLog Logfile.PMLDownload procmon from here
I thought RDP shouldn't be too hard if you just provide the filenames needed from the full win7 media
-False. Have you seen anybody or any other topic or something that anybody get remote desktop to work under winpe? (I talk about server. Not client.)
Also if you provide some info for the n00b how to modify those registery settings and what settings are needed for RDP.
-Do you know how many services that start with RDP* under system\controlset\services?
Theese files need for most of remote connection programs to work
IPHLPAPI.DLL, winnsi.dll, bcryptprimitives.dll, ncrypt.dll,bcrypt.dll,msasn1.dll,oleaccrc.dll,oleacc.dll
0 -
It is so complicated that better to use teamviewer to remote connect. I don't put to my builds anymore or work on it at least 6 months. You will need so many rdp services, rdp files, terminal services, secondary/user logon (i think my minimal winpe can connect remote at first page was 360mb) Also after boot need to start all services it could to connect. If i start to explain need to rewrite all 7 pages and winpe building instructions. If you ask more simpler questions i can try to help better.
0 -
You should try to demand help on wimbs another forum thread. There is more active about such support stuff.
0 -
Pop up the warning error message after start the service by manual:
"The operation couldn't be completed ,the executable program that this service is configured to run in does not implement the service."
Meaning of this error is there are no "AudioEndpointBuilder","Audiosrv" entries under software\windowsnt\svchost key. Could be also there is no sub services that theese services depend to doesn't exist under svchost registry.
Also add what i said.
Also add mmcss service to your winpe services registry and svchost. And add software\multimedia
0 -
I couldn't find the below register key in the win7 system , So i don't know how to write the sub key information from "AllowStart\AudioEndpointBuilder" ,"Setup\AllowStart\AudioSrv"
[HKEY_LOCAL_MACHINE\SYSTEM_00\Setup\AllowStart\AudioEndpointBuilder]
[HKEY_LOCAL_MACHINE\SYSTEM_00\Setup\AllowStart\AudioSrv]
Just create empty keys. There are a few entries in there should be like them. Very easy. You can add mmcss service too
reg.exe import AudioSrv.reg ; (was copied from win7 system)
Did you change RequiredPrivileges to "SeChangeNotifyPrivilege" only on audiosrv.??? Mount system hive and browse to audiosrv. You will see RequiredPrivileges key in there. There are 3 items. Delete last 2 and left
SeChangeNotifyPrivilege only.
and install the wdmaudio.inf ,hdaudio.inf,hdaudiobus.inf used the dism.exe in offline mode.
Also add ks.inf. Did you offline integrated also your sound cards drivers? I don't think offline adding audio drivers will be usefull. It always continue to complain not to find files about "drmk.sys,drmkaud.sys,portcls.sys,sysfxui,etc." in inf folder. It shouldn't complain and search sys files in inf folder. If you don't want to edit inf files. add all sys dll files from system32\driverstore\filerepisotry\*ks.inf*;*wdmaudio.inf*;*hdaudio*;*hdaudiobus.inf * etc to system32\inf folder too. Thats why i comment out cpyfiles sections.
Also add mmcss service to your winpe services registry and svchost. And add software\multimedia
There are so many parameters. You can not have audio only adding your soundcard drivers offline with dism. Also winpe will not load hardware drivers automatic else then networkcard. First when you run taskmgr.exe from command prompt you should see 3 audio services in the list. Then select them to run from right click, see all running or work to get them run. After try to load your soundcard.
Download makepe3.exe and browse inside with winrar under folder structure you will find the audio related inf and sys files. add them to you winpe structure.
0 -
why need sound on dos shell?
*did you add wdma_usb.inf, wdmaudio.inf. add the files mentioned in this inf files to related folders. comment out cpyfiles sections with comma ";" or use infcachebuilder commandline tool
*add
[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\services\AudioEndpointBuilder]
[HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\services\AudioSrv]
services
*change RequiredPrivileges to "SeChangeNotifyPrivilege" only on audiosrv.
*add AudioEndpointBuilder and AudioSrv to
[HKEY_LOCAL_MACHINE\SOFTWARE_00\Microsoft\Windows NT\CurrentVersion\Svchost]
*add
[HKEY_LOCAL_MACHINE\SYSTEM_00\Setup\AllowStart\AudioEndpointBuilder]
[HKEY_LOCAL_MACHINE\SYSTEM_00\Setup\AllowStart\AudioSrv]
theese are manuel methods. and i don't know how you will load sound card drivers in command shell. maybe can use inf loading and hwpnp. why don't you build with winpe builders?
0 -
No. Doesn't interact. Will not crash if you have all inf and drivers for services start 0,1,2. I didn't see you use that.
I nearly finished x64 winpe. Flash player x64 and media player x64 working. Used K-Lite_Codec_Pack_64bit_400.exe and it adds 10MB codecs to wim
Can not get media player to work without it. Works better then mine x86. There is no interruption at sound and video when playing with media player. (sometimes i get little interrupts at x86). I used windows 7 imageres.dll and it is 20mb standalone, maybe i need to change with winpe one. So it get over 400mb I don't see theme background and can not join to homegroup (it says no license for it.) Other everything works. For x86 have fundamental support and for specific x86 programs need to add extra dll files that programs need to work.I think to work on Media Center Winpe. That will start with Media Center shell default. After will return to work on Server winpe. I don't know why i spend all my time with this winpe sh*t
Working Media Center Winpe. It is only 400mb wim with .NET 2.0 and ehome. Now it has explorer shell. My aim was to boot ehome shell after boot but there is problems for that. First need to install sound and video drivers for to lauch ehome. It can be possible using batch files and inf loading at boot. If i can use profiling and optimize it can be better. It plays my divx files without problem. I didn't check every function. Screensaver and games works.
And this is another full winpe7 i made from zero again. I installed Windows Embedded Standart 7 with my desired features. Used it's file list and boot all windows. No media center and size 600mb. Updates finds but i couldn't installed webcam driver from updates. The reason of i want updates to work is user will not need to carry or add drivers to build. He will just use updates and install (if doesn't need restart of course)
I want to explain the difference of my builds from a real ram booting windows.
*I always keep it as winpe. My builds uses wpeutil and winpe boot process. In real windows it is user session login without wpeutil.
*Winpe registry values always kept for it to work and boot.
*I always keep SAM and SECURITY hives unchanged. It wasn't boot when they kept. (did not try again in near past) This gives some function loose to my builds. Forexample "User Control Panel" and "Reboot/Shutdown" icons never works. I believe the reason is that.
I have seen a real ram booting windows 7 in 450mb size at a russian friend. If i compare his and mine builds.
In real ram booting 7
*User control panel and shutdown buttons works.
*It works slow when compared to mine builds.
*After boot windows 7 driver loading works and it takes lots of time to install drivers.
In my builds.
*User control panel and shutdown buttons not works.
*It works faster then ram booting.
*Driver install is very quick.
I believe they can convert to each other very easly with little registry and file changes. I did not test.
0 -
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services
There nothing language specific stuff in it. Can use every language. I need to make anew hives editing for my turkish x64 windows 7. If you want i can give a teamviewer sesstion lesson for editing of everything. You can see every change on all hives that i do. If you know about teamviewer.
0 -
Hehe. I made that in two days. Previous i was also made a x64 build i have experience from there, but in that build i couldn't get x86 programs to work. Because of that i couldn't get procmon to work and couldn't develop more also i didn't have x64 capable pc to work on. I extracted files from JFX script and see that i forgot to put all x86 commoncontrol winsxs entries. When i integrate that i saw x86 programs work. It get procmon to work and i have x64 capable pc now. After months of work i found to convert full hives to winpe capable hives. It takes me a few hours to convert them so i don't work on registry much now. Also i have default services.hiv for both x86 and x64. I made 3 months. In every project i use them and it never blue screen. If there is extra services like in this server project i copy and add them. Also have experince from previous work and i can understand from file names what it is for. I made lots of optimizations with dism and had lots of optimized file lists. It is a plus too. In x64 builds procmon not works as i expected. It is my opinion. Also optimizations with dism gives x86 optimization file txt but it doesn't clean x86 files when applied to wim. Maybe bug. Maybe it needs servicing x86 programs and x86 servicing stack under x64 environment. Also using dart tools under winpe environment and as loader is a plus. It's winpe log files gives missing files for services and everything about under windows\inf\setupapp.log, setupdev.log
PS: Have you find a solution for multilanguage support ?
I made as it should be. Don't know why doesn't work. I didn't test in real environment because so much work for me
0 -
if you need i can work on it. probably you can integrate to windows 7 too.
0 -
server functions works on mmc snapins, from my previous experiences snapins doesn't work without related winsxs folders (normaly windows functions works without winsxs folders). It boots with all services (i don't say all working) like vhd,hypervisor,dhcpserver services. At the time of writing (now) none of hyper-v related services works. I have only 1GB RAM so adding more files and work on it is difficult for me (in virtual machine). Also my mother board usb boots very slow. I decided to stop on server based winpe until i decide to continue. Want start from basic windows 7 x64.
0
Also that problem maybe solved but i do not want to spend time for it. Good part it accept embedded serials and also ultimate edition serials same time. Only problem for me i can change background and use themes when it is unactivated and embedded trial but when i fully activate as ultimate ed. it says i do not have license for personalization and it shows blank screen to anytime upgrade. Also when it is ultimate edition it can search for updates but it says there is no update for my system 
Just add and use your own custom system without hard works with vlite. spending lots of time removing components.
Can not get media player to work without it. Works better then mine x86. There is no interruption at sound and video when playing with media player. (sometimes i get little interrupts at x86). I used windows 7 imageres.dll and it is 20mb standalone, maybe i need to change with winpe one. So it get over 400mb 
WinPeShl.exe,WpeInit.exe,WpeUtil.Dll
in Windows PE
Posted · Edited by Kullenen_Ask
Probably it works like tracking if the user clicked on shutdown button or not. It works same way with the ReBootTrace.exe,ReBoot.dll dll that i shared in my topic. If you read pecmd manual you can see that. There is source code of ReBootTrace.exe,ReBoot.dll in my topic if not deleted. If you want to use shutdown button, autologin as administrator rights user. You will have that functionality without using a third-party software.