Windows 8.1 9600.16384 RTM INFO.


Recommended Posts

Ok small update peeps. Windows 8.1 x64 Enterprise leaked in Chinese. Now i been doing some messing about to convert bits to english and this is what i have so far.

 

 

 

 

 

 

Is it even worth the effort to convert stuff to English, when 1: your hacking together the OS and it probably won't be 100% correct, 2: The english leak will be out likely in the next 2-3 days at most, and 3: IF not Oct isn't that far away to have an OS without modifications all hacked into it.

 

Just saying.

Is it even worth the effort to convert stuff to English, when 1: your hacking together the OS and it probably won't be 100% correct, 2: The english leak will be out likely in the next 2-3 days at most, and 3: IF not Oct isn't that far away to have an OS without modifications all hacked into it.

 

Just saying.

 

I have not changed any system files at all only used Genuine 8.1 RTM files :) Not even touched a resource hacker or hex editor to do the above. Also know there is no point (that's why this is installed in a VM, just makes it easier to convert bits to English for exploring). As for English language that will come tomorrow (apparently). 

 

All you do is upgrade windows 8 English to 8.1 and change region / language settings to get the above result ;) I have not done it yet but once settings are changed i think you can remove apps left in chinese and then install the english ones from store. So its a simple 5 min thing to do no messing about really and makes it more easy to explore. 

He's still going to leak builds apparently (via other means it seems).

 

So yeah, latest news... the install.wim file that leaked today was corrupted, but was 'fixed' only to be found it's faulty and can't be used to upgrade and it throws errors on things like .NET 4 applications. Wzor posted on a Russian forum that he has the builds ahead of the September 1st date he thought they'd leak, and is probably going to leak them as soon as they're checked to be 100% complete (100GB of files to check and verify).

 

So yeah, not long now.

 

 

So, has a not-modified ISO already leaked?

 

Not yet, Wzor will leak them soon hopefully.

Some places including here, are saying no they cannot be.  Who is right?

 

It seems to me that there is some confusion about Retail vs MAK vs KMS in regards to what can be updated with the same key.

 

But Retail is pretty much safe from any perspective it seems.

I've upgraded and the install didn't accept my retail Pro key but yes, Win8 to win8.1 can be upgraded but through another way.

I have a legit 8,  it came pre installed, with no key because they're "Flashed" into the bios,  or whatever they decided with microsoft,  will it work correctly?

I have a legit 8,  it came pre installed, with no key because they're "Flashed" into the bios,  or whatever they decided with microsoft,  will it work correctly?

 

Good question, I'm not sure honestly... :/ Maybe try to get/write the key down from the Bios and then try installing it? Or you could just try it and hope it works.

A MAK key should work depending on the number of activation left...So Upgrading from 8.0 to 8.1 is not possible? Only clean install?

 

The best you can do using the ISO, is to keep your files/settings .. you will need to re-install your apps, or upgrade through the Windows Store in October.

Good question, I'm not sure honestly... :/ Maybe try to get/write the key down from the Bios and then try installing it? Or you could just try it and hope it works.

 

 

How do I go about trying to find this?  I tired before when I first got it.  I suppose I can wait until October if need be.  Hmm.  

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I sort of agree with you on that. I had a telescope - a real hefty thing, although only around 500CHF - that got me so fascinated about the stars and planets. I would stare for hours, amazed that I could see the craters of the moon or the rings of Saturn in "realtime" (quotations because, y'know, speed of light and whatnot). A friend of mine has a telescope like the one mentioned in the review, and the pictures are amazing to look at. But there is something missing for me. I may as well just go to NASA's website and look through their gallery.
    • As opposed to catching bad press because it's the engine's fault? You didn't really think this through did you? lol
    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!