Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - whiggs

Pages: [1] 2
1
Win10PE SE HomePage / Re: Getwaiktools plugin question
« on: August 04, 2017, 04:01:27 AM »
JFX.  One more thing which, not only proves what I have been saying about needing to use the correct version of the deployment tools from the correct version of the adk (as I did verify that your script "GetWaikTools" downloads the deployment tools from the adk for Windows 10 redstone 1), but could also be part of the reason as to why the Win10PESE fails to create a bootable media using the creators update source files (I say part of the reason because I modified WinpeSE scripts to account for the changes and switched out the deployment tool files with the correct version of the same files pulled from the correct version of the adk and it still failed) is because of the fact that, in the ADK version 1703, the file which WinpeSE uses, called "WimMountInstall.exe", does not exist, and has instead been replaced with a file named "wimmountadksetupamd64.exe" and "wimmountadksetupx86.exe".  I have to say I am disappointed.  Instead of doing proper research yourself into the the importance of using the correct version of the adk on the associated version of Windows like a real professional, you were all too eager to say that my process, reasoning, and operating system image were flawed.  As a professional, I don't so much as open my mouth without verifying the facts first.  A lesson you hopefully take away from this. :mad:

2
Win10PE SE HomePage / Re: Getwaiktools plugin question
« on: August 03, 2017, 10:13:04 AM »
JFX.  So while not specifically stated that using a particular version of the adk to modify a different version of Windows 10 will break the installation, Microsoft did state this, which seems to support what I have been saying:

3
Win10PE SE HomePage / Re: How to Create a Windows 10PE Boot Disk
« on: August 03, 2017, 09:51:12 AM »
Atari800xl.  Did you see me ask a question?  I was providing feedback and advising on ways for him to bypass issues that can arise from using a pre installation environment to modify an already existing operating system that is not the same version.  His concerns are completely valid, as using sfc built for windows 7 probably would both break a Windows 10 installation as well as return invalid results.  Same holds true for using DISM built for windows 8 on windows 10.  When using an earlier version of Windows 10, the damage is not as obvious, but it is for this reason that Microsoft releases a new version of the ADK (and by extension, new versions of DISM and all the deployment tools) for every version of Windows 10 released, as the functionality is most certainly not the same and can potentially break the existing os.  This is why I advised that, instead of running the sfc that is native to the pre-installation environment, use the sfc executable that is native to the offline operating system and use that to perform the scan and fix.

4
Win10PE SE HomePage / Re: How to Create a Windows 10PE Boot Disk
« on: August 03, 2017, 02:57:30 AM »
It won't.  Take it from someone who has tried.  It won't.  As for what you said concerning needing the same version of the operating system as the one that is installed on the device, well that would depend.  What are you trying to accomplish?  If you are going to use tools that are native to Windows (like sfc, chkdsk, dism), then yes, you would need the same version of the operating system.  However, there is a very convenient way around this.  Lets say you wanted to run sfc on the offline operating system.  Instead of running "sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows", run instead the version of sfc that is within the offline operating system.  Assuming that your operating is stored on C: drive, type "C:\Windows\system32\sfc.exe /scannow /offbootdir=C:\ /offwindir=C:\Windows".  That way you are scanning the operating system with the version of sfc meant to support it.  Do the same with DISM and chkdsk.  If, however, you are simply using whatever built in programs that you build into the Winpe, then operating system is irrelevant. 

5
I don't know if you are still looking for an answer to this question, but the solution is simple:
1) open command prompt
2) Enter command "diskpart"
3) Enter "list disk"
4) Determine which of the listed disks is the flash drive you want to make into the bootable flash drive
5) Enter "select disk #" where # is the disk number associated with the disk you identified in previous step
6) Enter "clean"
7) Enter "create partition primary"
8) Enter "active"
9) enter "format quick fs=fat32 label=Boot"
10) enter "assign letter=T" or whatever letter you want to assign to the flash drive
11) type "exit"
You now have a blank, bootable flash drive.  You simply need to extract the contents of whatever bootable media you want to boot to the flash drive.

