"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. "
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
It still says 14393.0.amd64fre.rs1_release.160715-1616 in registry. Even after DISM-ing the CAB online. )
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.
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.
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
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).
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.
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 ---------------------------
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.
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