Recent Posts

Pages: [1] 2 3 ... 10
Win10PE SE HomePage / Logon as Admin - AutoLogin
« Last post by bob.omb on October 15, 2017, 05:32:00 PM »
For those who wish to have Administrator account auto-login (without the command window), replace your SwitchToAdmin.ini with the attached file.

It is a combination of exact(current as of 1709 -10/15/17),  SwitchToAdmin.ini, and SwitchToAdminPrepare.ini, and it bypasses SwitchToAdmin.cmd

Shortcut, Text-on-Top, and username,options will still function as usual, but countdown options will no longer work because it will automitaclly log in!  :wink:  I would love for this to be an option (checkbox) for LogonAsAdmin plugin but until then we can use this.  :great:

Shown in codebox and attached as 7z:
Code: [Select]
//   Switch to Administrator Auto  //

LOGS %WinDir%\System32\SwitchToAdmin.log

CALL PreShell
CALL workgroup
CALL RenameAdmin
CALL Registry
CALL Services
// KillExplorer only for Shortcuts, explorer is not loaded with Auto-Logon
//CALL KillExplorer
CALL OpenSystemMenucmd
CALL Disconnect


LOGO %WinDir%\web\wallpaper\Windows\img0.jpg
TEXT System configuration, Please Wait...#0xFFFFFF L59 T39 $20*
// TIPS  System configuration, Please Wait..,,1,#1

_SUB PreShell

// Mount media USB, ISO to drive Y: Hide Wait
EXEC !=%WinDir%\system32\MountPEmedia.exe

// Fix display screen problems and Show Desktop. Run it once before changing the screen resolution or load a graphic driver.
EXEC %SystemRoot%\system32\FixScreen.exe

//DEVI %WinDir%\inf\xxxxx.inf

// Install external drivers, load external program
LOAD Y:\PecmdExt.ini
INIT IU,3000

_SUB workgroup

// Join a workgroup WORKGROUP, use startnet.exe from PENetwork, to get some network support.
// We must first join the working group, otherwise Administrator can not log in
TIPS  Switch to administrator, set up workgroup......,,1,#1
EXEC != startnet.exe -wg WORKGROUP

_SUB RenameAdmin

// EXEC  = Wait, @background, ! Hide. ex: EXEC =WaitNoHide.cmd, EXEC @!=WaitHide.cmd, EXEC NoWaitNoHide.cmd, EXEC @!NoWaitHide.cmd
// Rename localized Administrator account to Admin
EXEC != secedit.exe /configure /db %WinDir%\security\database\unattend.sdb /cfg %WinDir%\security\templates\unattend.inf /log %WinDir%\security\logs\unattend.log

_SUB Registry

// Disable sihost.exe to speed up the logon. Already done at build time
//REGI HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\EnableSIHostIntegration=#0

// Administrator user logs automatically
TIPS  Switch to an administrator, set up automatic login......,,1,#1
REGI HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\AutoAdminLogon=#1
REGI HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\DefaultUserName=Administrator
REGI HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\DefaultPassword=""
REGI HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\DefaultDomainName=WORKGROUP

// GUEST do not need to use the login screen
REGI HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SpecialAccounts\UserList\Guest=#0

// Launch Pecmd SwitchToAdminLogon.ini after logon as As Admin
REGI HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce\Init=PECMD.EXE Main %WinDir%\System32\SwitchToAdminLogon.ini

_SUB Services

TIPS  Start the service to switch to administrator, ......,,1,#1
EXEC !=sc start gpsvc
EXEC !=sc start ProfSvc
EXEC !=sc start seclogon
EXEC !=sc start ShellHWDetection

_SUB KillExplorer

//TIPS  Switch to Administrator, disconnect current user......,,1,#1

// Existing current users and automatically switch to Administrator with log enabled, it will automatically execute Pecmd admin.ini
// Kill explorer is not necessary for Auto-Logon but required for Switch to Admin shortcuts
KILL Explorer
KILL *Explorer

_SUB OpenSystemMenucmd

// Auto-Login
EXEC !=PECMD.EXE Main %WinDir%\System32\SwitchToAdminLogon.ini

_SUB Disconnect

EXEC !%WinDir%\System32\tsdiscon.exe


Confirmed working ReFS read/write without ability to format in 1709 PE.  Supposedly product policy change allows formatting, but we are already enterprise? does proforW policy work? (I will try to figure this out)

Initial VM test = positive results. Switching from Pro to Pro Workstation instantly added ReFS format capability to diskpart. Below, I change the Product Key and you can see that diskpart instantly offers ReFS format. EDIT: Plus, I then formatted the volume as ReFS.

