Stop Windows 10 1607 upgrading to 1709

Tiger-1 · Mar 11, 2018

^dude search more for me is visible (when I'm using Build 1709) the performance when opening file explorer, MSOffice, heavy games as Ride for Example, MotoGP17 and so on is serious so for me 2016 LTSB(C) is already old

elzna · Mar 11, 2018

Tiger-1 said: ↑

^dude search more for me is visible (when I'm using Build 1709) the performance when opening file explorer, MSOffice, heavy games as Ride for Example, MotoGP17 and so on is serious so for me 2016 LTSB(C) is already old
Click to expand...

Eh. Doubt performance improves lol

erpsterm35 · Jun 18, 2018

You need to login to view this posts content.

abbodi1406 · Jun 22, 2018

You need to login to view this posts content.

ghostmankimo · Jun 24, 2018

Can't uninstall KB4132216.

Rename SupplementalServicingAI.dll under other system (PE), CU still blocked！

Any Suggestion ？

Thanks.

abbodi1406 · Jun 25, 2018

You may uninstall it
https://forums.mydigitallife.net/posts/1154312

but there is no point, all future CUs require it

i don't have any workaround in mind

abbodi1406 · Jun 28, 2018

Apparently integrating CU offline (before or after installing OS) can bypass the restriction

ghostmankimo · Jun 28, 2018

Thank you very much.

To integrate CU offline can bypass the WU restriction.

Tested this method under PE. It works！

Tany · Jul 1, 2018

me to have problems on dis build

erpsterm35 · Jul 3, 2018

You need to login to view this posts content.

xinso · Jul 5, 2018

[For Windows10.0-KB4284833-x64 - 14393.2339]

1. Blocked
KB4023057
KB4023814
KB4056254
KB4091461
Windows 10 Feature 1803

2. Uninstalled
Package_8530_for_KB4284833~31bf3856ad364e35~amd64~~10.0.1.8

erpsterm35 · Sep 26, 2018

abbodi1406 said: ↑

Apparently integrating CU offline (before or after installing OS) can bypass the restriction

View attachment 45979
Click to expand...

I wanted to ask you if integrating the CU can be applied to a "multi-edition" ESD or ISO. if so, how can it be done?

Enthousiast · Sep 26, 2018

erpsterm35 said: ↑

I wanted to ask you if integrating the CU can be applied to a "multi-edition" ESD or ISO. if so, how can it be done?
Click to expand...

The same way as with a single index ISO (ESD can't be serviced).

Extract the ISO to a folder (use folder as target in settings). Put the updates next to W10UI script and set the settings as you wish and run it elevated.

erpsterm35 · Feb 14, 2019

ah thanks Enthousiast.

another user found a way to install new CUs for v1607 pro but mentioned it in another thread.

TEMPUSER_ said: ↑

Are these suggestion applicable to 1607 Pro version, (to fix latest CU installation)
Because after update 2018-05 issues appeared when I try to install newer CU's.
My solution to get latest CU (2018-12), was to integrate updates into ISO
- KB4132216
- KB4483229
This worked fine, until I tried to install latest CU.

Okay, now I written comment, then checked out links above, and found more info about my problem.
Seems like if you are on Pro, only way to install latest CU's, is integrate them into image.
_
UPD.
0. Install KB4132216.
1. Get NSudo, ProcessHacker, or other utility that allows you to run software with TrustedInstaller rights/access.
2. Run with it file manager/explorer (in my case Explorer++)
3. Navigate to - C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.0_none_36d3ccc3ddfd1ecb
4. Copy wcp.dll
5. Paste copied file in - C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.2272_none_7f1843c421e0830a
This folder should appear when you install KB4132216. (if necessary create backup, and replace wcp file)
6. Install latest cumulatives.
*I think folder names can change for other users, but it should be easy to understand 14393.0 and 14393.2272, where to take file, and where to paste it.

Tested on 2018-12 CU (KB4483229), installed without problems.
Before update system had only 2018-05 CU (KB4103720).
Click to expand...

Feniksrising · Feb 17, 2019

Why not just switch to LTSC? Its the only version that gives you complete control.

pf100 · Feb 17, 2019

Feniksrising said: ↑

Why not just switch to LTSC? Its the only version that gives you complete control.
Click to expand...

I think you meant to say LTSB which is 1607 which is the version he's trying to stay on.

zexmais · Feb 19, 2019

You need to login to view this posts content.

dzem · Feb 24, 2019

One question:
Since upcoming version of win 10 has problems with x.fi cards, and i am the owner of one, i am not going to install it until they fix a bug. Something tells me that is not going to happen soon, so i will like to know how to disable automatic update of upcoming march/april version of windows 10? Thank you

pf100 · Feb 24, 2019

dzem said: ↑

One question:
Since upcoming version of win 10 has problems with x.fi cards, and i am the owner of one, i am not going to install it until they fix a bug. Something tells me that is not going to happen soon, so i will like to know how to disable automatic update of upcoming march/april version of windows 10? Thank you
Click to expand...

https://forums.mydigitallife.net/th...-completely-control-windows-10-updates.72203/

Super Spartan · Feb 25, 2019

abbodi1406 said: ↑

A very interesting way to block CU
it's controlled by new SSU component SupplementalServicingAI.dll which check edition and device for "support" compatibility

on Pro:

Code:

Info                  CSI    000008e4 Begin executing advanced installer phase 38 index 1616 (sequence 1655)
    Old component: [l:0]''
    New component: [l:171 ml:172]'Microsoft-Client-Licensing-SupplementalServicing, Culture=neutral, Version=10.0.14393.2312, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS'
    Install mode: install
    Smart installer: FALSE
    Installer ID: {4e9a75dd-0792-460c-a238-3f4130c39369}
    Installer name: 'Supplemental Servicing AI installer'
Info                  CSI    000008e5 Loading installer DLL from explicit path: C:\Windows\WinSxS\x86_microsoft-windows-s..ingstack-base-extra_31bf3856ad364e35_10.0.14393.2272_none_389f3215658c29cd\SupplementalServicingAI.dll
Info                  CSI    000008e6 Performing 1 operations as follows:
  (0)  LockComponentPath: flags: 0 comp: {l:16 b:6f5b7180e409d4019e050000f4041405} pathid: {l:16 b:6f5b7180e409d4019f050000f4041405} path: [l:118]'\SystemRoot\WinSxS\x86_microsoft-client-li..pplementalservicing_31bf3856ad364e35_10.0.14393.2312_none_278dba357946c402' pid: 4f4 starttime: 131741164880208629
Info                  CSI    000008e7 Windows::WCP::SupplementalServicingAI::SupplementalServicing::Install.
Info                  CSI    000008e8 Windows::WCP::SupplementalServicingAI::SupplementalServicing::Install Phase = 38
Info                  CSI    000008e9 Windows::WCP::SupplementalServicingAI::SupplementalServicing::IsAllowedSKU Checking if it's Allowed SKU 48.
Info                  CSI    000008ea Windows::WCP::SupplementalServicingAI::SupplementalServicing::IsCloverTrail.
Info                  CSI    000008eb Windows::WCP::SupplementalServicingAI::SupplementalServicing::IsSupplementalServicingSKU Checking if it's SupplementalServicing SKU 48.
Info                  CSI    000008ec Windows::WCP::SupplementalServicingAI::SupplementalServicing::Install It's not SupplementalServicing SKU 48
Info                  CSI    000008ed Performing 1 operations as follows:
  (0)  LockComponentPath: flags: 0 comp: {l:16 b:2cc17380e409d401a0050000f4041405} pathid: {l:16 b:2cc17380e409d401a1050000f4041405} path: [l:115]'\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_10.0.14393.0_none_09e78f632173f4c5' pid: 4f4 starttime: 131741164880208629
Error      [0x018066] CSI    000008ee (F) Failed execution of queue item Installer: Supplemental Servicing AI installer ({4e9a75dd-0792-460c-a238-3f4130c39369}) with HRESULT HRESULT_FROM_WIN32(50).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]

on Enterprise LTSB

Code:

Info                  CSI    000009d9 Windows::WCP::SupplementalServicingAI::SupplementalServicing::Install.
Info                  CSI    000009da Windows::WCP::SupplementalServicingAI::SupplementalServicing::Install Phase = 38
Info                  CSI    000009db Windows::WCP::SupplementalServicingAI::SupplementalServicing::IsAllowedSKU Checking if it's Allowed SKU 125.
Info                  CSI    000009dc Windows::WCP::SupplementalServicingAI::SupplementalServicing::Install It's allowed SKU. Bypassing check. 125
Info                  CSI    000009dd@2018/6/22:08:35:41.191 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{4e9a75dd-0792-460c-a238-3f4130c39369};Microsoft-Client-Licensing-SupplementalServicing, version 10.0.14393.2312, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35};49572us
Info                  CSI    000009de End executing advanced installer (sequence 1503)
    Completion status: S_OK

BTW, KB4284880 and later CUs explicitly depend on KB4132216

Click to expand...

how to run this? Make a .BAT file out of it and simply copy/paste the command you mentioned?

Stop Windows 10 1607 upgrading to 1709

Do you hate the forced update style Windows?

Yes

No

Tiger-1 MDL Guru

elzna MDL Senior Member

erpsterm35 MDL Guru

abbodi1406 MDL KB0000001

ghostmankimo MDL Novice

abbodi1406 MDL KB0000001

abbodi1406 MDL KB0000001

ghostmankimo MDL Novice

Tany MDL Novice

erpsterm35 MDL Guru

xinso MDL Guru

erpsterm35 MDL Guru

Enthousiast MDL Tester

erpsterm35 MDL Guru

Feniksrising MDL Member

pf100 Duct Tape Coder

zexmais MDL Novice

dzem MDL Senior Member

pf100 Duct Tape Coder

Super Spartan MDL Expert