Download Windows 10/11 ESD

[Drone]

Windows RS4 launch date cancelled to big bug... maybe we should have waited? LOL

http://www.guru3d.com/news-story/mi...ring-update-after-spotting-extensive-bug.html

Lol with so many builds around I always wonder who on earth is gonna test them all. RS3 wasn't super awesome but RS2 was good.

 

[Hood]

@Drone, your recent post of 1803 RS4 won't let me do a soft upgrade, because it's a different edition from mine (I have Pro, yours seems to be Home) It will only let me do a hard reinstall, not keeping apps and files.
I assume my Windows key won't work with this anyway, and even if it does, I don't want to change to Home Edition. Any plans to post a Pro version?

 

[Space Lynx]

@Drone, your recent post of 1803 RS4 won't let me do a soft upgrade, because it's a different edition from mine (I have Pro, yours seems to be Home) It will only let me do a hard reinstall, not keeping apps and files.
I assume my Windows key won't work with this anyway, and even if it does, I don't want to change to Home Edition. Any plans to post a Pro version?

we are only about 1 week away from official release, might as well wait at this point

 

[StrayKAT]

we are only about 1 week away from official release, might as well wait at this point

Darn.. I thought it'd be released today. A week you say? Oh well. I figured it'd be a on Tuesday though (seems the norm).

 

[Drone]

@Hood it's not home, it's all in one

@StrayKAT Nope, they just released another insider version

Today, we are releasing Windows 10 Insider Preview Build 17134 (RS4) to Windows Insiders in the Fast ring. This build has no new features and includes the fixes from KB4100375 as well as some fixes for general reliability of the OS. As Build 17133 progressed through the rings, we discovered some reliability issues we wanted to fix. In certain cases, these reliability issues could have led to a higher percentage of (BSOD) on PCs for example. Instead of creating a Cumulative Update package to service these issues, we decided to create a new build with the fixes included. This just reinforces that Windows Insiders are critical to helping us find and fix issues before releasing feature updates to all our customers so thank you!

The real thing is delayed

 

[jsfitz54]

@Drone : Will the new build 17134 require a reinstall? If I'm on 17133.73 will that get patched to the new version?

 

[Drone]

@jsfitz54 If you're on fast ring it will be updated but if not then you might wait till final build or when they push it on the slow ring. You can do a clean install (format) or upgrade from 133 to 134

 

[Hood]

@Hood it's not home, it's all in one

I was going to install it anyway, but my system insists that this image is Windows 10 Home. Then I tried to set up a clean install, and it says Windows can't be installed on this drive, because it can't boot from it (tried all my drives, same warning). So something is wrong, I've never had this problem before. I'll just wait for Windows update and see how that works.

 

[jsfitz54]

I was going to install it anyway, but my system insists that this image is Windows 10 Home. Then I tried to set up a clean install, and it says Windows can't be installed on this drive, because it can't boot from it (tried all my drives, same warning). So something is wrong, I've never had this problem before. I'll just wait for Windows update and see how that works.

If you download x64 version into a new folder and also download the Decrypter into the same folder (ALL IN FIRST POST) then run the Decrypter paying attention to what selections are made ( I believe #1 and #1) then it does all versions. I then mount the created ISO image to a USB drive using RUFUS to make a bootable drive.

I think your hangup is in what you are selecting using the Decrypter tool.

 

[Hood]

I figured it out - I didn't notice the decrypter on the first page below all the older esd files, so I used one that I found somewhere else, and it didn't have the options for different Windows editions. Once I used the right decrypter, everything worked fine to just do the upgrade, keeping files, apps, and settings. How stupid of me... anyway, it worked perfectly, no bugs noticed. I've been on a roll with these major updates, no problems at all since the earliest Win10 builds (Threshold 1 & 2).

 

[jsfitz54]

I figured it out - I didn't notice the decrypter on the first page below all the older esd files, so I used one that I found somewhere else, and it didn't have the options for different Windows editions. Once I used the right decrypter, everything worked fine to just do the upgrade, keeping files, apps, and settings. How stupid of me... anyway, it worked perfectly, no bugs noticed. I've been on a roll with these major updates, no problems at all since the earliest Win10 builds (Threshold 1 & 2).

Now that you did that update you need to run a CAB file update SEE POST 345 and this page:
#345

Download KB4100375 x64 first CU for 1803

https://www.tenforums.com/tutorials/66170-cab-file-add-install-context-menu-windows-10-a.html

That will get you to 17133.73.

 

[erpguy53]

Lol with so many builds around I always wonder who on earth is gonna test them all. RS3 wasn't super awesome but RS2 was good.

The 1703 (RS2) release was incompatible with some old machines (desktop & laptop PCs) that have integrated Broadcom 440x 10/100 Ethernet/LAN adapters - and this was a known problem (tenforums topic) (ms answers forum topic), which the RS2 version would hang/freeze on either the startup screen or on the desktop screen. It took Microsoft several months (with releasing either the KB4032188 or KB4034674 cumulative update for RS2) to fix the "hanging" problem but the RS3 1709 release fully fixed it.

yup the real 1803/1804 release is delayed maybe until either next Tuesday 4/24 or end of April (maybe 4/30)? I don't mind waiting a little longer.

 

[Hood]

Now that you did that update you need to run a CAB file update SEE POST 345 and this page:
#345

Download KB4100375 x64 first CU for 1803

https://www.tenforums.com/tutorials/66170-cab-file-add-install-context-menu-windows-10-a.html

That will get you to 17133.73.

Thank you. I had trouble getting the install command on the cab file context menu, had to run a registry file, and still no install command, until I changed the default file association for .cab files , to open with file explorer, not winrar. All good now. I'm at 17133.73 now. Thanks again.

 

[Drone]

Cumulative Update for Windows 10 1709 (build 16299.402)

760 MB

KB4093105 x64

 

[Drone]

Okay ...

Microsoft Windows 10 Spring Creators Update (version 1803 aka RS4, build 17134.1) (April 2018)

is out, check the op

 

[FordGT90Concept]

^ Insider Preview

 

[Mussels]

wait, so if i update to that i'm stuck on insider?

 

[Drone]

wait, so if i update to that i'm stuck on insider?

Who says it's insider? It's OEM retail, you can see the link

 

[Mussels]

ford said it, i just panicked cause i'm about to install

 

[FordGT90Concept]

Spring Creators Update is not released for public consumption yet. "build 17134.1" is still Insider Preview.

 

[Drone]

@Mussels
I don't post insider builds here

 

[FordGT90Concept]

Yes, you do:

I have MCT downloading.

That wasn't official Spring Creators Update. That was still Fall Creators Update. What you linked is a release candidate. Microsoft can still say "nope" and delay it again.

When Spring Creators Update drops, it will get a lot of media coverage.

 

[jsfitz54]

@Drone : You could remove the 17133.1 from the first post, as that was not a final build and 17134.1 supersedes it.

EDIT: 1 laptop and 1 desktop updated. Seems quicker.

 

[Mussels]

updated and installed, while it may be a preview build there is no indications of it being insider, or limited in any way.

defaulted to HDR on in windows settings and looked horrible with washed out colors, turning that off looks heaps better. Have no idea why HDR on looks garbage, but HDR off has better colours but its been this way for a while.

 

[Eroticus]

Yes, you do:

That wasn't official Spring Creators Update. That was still Fall Creators Update. What you linked is a release candidate. Microsoft can still say "nope" and delay it again.

When Spring Creators Update drops, it will get a lot of media coverage.

He also posted Fall Creators Update before all the media jumped on the train....