Aborted - Package integration [13] The data is invalid

Ceyarrecks

Ceyarrecks

Member
Excuse me Please:
I am attempting to hone a win7u sp1 64bit install on an Alienware system using the OEM disk as source.
I am using NTLv1.6.3.6440 64bit and Clanger's W7-Lite-v4 preset.

I have received the error while integrating .msu patches for an off-line store.

Aborted - Package integration [13]
The data is invalid.

(having difficulty remembering where find the .log file, please remind me for inclusion, if need be)

is this error enough to render understanding as to what I have done incorrectly?
 
well, the NTL got all the way through the patches and such, burned the DVD (although using win7 built-in burner, so that might be a problem)
status: 0xc0000001
file: winload.exe
missing or corrupt

any ideas?

edit:

since I can not upload the ntlite.log.bak for some unknown reason, here is its text:

3/1/2019 2:09:58 AM Load tool settings
3/1/2019 2:09:58 AM NTLite v1.7.3.6760 x64
3/1/2019 2:09:58 AM 8 CPU Threads


or so i thought, but:

The submitted message is too long to be processed. Please shorten it.
so guess I am at a loss.
 
and this supposed ISO comes automatically "activated" on an Alienware system?

and, rather presumptuous, no?, expecting that "EVERYONE must have Unlimited Bandwidth ISP accounts."
 
Kasual said:
The ISO download is from Ms, windows update. Links are generated and expires.

Activation commands file attached for easy.
Click to expand...
well, all of the .ru domains referenced on the site that expected to run scripts gave me pause; selecting win7ultimate as is the Alienware OEM disk I have stated it could not be found. /shrug

I need to go through NTLite's quite exhaustive list with a fine-toothed comb, because the second burned ISO where I used a previous Saved Preset from an earlier build is still missing winload.exe--suggesting I am inadvertently removing it with a particular setting change.
{the & trim setting on the last page maybe?}

I know the Alienware OEM disk works, as the hard drive of that system was newly installed, and the DVD used to just throw an OS on the system.
it has been from there that I have been wrestling with NTLite and my resent experiences.

I also realize a VM would make this experimentation must faster, but I have zero experience and no clue where to start; so burned disks and boot is my remaining option.
 
Get a clean source.
I used the drop down menus to get the english Ultimate (not the COEM) ISO download link (tied to my ip i think).

File upload: 02/18/2012 02:06:29 GMT
File size: 3167.06 MB (3320903680 bytes)
Download: 206055
SHA1: 36ae90defbad9d9539e649b193ae573b77a71c83
Link expire: 03/05/2019 01:00:27 MSK


I have a DELL Inspiron and i'm working with OEM DELL activation.

The product key for home basic x86 works with x64 and so does for Ultimate.

Get the product key:
Install the Windows OEM, use ABR (Activation Backup and Restore) to get the product key and certificate.
Download the oobe.txt attached in my post above and edit, replace XXXXX-* with the Alienware backed up product key.
Rename oobe.txt to oobe.cmd and copy to sources\$OEM$\$$\Setup\scripts
Copy the certificate to sources\$OEM$\$$\Setup\scripts

For setup i use a flash drive and WindowsSetupFromUSB, 8 GB size is good because bigger takes longer to boot (compared to 64 GB flash drive).
 
Ceyarrecks said:
well, the NTL got all the way through the patches and such, burned the DVD (although using win7 built-in burner, so that might be a problem)
status: 0xc0000001
file: winload.exe
missing or corrupt

any ideas?

edit:

since I can not upload the ntlite.log.bak for some unknown reason, here is its text:
Click to expand...
Thanks, I tried the preset, it worked fine with an official Win7 ISO and latest updates.

Question is when do you get that winload error, is it immediately when booting it? If so, then it's a Windows/DVD/Machine issue, since NTLite does not touch boot.wim in your preset - other than deleting an unneeded edition from it.
Try keeping that - meaning after loading the preset on the Apply page, under Save method, choose Save, and make sure no editions are removed from boot.wim. This never was an issue, I'm just trying to get to 100% untouched boot.wim.

If you get the winload error later in the setup process (install.wim), then please try the NTLite's list of updates (Updates - Add - Latest online updates) instead of your list, it is current and covers all fixes.
Meaning after loading your preset and correcting the above boot.wim thing, remove all updates from the updates page, the "add latest".

You can Zip the log file and upload that zip. Logs are more important for the crash situation, preset for testing finished processing.