6
Win10PE SE HomePage / Re: Getwaiktools plugin question
« on: August 01, 2017, 07:58:08 PM »
Agree to disagree then. 

7
Win10PE SE HomePage / Re: Win10PE PXE Boot
« on: July 10, 2017, 06:11:58 AM »
As for getting your Winpe to boot off a Pxe Server, look no further than the below setting in "WinBuilder".  Be warned, though, if you have a lot of content in your WinPE, you will need a lot of RAM in the client device to successfully load it, as EVERYTHING will be packed into the WIM file:

8
Win10PE SE HomePage / Re: Will Win10PE SE Support 15063 Build?
« on: July 10, 2017, 06:06:52 AM »
Waiting for an update.

Don't hold your breath.
10PESE is on hold for now...

What?!  Why?

9
Win10PE SE HomePage / Re: Run Command After PENetwork in Win10PE SE
« on: July 10, 2017, 06:03:44 AM »
Or, what you can do is, after the Winpe is compiled and built, there is a script called TheOven_Startup_CD.cmd in the root of whatever media you built and in the root of the directory containing the build files.  That is the script which launches upon the WinPE first loading up, so you can just put whatever commands you want to in that file....

10
Win10PE SE HomePage / Re: Will Win10PE SE Support 15063 Build?
« on: May 10, 2017, 03:49:35 PM »
I agree with the statement that the Creators update release was a total disaster.  Get this.  In addition to the other issues discussed in this thread, almost immediately upon installing the creators update (how naive I was, getting so excited about it), I discovered that running "Dism /online /cleanup-image /restorehealth" would fail.  No matter if it was run on a brand new os, no matter if the install media install wim was specified as the source, no matter what, the command would fail.  You might ask yourself why this is.  for the answer, look no further than Tweaking.com's Widnows AIO repair tool.  When running the pre-scan, the log outputs the following information concerning the Windows package files:
Scanning Windows Packages Files.
│ Started at (5/8/2017 12:55:25 PM)

│ These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 1)
C:\Windows\servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum

1 Combined Problems were found with the packages files, these files need to be replaced (These mainly only effect installing Windows Updates.)
│ The SFC (System File Checker) doesn't scan and replace some of these files, so you may need to replace them manually.

This would also explain why sfc is still able to run and complete successfully.  In short, Microsoft shipped us a product which has corrupt package files out of the box.  In my opinion, its just a broken product out of the box, and its unacceptable.  I mean they have had almost two years to improve upon this product.  The Redstone edition has probably been the most stable to date, but how is it that the release after it is so utterly horrible that it is almost as bad, if not worse, than the initial release??  Microsoft should literally be ashamed of themselves for releasing this product, as it has brought me really nothing but grief.  I fully stand behind your decision not to update WinpeSE until Microsoft releases an actually functional product because this embarrasment of a release is not even worth your time, that is for sure.

11
So while this answers the question as to why (I am guessing creators update os installation media is not compatible with WINPESE), are there any plans to make WINPESE work with the creators update or is there a more fundamental reason why it just won't work?

scratch that

12
Win10PE SE HomePage / Re: Getwaiktools plugin question
« on: May 10, 2017, 01:12:26 PM »
So you are saying that you can use any version of the adk tools with any version of Windows 10?  I don't know if I agree with that.  I remember around the time that the Redstone version of Windows 10 came out, I had forgotten to upgrade my version of the adk to the version released for the redstone edition and had created a custom capture of the redstone edition using the adk from the previous version.  I remember this because I remember getting super frustrated because I couldn't figure out why a) my disk resources were almost always polling at 100%, so it was really slow, b) sfc and dism would always fail to complete successfully until dism was run using an install.wim pulled from install media as the source, and then running sfc would find and repair corruption, and c) there was a very bad latency issue when attempting to play any kind of media on the computer: movies, songs, even spotify would start making this "skipping" sound, like you hear when your media player crashed or when you play music from a scratched CD (are cds still even a thing at this point, lol jk).  It was only when I was just about to install the previous version of Windows 10 because I was so tired of all the issues that I realized I had been using the wrong version of the adk.  Once I re-created the custom image of Windows 10 with the correct version of the adk, all the problems magically went away....