from bottom of page 10 below:
Win10PE SE HomePage / .NET Framework dispci.dll - 1709 - shows error despite fix
« Last post by bob.omb on October 15, 2017, 01:06:35 PM »
I see that this is explained in the comment section of the Direct X Plugin but the syntax of the current fix doesn't appear to be working.  Error still persists with 1709 source.  It can be ignored but maybe IfExist instead? I should've put this in the 1709 build thread, rather than a new thread, but cannot delete.

Line 343 in DirectX 11.Script:
Code: [Select]

Code: [Select]
Win10PE SE HomePage / Re: get-disk cmdlet non-functional
« Last post by bob.omb on October 15, 2017, 11:56:07 AM »
Is this caused by a script that runs after powershell.script that changes those files? (Need to move powershell fix to end of build process?) - Or is this just an overall fix on the script itself that needs to be done?
Win10PE SE HomePage / Re: PEStartup allows you to configure WinPE without rebuilding
« Last post by bob.omb on October 15, 2017, 11:42:20 AM »
The problem with doing it this way is your using the same amount of effort you could be using to learn how to do it the correct way... It's only easy once you learn it, but so is properly creating a build.. This is a bad habbit.  I highly recommend learning how to use the builder rather than rely on someone else's build if you plan on making enough modifications that you would need this tool.
Win10PE SE HomePage / Re: PEStartup allows you to configure WinPE without rebuilding
« Last post by oldB on October 15, 2017, 05:45:36 AM »
This looks like a really useful addition for anyone who want to customise a WinPE but doesn't want to get stuck into DISM, WAIK etc. or over-use of UltraISO - especially on Flash Memory drives.

An easy question first - when creating an 'Autorun' entry you prompt for a Path and parameters...
I tried 'Drive\Path\MyBatFile.Bat' and 'Parm1' and that gave me a message telling me that Windows(?) couldn't find 'Parm1'
I then tried as you asked - JUST the path - i.e. 'Drive\Path\' and used 'MyBatFile.BaT Parm1' as a parameter list - that doesn't show me an error but doesn't do what I am expecting.
Can you post an example of what to use as 'Path' and 'Parameters' - ideally of a '.Bat invokation' please?

On a broader point - I am using PEStartup using Gandalf's WinPE within an Easy2Boot USB Flash drive.

What I am trying to get my head around is - First - where to put what - e.g. Your own App but also the PortableApps that I would *ideally* just have 1 copy on the USB even though I may have 2-3 variants of WinPE to use them from. In E2B it *appears* that I can get away with just one (2nd = x86) instance of PEStartup and Portable App's.

Second is the topic of UEFI which affects the above - do I need to have all the App's inc. PEStartup within the build or can I get the same level of "sharing" of App's inc. PEStartup between WinPEs? OR? Do I need to look for a UEFI-compliant tool similar to E2B?

I have just realised that I am probably a little off-topic but I am asking here because what you have created in PEStartup addresses the same *sort* of requirements for Easy to Manage Bootable WinPE tools...

If this *is* too off-topic please suggest a more suitable sub-forum or even a different forum/site if that is more appropriate... Many thanks in advance...
Plugins / Re: Components\vcRuntimes_File plugin x86-VC9.7z is corrupted
« Last post by biatche on October 14, 2017, 12:32:36 AM »
not sure if this is the topic, is it possible to add vcruntime 2017?

Win10PE SE HomePage / Re: get-disk cmdlet non-functional
« Last post by Venerence on October 13, 2017, 08:32:28 PM »
I remember that problem.

copy the following files into system32


copy overwrite the system32\wbem folder with the one from install.wim.

rebuild WIM and try again.
Research and questions / Re: WinNTSetup
« Last post by JFX on October 13, 2017, 05:34:38 AM »
I need more information on how to reproduce this.

Does it only happens with ESD files?
Is there a difference wimgapi or wimlib?
Research and questions / Re: WinNTSetup
« Last post by freesoft00 on October 13, 2017, 05:18:29 AM »
If I make something to do this, is "-wimindex:1" where it gets edition? index:2home, index:3pro etc?

Can command line WinNTSetup use iso or does it have to be mounted first?

Yes, can use an ISO with the command line and wimindex is usually a 1-based index.
But you can also pass it's name:

Code: [Select]
WinNTSetup_x64.exe NT6 -source:J:\16299.15.170928-1534.RS3_RELEASE_CLIENTCONSUMER_OEMRET_X64FRE_DE-DE.ISO -wimindex:"Windows 10 Pro"

Installs the Win7 64-bit system in the WIN10 X64 PE environment. Winntsetup prompts for memory errors during installation and exits.
The win7 system ISO file is WIN10, and the system WIM file is converted to ESD format.
Same environment, same system file, WinNtsetup3.8.7 normal.

Pages: [1] 2 3 ... 10
Powered by EzPortal