I'll send you a newer version which may fix the crashing you had, but for this second issue try the mentioned, if that didn't help, get a different ISO or upload that one (PM me) and I'll test.
Also check how do you boot the machine, is it via BIOS or UEFI mode - that's whole 'nother can of worms, research a bit. Win7 is better in BIOS mode, it officially does not support UEFI.

edit: also try using an USB key to boot instead of burning the disc. Rufus is a good tool to prepare that.
Just make sure to use USB2 port when booting, not 3 to avoid the need to integrate drivers into Win7 boot.wim.

Thanks.
 
Thank you ALL! for the guidance! :D:cool:
I actually found a Dell win7u disk, so I can try that as an alternative; I do experience the winload error immediately after the "Press any key..." prompt.
And previously I was using a USB-connected external CD/DVD-burner; so great IDEA! for the use of a USB drive, heh, less disks need I burn then;
and I do have Rufus around here somewhere already.

The bios already to ATA/BIOS.

before getting too far down the Rabbit Hole(tm) let me try previously attempted ISO on a flash drive and see what happens,..
will report back results.
 
nuhi said:
Try keeping that - meaning after loading the preset on the Apply page, under Save method, choose Save, and make sure no editions are removed from boot.wim. This never was an issue, I'm just trying to get to 100% untouched boot.wim.
Click to expand...
will re-attempt following this guidance and create new .iso; as previously had NTLite "trim" unneeded versions.
this is the previous preset that I had success with on my current Dells (removed and then re-added all patches is only difference, nothing else was changed)
the .RAR is the previous .DMP received, which I have not experienced any crashes last few times I used the program; I include for completeness of previous issues, as it may still be relevant.
 
Try the untouched ISO first with the same deployment, should be no difference regardless of the preset or no edit.
Then debug what is wrong, search on the web for that Windows error.
Bunch of ideas here.
Let us know what you find out.
 
not sure if this is important, but I found this oobe.cmd already in the scripts folder on the Alienware OEM disk while attempting to follow the oobe.txt guidance....
 
OOBE is at the end of setup, as far as I understood the report, your issue is at the very beginning.
That is only influenced by boot.wim image, and judging by online solutions, disk layout.
Check the link above and try a few.
 
WOOT!
Progress!
YEAH!, Thank You Nuhi! for the v1.8.0.6776.
That and tell NTL not to "trim" allowed for a successful install on Alienware Laptop.
{so was it the lack of trim or the newer version that resulted in successful install?}

However, it seems I may not have done the oobe correctly in NTL since the system is not activated, so am retracing steps.

to verify, one need only identify oobe.cmd's path in the Additional Execution window along with the powercfg and expirations, right?
no additional parameters like powercfg gets? i.e. "/hibernate off"
 
Ceyarrecks said:
However, it seems I may not have done the oobe correctly in NTL since the system is not activated, so am retracing steps.
Click to expand...
In virtual machines doesn't works this Activation:
Kasual said:
Rename oobe.txt to oobe.cmd and copy to sources\$OEM$\$$\Setup\scripts

Copy the certificate to sources\$OEM$\$$\Setup\scripts
Click to expand...

Drop the oobe and certificate in scripts folder, verify the pid key and certificate name.
 
Ceyarrecks said:
WOOT!
Progress!
YEAH!, Thank You Nuhi! for the v1.8.0.6776.
That and tell NTL not to "trim" allowed for a successful install on Alienware Laptop.
{so was it the lack of trim or the newer version that resulted in successful install?}

However, it seems I may not have done the oobe correctly in NTL since the system is not activated, so am retracing steps.

to verify, one need only identify oobe.cmd's path in the Additional Execution window along with the powercfg and expirations, right?
no additional parameters like powercfg gets? i.e. "/hibernate off"
Click to expand...
Good, maybe that ISO does something special with WinPE (no trimming it then).
Do let us know when you confirm, least probable is the new version.

You can try running OOBE.cmd manually after install, from CMD, and see if there are any errors.

Also see if modification, especially setupcomplete.cmd, removed/edited any original lines in a way that would skip activation.
 
WOOTWOOT!:D
Successful & auto-activated install using the OEM Disk, the v1.8.0.6776 and replaced oobe.cmd;
I learned also that the "backup-" text needs to be removed from the file name of the backed-up cert that is placed in \scripts\ directory as the oobe.cmd calls specifically for it by name.

I want to Thank Everyone!
Nuhi, Kasual, Clanger,
all of you have been a great help!!!!
 
You must log in or register to reply here.
Back
Top