13
forgot to attach log for those who want it.

14
Whenever I try to build my Win10 PESE media, I always get the following error when the build process reaches the powershell component script:
Cannot create file "%BaseDir%\Target\Win10PESE\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Computer Management\desktop.ini". Access is denied: [IniWrite,#2\desktop.ini,#3,#4,#5]
I have run the application with administrator rights, so I know that permissions is not the issue.  Rather, I believe it is, due to the prompts that I receive when I delete the contents from the hard drive, that the path that the application is trying to write the file to exceeds the 260 character Path limit that is a limitation of windows.  My question is how do I get around this in order to make the build succeed?  The folder which contains the application is already in the root of one of my slave drives and the folder name is 2 characters.  Please advise.

15
Win10PE SE HomePage / Getwaiktools plugin question
« on: May 03, 2017, 08:40:54 AM »
Hello the Oven community.  I had a question in regards to the GetWaiktools script which downloads the necessary deployment tools which are normally included in the adk installation for use in the building and configuring of Windows 10 PESE.  More specifically, as you may or may not know, microsoft has released a new version of the Windows 10 adk for each new major update of windows 10 that has been released, including new versions of the tools included within.  So my question is how does the script know which version of the ADK tools to download and use when the script is run.  Does it scan the source media and use that to download the right version?  Does it not check at all and download only a specific version that is specifically specified in the script?  If the answer to this question is the latter of the two scenarios, then it would probably be a good idea to update the script so that it downloads the version of the ADK tools that match the version of Windows 10 that is being used as the source.  But this is a question to which I would like to get an answer to.  Thanks in advance.

16
Win10PE SE HomePage / Quick question.
« on: February 11, 2017, 01:14:19 AM »
Hello "theOven" Community.
So I have been using WinPESE for about 3 years now, and love what the tool can do.  Absolutely spectacular tool guys.  I haven't had any issues with the product (well, none that weren't answered by reading the forums anyway), but I did have one question about the tool in general.  Is there a way to replace the standard Windows Recovery environment with a Wim created with WinpeSE.  I have tried doing something like this during an os deployment, but instead of using WinRE, I try to use a wim created with WINPESE and activate it with Reagentc tool, but I get error "not a valid Winre image" or something around those lines.  The closest that I have gotten to my goal is to extract the contents of a WinpeSE iso to a bootable partition and edit boot menu to include that partition when booting.  So while I have kind of sort of gotten it to work, I would like to do it, for lack of a better phrase, "the right way."

17
AutoIt3 is supported. I would say it's the same problem laddanator has with his batch files.

Since all is working here, both of you must write bad scripts  :tongue:

I take offense to that sir.  I am fully aware that autoit is supported: the batch file that I ended up using runs a compiled autoit script to edit the contents of an unattend file.  And believe me when I say I tried for hours to get the correct console command to run in autoit, making edits in the editor, compiling, saving script ot flash drive, and then running it on machine running winpese.  Also, if YOU had read the entirety of my initial post, you would have seen that I tried both setting the "working directory" parameter to "X:\windows\system32" and I tried not calling the working directory parameter at all, instead using format.com's full path in the command.  Which is why I eventually just gave up and went with the batch file method and why I felt confident in posting.  If you can provide at line of autoit script that can do this in the win10pese, I will eat my words.  However, untill then, this post was simply meant to be informative. 

