Win8china: Windows 8.1 2014 Update(Spring GDR) Expected in March, Release in BUILD


Recommended Posts

So, just to double check here, is WIMboot something OEMs can put off of the SSD, like say on a ROM on the device that you would then flash to update the OS in the future?   It did say it supports SSD and eMMC only,  are we looking at more of a LiveCD, USB Boot/Windows on the Go type option for OEMs to preload on hardware without doing the whole install process, just flash the image and done?  

 

If it's how I think, and how it sounds, then how much space are we actually saving here?

I dont think saving space is the reason.

I think its "less time = less money"

If they can do less, and all charges stay the same - the OEMs score a big one.

Is that what you were referring to, or did I completely take things out of text ?

If they [OEM] save 1 minute on imaging a new machine that equates to substantial time management benefits.

1 minute x 100,000 machines annually = 100,000 minutes/60 minutes = over a month.

I dont think saving space is the reason.

I think its "less time = less money"

If they can do less, and all charges stay the same - the OEMs score a big one.

Is that what you were referring to, or did I completely take things out of text ?

 

Saving time and money is part of it as well but they've talked about supporting smaller and cheaper devices that only have 16GB of storage and 1GB of ram.  So the OS footprint has to have shrunk, right now a default 8.1 install for the OS alone will take something like 8GB or more, not really good for a cheap tablet that's only got 16GB of space.

  • 2 weeks later...

Neowin News had reported about this win8.1 new version 9600.17042 displayed in the MS KB article

 

https://www.neowin.net/news/newer-version-number-for-windows-81-update-1-revealed-on-microsoft-support-page

 

Seems some guys didn't catch the point,The KB itself is trivial, and it properly won't change any build nos.; what it said in the "additional files" section means that it could be installed on a win8.1 build 9600.17042.

 

AFAIK, KB's usually refer to the "base version"(version displayed in DISM), currently in my win8.1Pro, msinfo32 reports 9600.16500, DISM reports the RTM 9600.16384 .  :)

 

 

i.e.: On Mar 9, KB294155 is eligible to be installed on an existing win8.1 build that reports a base version 9600.17042 ..... need I say more?

 

  • Like 2

A MDL member has posted an image "said to be" from OEM's (note: cannot verify if it's real or not), if it's real, then it means the leaked MSU's from WZOR might not be the final release; because if you look at the folder for the most important update KB2919355, if it only consist of the 3 MSU's, it is still larger than the WZOR leak X64+X86+RT combined. 

 

 

BN9bmCx.jpg

 

Note that, even so, it only means that the leaked update1 pack might not be final, but as WZOR has reported, and I have also said a few times before, build 9600.17031 is the RTM . And in the download request page of KB2941455, MS has actually unofficially confirmed it, because this KB has to be installed on a RTM platform, and has even called Update1(build 9600.17031) as "SP1".

 screen1596.jpg

This might be a dumb question - but is it possible that the updates that are delivered to OEMs are not "bundled" the same as the files that were leaked by WZOR?  What I mean is, how do we know that what is inside of each of those folders is not an uncompressed version of the files that were leaked by WZOR and on Windows Update?  This would be more convincing if we were looking at an actual MSU file for KB2919335 that was a different size than the leaked version.

This might be a dumb question - but is it possible that the updates that are delivered to OEMs are not "bundled" the same as the files that were leaked by WZOR?  What I mean is, how do we know that what is inside of each of those folders is not an uncompressed version of the files that were leaked by WZOR and on Windows Update?  This would be more convincing if we were looking at an actual MSU file for KB2919335 that was a different size than the leaked version.

We don't know, unless there would be more infos of the contents in these folders. :)

 

Update: Now we have the infos, it's because the servers MSU's are added:

 

a6119d3e5ddd1a233a09dd79d91067de7b826f85 *KB2919355\Windows8.1\ARM\Windows8.1-KB2919355-arm.msu
e6f4da4d33564419065a7370865faacf9b40ff72 *KB2919355\Windows8.1\X64\Windows8.1-KB2919355-x64.msu
de9df31e42fe034c9a763328326e5852c2b4963d *KB2919355\Windows8.1\X86\Windows8.1-KB2919355-x86.msu
e6f4da4d33564419065a7370865faacf9b40ff72 *KB2919355\WindowsServer2012R2\X64\Windows8.1-KB2919355-x64.msu
506ed7113697c597c2859d295d562fa4311834ec *KB2919442\Windows8.1\ARM\Windows8.1-KB2919442-arm.msu
f97d8290d9d75d96f163095c4cb05e1b9f6986e0 *KB2919442\Windows8.1\X64\Windows8.1-KB2919442-x64.msu
94ee3d715e732ed28c64b8096327375a35f5d211 *KB2919442\Windows8.1\X86\Windows8.1-KB2919442-x86.msu
f97d8290d9d75d96f163095c4cb05e1b9f6986e0 *KB2919442\WindowsServer2012R2\X64\Windows8.1-KB2919442-x64.msu
fe6acf558880d127aef1a759a8c2539afc67b5fb *KB2932046\Windows8.1\ARM\Windows8.1-KB2932046-arm.msu
6aee5fda6e2a6729d1fbae6eac08693acd70d985 *KB2932046\Windows8.1\X64\Windows8.1-KB2932046-x64.msu
bfd8ca4c683ccec26355afc1f2e677f3809cb3d6 *KB2932046\Windows8.1\X86\Windows8.1-KB2932046-x86.msu
6aee5fda6e2a6729d1fbae6eac08693acd70d985 *KB2932046\WindowsServer2012R2\X64\Windows8.1-KB2932046-x64.msu
860c83a0cccc0519111f57a679ae9f9d071315e5 *KB2937592\Windows8.1\ARM\Windows8.1-KB2937592-arm.msu
4abc0a39c9e500c0fbe9c41282169c92315cafc2 *KB2937592\Windows8.1\X64\Windows8.1-KB2937592-x64.msu
96a3416d480bd2b54803df26b8e76cd1d0008d43 *KB2937592\Windows8.1\X86\Windows8.1-KB2937592-x86.msu
4abc0a39c9e500c0fbe9c41282169c92315cafc2 *KB2937592\WindowsServer2012R2\X64\Windows8.1-KB2937592-x64.msu
d4004710f89d5b328e0f9e6446c2bc82b5fba9f6 *Readme.txt

