How to SAFELY update to windows 10 build 14393.222

Discussion in 'Windows, Linux & Others on the Mac' started by tywebb13, Oct 2, 2016.

  1. tywebb13, Oct 2, 2016
    Last edited: Oct 2, 2016

    tywebb13 macrumors 68020

    Joined:
    Apr 21, 2012
    #1
    I had a clean install of build 14393.0 and wanted to update to 14393.222 via a cumulative update KB3194496

    But this is a REALLY dangerous update to do via windows update. So when I became aware of this I hesitated to do the update the normal way. What I describe below is an offline method to update which is much safer to do. Often microsoft provide an easy way to do this for some updates, but sadly haven't done so for this one.

    The first rule for any update is READ. Read as much as you can to ascertain any potential dangers lurking within such updates. If there are such problems the internet is probably awash with scathing comments.

    And so it is with KB3194496. Just google it and you will be bombarded with complaints about it. And do this before trying to update.

    Of all criticisms I think the most pertinent one is that this build was originally released to Windows Insiders and microsoft were warned in no uncertain terms that it is BAD…….REALLY BAD!!! Nevertheless microsoft in their infinite wisdom released exactly the same build to the public. Understandably the internet exploded and went nuclear against microsoft. WHY? WHY MICROSOFT? WHY?

    Despite the disasters associated with this update what is not well known is that there is actually a safe way to install this update.

    First it is advisable to completely disable windows update, actually. You can turn it back on later if you want to.

    To do this, just open services by searching for services.msc in Cortana/Search box and open it. Find Windows Update in the services list. Double click Windows Update services. In the Windows Update Properties Window, click stop and select ‘Disabled’ in the Startup type list box. Click Apply and OK.

    Now we do the update offline. And it is this aspect which is making it a much safer way to update. It is not so much the update itself which is dangerous, but rather the way windows update interacts with it that had resulted in so many disasters. We are actually totally circumventing windows update here thus averting such disasters.

    Download the .cab file for KB3194496 depending if you have 64 bit or 32 bit:

    64 bit:

    http://download.windowsupdate.com/c..._2cacef6b46462af81dd957d5b883f32665aad56e.cab

    32 bit:

    http://download.windowsupdate.com/d..._f5ab829a5d2fad9d625797df46ab6ea95cfd78e6.cab

    Move it to C:\update

    Search for cmd in Cortana/Search box, right click and run as administrator.

    Now copy this into the command line in cmd:

    For 64 bit:

    dism /online /add-package /packagepath:"C:\update\windows10.0-kb3194496-x64_2cacef6b46462af81dd957d5b883f32665aad56e.cab"

    For 32 bit:

    dism /online /add-package /packagepath:"C:\update\windows10.0-kb3194496-x86_f5ab829a5d2fad9d625797df46ab6ea95cfd78e6.cab"

    Because this particular cab file is so large (compared to many other cab files) it is going to take quite a while to run. It may even seem to have stalled. It hasn’t. Just be patient and wait. You will eventually be prompted to restart.

    Restart and the update will install normally. And with no disasters caused by windows update.

    You may check the build number has been increased to 14393.222 by using the “winver” tool to find the build number of your Windows 10 system. To launch it, you can tap the Windows key, type “winver” into the Start menu, and press Enter. You could also press Windows Key + R, type “winver” into the Run dialog, and press Enter.

    And if you are really brave, you may then re-enable windows updates in services.msc and check for more updates the normal way.
     
  2. tywebb13 thread starter macrumors 68020

    Joined:
    Apr 21, 2012
    #2
    You can also downgrade to a lower build if you want to using an iso and msu files. There is still no msu for build 14393.222 though.

    Microsoft make these still available for download for those who really know what they are doing (and I hope you do after reading this thread).

    You can retrieve your product key with magical jelly bean keyfinder at https://www.magicaljellybean.com/downloads/KeyFinderInstaller.exe , then download the full installer iso file for build 14393.0 at https://www.microsoft.com/en-us/software-download/windows10ISO/ and do a clean install of 14393.0 (which asks for the product key - hence why you need to find it first)

    and then use the msu files to install any of these builds released prior to 14393.222:

    14393.10 (KB3176929):

    64 bit: http://download.windowsupdate.com/d..._239f7e8c5075df555b2898b4efc734d7d7dded49.msu

    32 bit: http://download.windowsupdate.com/c..._cf3f361027798193039075137ce5f78a10759c50.msu

    14393.51 (KB3176495):

    64 bit: http://download.windowsupdate.com/d..._a344b21f039bfc4c4c145af471da86005fa4288f.msu

    32 bit: http://download.windowsupdate.com/d..._53681ca9d2e5efe55370591ba5fa5f3ff973219d.msu

    14393.82 (KB3176934):

    64 bit: http://download.windowsupdate.com/d..._5e7bc3013384454c32a4fa59c7879367b93f6e86.msu

    32 bit: http://download.windowsupdate.com/c..._7a0bfab3a61d3b4823a52177f1153ce7a62927e3.msu

    14393.105 (KB3176938):

    64 bit: http://download.windowsupdate.com/d..._44ba449488623e643b57988555bcd7db36ac44ce.msu

    32 bit: http://download.windowsupdate.com/c..._e9d96e74ad2b2b2bb7a89e4211c4f9fa873da4ea.msu

    14393.187 (kb3189866):

    64 bit: http://download.windowsupdate.com/d..._2c3e91a8162269579c8bf26a502c620d41efef0d.msu

    32 bit: http://download.windowsupdate.com/d..._48cc54806747877357a732fee03118eb38e92947.msu
     
  3. doynton macrumors 6502

    Joined:
    Oct 19, 2014
    #3
    You don't need a key to re-install Windows 10 if it has previously been installed as it will activate using the hardware ID stored on MS servers. Just click "I don't have a key" when prompted.

    If you have upgraded from an earlier version of Windows you'll only retrieve the generic Windows 10 key anyway.

    I didn't have any problems on any of my systems with KB3194496 in bootcamp (although some have for sure). MS have released a script to get around installation issues with this upgrade https://www.microsoft.com/en-us/download/details.aspx?id=53942

    There is also a new cumulative update KB3197356 released today which (allegedly) fixes the update freezing problems.
     
  4. tywebb13, Oct 6, 2016
    Last edited: Oct 6, 2016

    tywebb13 thread starter macrumors 68020

    Joined:
    Apr 21, 2012
    #4
    Thanks for that. And to add more info to this, microsoft have now released msu files for this new build (14393.223)

    64 bit: http://download.windowsupdate.com/d..._494e8e0044697e7ded8d75fe65a33cc521a938f1.msu

    32 bit: http://download.windowsupdate.com/c..._dd99b4cbdbcd1dbffad24a3dd45ec2bfd1c5480f.msu

    These are much easier to run than cab files. Just double click them and they should install.

    And this one only increases the build number a tiny bit from the last one 14393.222 to 14393.223. It can also increase the build from any of the previous builds from 14393.0 onwards to 14393.223.

    This is unusual. Basically an admission by microsoft that they stuffed up with 14393.222 (although they don't say this).

    Anyway, I'll run windows update the normal way to see if 14393.222 updates to 14393.223 without any disasters. I will do so without running the script you linked to - because despite it being publicly available it actually was released to windows insiders (it is called "Windows 10 1607 Script fix to unblock update for Windows Insiders"). My first post in this thread basically circumvents the block anyway.

    I was going to say before that the lazy way to avert these disasters would be that you could just skip 14393.222 and wait for the next one instead (which now turns out to be 14393.223). But the reason I didn't post that is that microsoft are forcing the update downloads and not giving an obvious way for a choice to disable it. So many people may have basically been forced into an update disaster by microsoft. As is clear from my first post, there IS a way to disable it. And maybe we should exploit this and disable microsoft update in services.msc by default and only re-enable it when WE want to update it (after we have read all the bad news on the update on the net) - not when microsoft want us to.

    I always knew that this thread would have a very temporary relevance - but many people have ended up with unusable computers as a result of the disasters. Hence I don't regret posting it. Microsoft were silent on the issue and did not provide anywhere as clear a way to safely update to 14393.222 as in this thread. When OS vendors fail to communicate their failures and workarounds, we must take over and fill the gaps - whether it be apple - or microsoft.

    And despite the relative short life of this thread there are certain permanent lessons to be learned here. Basically it is about taking back control of our computers. They don't belong to apple or microsoft. THEY BELONG TO US!
     
  5. doynton macrumors 6502

    Joined:
    Oct 19, 2014
    #5
    I think you may have the wrong forum.

    The idea here is to discuss running non apple operating sytems (Linux, Windows etc) on Apple hardware.
     
  6. tywebb13, Oct 6, 2016
    Last edited: Oct 6, 2016

    tywebb13 thread starter macrumors 68020

    Joined:
    Apr 21, 2012
    #6
    I know that.

    Anyway I think the thread might not be quite dead yet. KB3197356 doesn't show up in microsoft updates and so one needs to run the msu file I linked to in order to update the system to build 14393.223.
     
  7. tywebb13 thread starter macrumors 68020

    Joined:
    Apr 21, 2012
    #7

Share This Page