18
ok.  so I wrote an autoit script order to automate the steps in deploying windows to client devices: 1) first the user was prompted to enter the computer name into an input box which the script would then use to edit the portion of the unattend.xml file used in step 3 relating to computer name, 2) the script would then format the C: drive of the client device to prepare it for the operating system installation, and 3) using WinNTsetup's command line arguments, automatically configure and begin installation of the operating system to the device.  Only 1 of the three steps outlined above did not complete successfully no matter what I tried, and believe it or not, it the one that would appear to be the most simple: formatting the C drive.  I believe the problem most stems either from the fact that the "windows" folder containing the system32 files is mapped to the X: drive, and not C:, or it may be due to the fact that for the line of script in question (Code is:    RunWait ( @Comspec & " /c X:\windows\system32\format C: /FS:NTFS /q /x /v:Windows /y" )uses the Comspec macro, but regardless, even calling the function with its full path did not work, so I was forced to improvise and creat a batch script which then called a modified version of the above script (which just had part 1), then would perform format and launch installation.  It would be great if this could be fixed, as autoit is one of favorite scripting languages. 

19
Win10PE SE HomePage / Re: windows setup tool
« on: May 11, 2016, 06:34:12 PM »
Let's see...
For WinNTSetup (running from a Win8PESE64 usb, or other flavour), this is the commandline I use (Autohotkey "driven"):

(I'm not using a codebox here, because the line is so long)
run,q:\winntsetup\WinNTSetup_x64.exe nt6 -source:y:\os\w10ent.wim -syspart:c: -unattend:"w8_audit.xml" -savedriveletters -sysletter:c -reboot -disableuac -wimindex:1 -DisableHiberBoot -win8noanimation -DisableSystemRestore -DisableSFC -DisableHibernate -runafter:"CopyAuditModeUpdateScriptstoPSModules.exe" -BootToDesktop -nobootsect

"CopyAuditModeUpdateScriptstoPSModules.exe" is a (silent) WinRar SFX, it uses the "Windows Update Powershell Module":
https://gallery.technet.microsoft.com/scriptcenter/2d191bcd-3308-4edd-9de2-88dff796b0bc

This is in the WinRar comment for the SFX:
Code: [Select]
overwrite=1
path=c:\windows\system32\windowspowershell\v1.0\modules
silent=1

So this is installing Windows 10 in audit mode automatically and fully unattended (I'm not listing the "w8_audit.xml" here). After setup, I use "Set-executionpolicy remotesigned", "Get-WUList" and "Get-WUInstall" to install updates. After that, it's "dism /online /cleanup-image /startcomponentcleanup /resetbase", then sysprep and capture (using Wimlib-imagex, of course).

There's other stuff in there as well, being installed while in audit mode, but that's not of intereset here, just wanted to show you how powerful WinNTSetup is!!! JFX Rulezzzz...
 :thumbsup:

Thanks for the information friend.  I was having trouble figuring out how to use the command line aspect of the tool, but you have cleared that right up.  Thought nt5 and nt6 were also parameters preceded with "-".  One more question.  I see you have experience in autohotkey.  I personally use Autoit, but they do the same things with different syntax.  I am trying to write the autoit script which will format the windows drive prior to running the command line for the setup tool, because if I don't format it, the setup will fail due to permission error.  However, when I attempt to run the code to perform the format, it fails.  Not sure which aspect of it is failing, but maybe you can provide some feedback?
Code: [Select]
$wtf = Run ( @ComSpec & " /c format C: /x /q /v:Windows", "X:\Windows\system32", @SW_SHOW, $STDIN_CHILD )
StdinWrite ( $wtf, "Windows" & @CRLF & "Y" & @CRLF )

20
Win10PE SE HomePage / Re: windows setup tool
« on: May 09, 2016, 03:19:05 AM »
WinNTSetup has its own forum, my advice would be to do some reading there. Just google for "WinNTSetup" or "WinNTSetup forum".
The "RunAfter" command is very useful, I use it all the time, for normal installs I use it to copy Abbodi's KMS stuff to the \Setup\Scripts folder (using an SFX archive), for Sysprep installs I use it to copy the Powershell Update tools to the appropriate folder.

Thank you for your reply.  The second scenario you described concerning sysprep install s is exactly the scenario I find myself in at the moment.  I want to automate as much of the process for the company I work for as I can, and if I can get Run after to work, I will eliminate all but the initial configuration and turning off the machine at the end.  Thanks.  I will go check it out

Pages: [1] 2
Powered by EzPortal