http://forums.mydigitallife.info/threads/52611-DISCUSSION-Windows-8-1-Spring-2014-Update-RTM/page189?p=888406&viewfull=1#post888406

 

Looks like the hashes are identical to those files leaked by WZOR and through WU.  This should confirm that the files leaked are the final 17031 RTM.

http://forums.mydigitallife.info/threads/52611-DISCUSSION-Windows-8-1-Spring-2014-Update-RTM/page189?p=888406&viewfull=1#post888406

 

Looks like the hashes are identical to those files leaked by WZOR and through WU.  This should confirm that the files leaked are the final 17031 RTM.

Yup, Those msu's comes with manufacturing documents for OEM's, so, it's final.

 

What's interesting to know will be: If the public(MSDN) release include another rollup, like what they did in last Oct. for win8.1 GA. :)

 
MS has announced RTM of SQL Server 2014, and release on April 1.....

http://blogs.technet.com/b/microsoft...z&country=zUSz

Wondering ........ will they also release win8.1Update1 on this famous day too?  :rolleyes:

MS Direct download links to the 6 KB's :  :)

 

 
 
  • Like 3

I'm just going to wait for WU, besides I haven't updated anything other than defender since back in early February.  Last time I restarted was over 9 weeks ago!

 

 

MS has announced RTM of SQL Server 2014, and release on April 1.....

http://blogs.technet.com/b/microsoft...z&country=zUSz

Wondering ........ will they also release win8.1Update1 on this famous day too?  :rolleyes:

 

From the comments section in Neowin  News:

 

 

screen1616.jpg

 

....and tks @seeprime  :)

I was the one that liked that comment :p

Oh! Reminds me to like it too. :D

 

Actually I have caught some wind on this, but if I said it, people will flame me for "celebrating that special day".

  • 2 weeks later...
This topic is now closed to further replies.
  • Posts

    • Absolutely NOBODY has suggested such a conclusion. I am affirming the sober reality check that AV2's overall market adoption will take longer than AV1's adoption rate -- which, by the way, is the whole point of the article! While PCI-SIG is productive (on paper), other WGs have created all sorts of confusing progress plans that consumers have tuned-out of their improvements... HTML/W3C, USB, HDMI, BT, WIFI (ieee802.11) as a few other groups where spec naming conventions, split progress paths, overlapping ambitions... I'm not critiquing the AV specs group; I'm simply affirming that adoption for AV2 faces headwinds beyond the macroeconomics of it all.
    • Segra 1.5.2 by Razvan Serea Segra is a free, open-source OBS-powered game recorder offering fast gameplay capture, instant clips, AI highlights, deep game integration, and seamless uploads—perfect for gamers, streamers, and content creators. Lightweight, fast, zero bloat. Segra key features: Automatic Game Recording: Begin capturing gameplay the moment your game launches, with zero manual setup. Instant Clipping: Save important moments instantly using a customizable hotkey—perfect for highlights, montages, or quick shares. Segra AI Highlights: Let Segra automatically detect kills, assists, deaths, and key events to generate polished highlight reels without manual editing. Gameplay Uploads: Upload recordings and clips directly to Segra.tv for fast sharing and cloud access. Deep Game Integration: Enjoy advanced game-data tracking across hundreds of supported titles, enabling smart highlight generation and stat-informed clipping. High-Performance Capture: Record up to 4K at 144 FPS using OBS-powered technology with minimal performance impact, supporting NVENC, AMD VCE, and custom quality controls. Segra Editor: Edit recordings easily with timeline controls, segment management, and event-based navigation to build the perfect clip. Customization Options: Adjust hotkeys, output formats, storage paths, codecs, capture quality, and performance settings for a tailored recording experience. Segra 1.5.2 changelog: Settings: Added an Airplane Mode that hides account, login, and upload features. Storage: Added a button to migrate videos into the recording path after changing it. Import: Added auto-scroll and a highlight pulse to videos right after importing. Recording: Added graceful handling of low disk space and output failures, finalizing files safely with clear errors. Recording: Added a guard blocking recording when any drive exceeds 99% full. OBS: Removed the download timeout to support users with slow internet. Clips: Fixed an error modal incorrectly appearing when clip creation was cancelled. Settings: Fixed the content folder path not refreshing in the UI after changes. Updates: Improved error handling for multiple simultaneous update checks. Stability: Fixed a WebSocket reconnect loop that ran while the window was backgrounded. Dependencies: Updated project dependencies. Maintenance: Removed dead code, reduced duplication, and fixed several latent bugs. Download: Segra 1.5.2 | 73.1 MB (Open Source) View: Segra Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • No thanks! WebView trash is unacceptable. I only use software that's native.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      465
    2. 2
      PsYcHoKiLLa
      244
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      69
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!