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

[videobruce]

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.

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?

 

[Clanger]

I been using Debian for internet and windows offline, works for me.

Ive bareboned 8.1 services and scheduled tasks, files are in my tweak pack, 8.1 rock solid stable and its old enough that nuhi got to grips with it long ago.

 

[videobruce]

A quick search brought up tons of disabling Telemetry, so it's obvious it's another M$ problem.

Not knowing all of the Services tweaks other than BV's list (the bible), I already have seen many of those that I instinctively changed (in my test runs of NTLite) to disable. Since they can always be enabled, there isn't any reason for concern. Frankly, I would be more inclined just to remove them.

 

[Clanger]

I did use BV for information on what some 8.1 services did but its all my own work otherwise.

You have to be careful with some windows 10 services, those with a number in the display name, you delete them then they regenerate like a time lord, and have a new number at each start, you have to get sneaky.