[DISCUSSION] Windows 10 Final 1607 RS1 Build 14393 + Jan. 2017 Refresh (PC + Mobile)

Discussion in 'Windows 10' started by Enthousiast, Jul 18, 2016.

  1. Flax4

    Flax4 MDL Senior Member

    Apr 10, 2015
    389
    375
    10
    "We have released a Cumulative Update (KB3176925) to Windows 10 Insider Preview Build 14393 on PCs and Mobile devices which will bring the build number to 14393.3. This Cumulative Update includes a handful of fixes:


    • We have fixed an issue where keyboard input on some Windows tablet devices would not rotate to landscape normally.
    • We have fixed an issue that results in Windows Updates being delayed on systems with Connected Standby.
    • We have fixed a problem with text input with Korean Input Method Editor (IME) in some Store apps.
    • We fixed an issue causing Store apps to stop launching due to a licensing issue.
    • We have fixed an issue with apps that synchronize using DDE for inter-process communication. "
     
  2. antonio8909

    antonio8909 MDL Guru

    Feb 16, 2014
    3,116
    1,517
    120
    #862 antonio8909, Jul 22, 2016
    Last edited: Jul 22, 2016
    Hi,

    I'm receiving 14393.3 in Phone named as "Windows 10 Technical Preview for phones (10.0.14393.3)"

    Can I opt out of Insider Build in mobile? I'll receive all updates, right?

    Thanks
     
  3. moderate

    moderate MDL Guru

    Aug 31, 2009
    3,469
    2,485
    120
    #863 moderate, Jul 23, 2016
    Last edited by a moderator: Apr 20, 2017
    It still says 14393.0.amd64fre.rs1_release.160715-1616 in registry. Even after DISM-ing the CAB online. :))
     
  4. MS_User

    MS_User MDL Guru

    Nov 30, 2014
    4,657
    1,361
    150
    looks like by the time we get to august 2 public release mite be 14393.10
     
  5. bjf2000

    bjf2000 MDL Expert

    Apr 11, 2008
    1,101
    199
    60
    I was just counting the ones in System32, which are the ones that are loaded in memory. Winsxs is just a dll cache, an echo of System32.
     
  6. antonio8909

    antonio8909 MDL Guru

    Feb 16, 2014
    3,116
    1,517
    120
    Where you in any ring when you install this update?
     
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,681
    103,558
    450
    It's released to the fast ring and ms_user did download the cabs from 100's post and used the online dism command to integrate the update.
     
  8. genenioo

    genenioo MDL Addicted

    Oct 9, 2007
    654
    113
    30
    #868 genenioo, Jul 23, 2016
    Last edited: Jul 23, 2016
    Downloaded the en-us pro x64 (.esd) and first got an incorrect hash, so I re-downloaded and got the correct hash (same as in the file name--ed8daab17a31489925a8d5e19c77d9d466c36fd7), but then after decrypting the .esd that same .esd went back to the first hash. Anyone experiencing this? Would the hash of the .iso always be the same? My understanding is that they all come out different after decrypting. My .iso is SHA1: A20880E8305EFE26BFCF71D00B80F9A12E5D9458
     
  9. Simple07

    Simple07 MDL Addicted

    Nov 15, 2012
    585
    222
    30
    They are joking, man!!! read the post again, or use google translate..
    And by the way, you will receive updates if you opt out of the insider program (if this is the RTM release or whatever name it is).
     
  10. antonio8909

    antonio8909 MDL Guru

    Feb 16, 2014
    3,116
    1,517
    120
    Ops... I install it via dism. I hope that I'll not get any problems
     
  11. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,681
    103,558
    450
    #871 Enthousiast, Jul 23, 2016
    Last edited: Jul 23, 2016
    (OP)
    After decrypting the checksums of the decrypted esd are different from the original, it would be very impossible to get the same checksums after decrypting.

    And the iso checksums will also never be twice the same, so they can not be verified.
     
  12. genenioo

    genenioo MDL Addicted

    Oct 9, 2007
    654
    113
    30
    What do you make of the .esd hash first being correct and then changing?
     
  13. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,681
    103,558
    450
    #873 Enthousiast, Jul 23, 2016
    Last edited by a moderator: Apr 20, 2017
    (OP)
    After decrypting, the decrypted esd has other checksums, next time use either a copy of the original esd file or use "9" to toggle "backup esd" to "ON".

    The original sha-1 esd of Pro x64 en-US = ed8daab17a31489925a8d5e19c77d9d466c36fd7

    Code:
    ---------------------------
    Checksum information
    ---------------------------
    Name: 14393.0.160715-1616.rs1_release_CLIENTPRO_RET_x64fre_en-us_ed8daab17a31489925a8d5e19c77d9d466c36fd7.esd
    Size: 2969293046 bytes (2831 MB)
    
    SHA1: ED8DAAB17A31489925A8D5E19C77D9D466C36FD7
    
    ---------------------------
    OK   
    ---------------------------
    
     
  14. WardocsRevenge

    WardocsRevenge MDL Expert

    Jan 13, 2012
    1,848
    645
    60
    thread name change to 14393.3 now thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,681
    103,558
    450
    The esd is released as 14393.0 not 14393.3, the updates will be discussed in the "hotfix repository" when it gets released @MSDN/VLSC.
     
  16. 100

    100 MDL Expert

    May 17, 2011
    1,354
    1,589
    60
    Probably comes from NT kernel, and that hasn't been updated yet.
     
  17. MS_User

    MS_User MDL Guru

    Nov 30, 2014
    4,657
    1,361
    150
    why would it give u problems?
     
  18. vipanonymous

    vipanonymous MDL Senior Member

    Apr 3, 2014
    381
    93
    10
    Instead of builds insiderso are getting kbs now? This proves it's definitely the final version. I did a clean install today. I have to say how I miss kickass :D