Using NT Lite on W7 to customize W10 & wrong update package

V

videobruce

Member
Messages
135
Reaction score
8
Note the bold text;
Check the following:
- Using Windows 7 as a host to integrate Windows 10 cumulative updates, use Windows 8.1 or 10 instead (can be a Virtual Machine)
- Updates page Analysis may contain helpful tips
- Are there any Servicing Stack updates for this image
- Integrating updates for the wrong Windows version, e.g. Windows 10 1511 (10586) updates on Windows 10 RTM (10240) image
- Removed components from this image prior to this integration session
3/27/2019 4:37:22 PM The image has been damaged by an offline servicing failure and no further servicing is allowed.
Click to expand...

1. Why would/should using W7 to customize a W10 O/S make any difference?
2. Using the updates provision in the program, why/how did it choose the wrong update package or is that another M$ screw up?
3. "Offline servicing" failure?
 
videobruce said:
Note the bold text;
1. Why would/should using W7 to customize a W10 O/S make any difference?
2. Using the updates provision in the program, why/how did it choose the wrong update package or is that another M$ screw up?
3. "Offline servicing" failure?
Click to expand...
You didn't note the bold text:

1 Integrating isn't customizing, customizing isn't an issue.
2 Updates for 1511 are'nt the same for 1607 or 1709, make sure to download the 1511's updates
3 Offline servcing is modifying a windows image like wrong update or process failed
 
Kasual said:
You didn't note the bold text:
1 Integrating isn't customizing, customizing isn't an issue.
2 Updates for 1511 are'nt the same for 1607 or 1709, make sure to download the 1511's updates
Click to expand...
"Note" means take notice.
The choice of verbs/adjectives (wording) of my question shouldn't be material. Why the 1st error message in the original quote?
Again, the program choose the update, as I stated, I didn't!
 
Please, explain why should mean the same this:

Note the bold text;
Check the following:
- Using Windows 7 as a host to integrate Windows 10 cumulative updates, use Windows 8.1 or 10 instead
1. Why would/should using W7 to customize a W10 O/S make any difference?
 
I thought there was a language problem, now I'm sure. Your sentence makes no sense no matter how the words are rearranged.
 
It is a dism limitation.

NTLite has its own removals engine but it needs dism to mount/unmount an image and for update integration.
Due to a dism limitation you cannot integrate windows 10 updates on a windows 7 host, i dont know the technical details, whether you use NTLite or do it manually with the command line update integration will fail/break whatever, i have never tried so i dont know what and how.

NTLite can service a windows 10 captured image, one that has the updates already installed/baked in it should work. Again i have never done this because i always leave spare space on a hdd/ssd so if i run w7 i create a w10 partition and build my image(with NTLite) from there.
 
"Deployment Image Servicing and Management", I saw the term before, but didn't know what it was.

I have done a couple of dry runs with the program, but that was w/o adding updates. Then the program got confused running in W7 and downloaded the wrong update package? If so, can I manually find updates (I would only be interested in security) and add them myself?

Then you are saying I can't ever use NTLite in W7 to compile W10? o_O

To be clear, I'm NOT trying to add or integrate W10 into the existing W7 in any way, just create a W10 I might be able to live with, then wipe the W7 partition.
 
Or, is this just having to do with adding updates?? If so, then that should be made clear in NT Lite's download/FAQ page. If it's there I didn't see it.

Without going too far OT, the term "mounted", is that referring to unpacking O/S files from a ISO in a form/format replicating what would be the actual installed version of the O/S? (I hope that made sense)
.
 
Last edited:
G'day Bruce, ive always wanted to say that :D

NTLite on windows 7 can do everything to a windows 10 image but not update integration. The tools update downloader will download whatever you select in the drop down box, i got a topic here on it somewhere. If tool downloaded wrong updates then itsa bug, more likely pebkac.

If i am correct NTLite only lists security updates, i use a different method to fully satisfy windows update.

If your hardware fully supports 8.1 and there is no technical reason for using 10 give 8.1 ago, again i have a topic here.
 
"Mount" is unpacking a wim file but it uses links instead of the files themselves, its a bit technical for me, nuhi could explain it better.
 
"Links" to the existing files within the source folder? I have looked at folders these programs temporarily create (this, RT7Lite & nLite) to do all of this and see the 'unpacked' O/S folders they way they would be in a install version.

I wish there was a smiley for one banging his head against a brick wall here to use in this thread.
Unbelievable.

I would never even consider using W8.1 let alone W8. ;)
 
Last edited:
nuhi We have Live Image editing, how about remote image editing? A user extracts a wim file with 7zip, adds any custom files, patched theme files, wallypapers/themes, folders/protables etc, Tool services that image, updates/tweaks etc, saves changes then a user can capture that image with GIMageX.
 
Last edited by a moderator:
It's that interface I was referring to.
Using scripts are above my pay grade. This entire process is complicated enough as it is. After hearing and reading about the forced updates problem with Pro, it's the Enterprise version I was talking about using.
 
Use Classic Shell/Open Shell for shell and (classic)start menu, 8.1 looks like 10 but its miles better. Its bloody stable for a start, tweak the tits out of it and its miles ahead. :cool: You will hardly see a difference between the two.

Bat/cmd scripts are easy once you get used to them, ive only got a basic knowledge of them but i created my own and they are here in a tweak pack.
You can convert a reg file to bat(bats and cmds are the same) with Reg Convert, Sordum i think.

8.1 does what YOU tell it too, not ms.
 
Last edited by a moderator:
Even if you use enterprise to sort the forced updates issue you still got telemetry to worry about and if you use an edition on a bad base build, 1809 and ltsc, its still buggy as hell. I had some issues with 1809 ltsc when changing services, id get "the parameter is incorrect", now goggle that and see how many results there are, some are even basic file moving etc problems. If your os is that buggy you cant move or copy files then you are going to be severely screwed at some point. With those problems and ms concentrating on silly social media type stuff then you can bet your aunt nelly those bad bugs dont mean diddly squat to ms.

In all fairness i ran ltsc for about a week, updated to .379 and it was quite stable. I kept it offline as i would my main workstation so telemetry wasnt an issue, did a few tweaks and it was ok but when i started seeing all those parameter warnings i legged it back to 8.1.
 
Clanger said:
8.1 does what YOU tell it too, not ms.
Click to expand...
Then it can't be from M$. :eek:

You are killing me.
I completely wrote off W8 some time back based on the disastrous original "toy idiot phone" look W8 with those juvenile "tiles" (what a utterly stupid idea) and no start menu.

I was going to use OpenShell anyway. I'm running ClassicShell now. ;)
 
Put an old style start menu in, get 8.1 U3(update 3), update it and give it a test run, thats if your hgardware has drivers, its supported until 2023.
 
I'm seeing more mentions of this "Telemetry" during my searches and reading up on W10. I'll put that on my list pof things to do which is getting longer. :mad:

Support is another thing. There aren't anywhere as many forums (threads) for W8.1 because of the well known f' up of W8. Plenty of support with 10.

The guy who I bought my 1st PC from 20 years ago (I got a late start) which was a custom build (I've never had a store bought one), talked me into Enterprise LTSC based on it doesn't have the consumer crap and the forced updates that Pro has (I never used any 'Home' version).
 
Last edited:
You must log in or register to reply here.
Back
Top