Download Windows 10/11 ESD

[FordGT90Concept]

Another thing to check is make sure C: has many GB available space. Everytime I run MCT, I see two hidden $Windows (I think it was) created in C:\

 

[Octopuss]

It worked fine for me when I used it. But it's sort of pointless to use it for the 17134.1 ESD at this point anyway. Since, like he says, you can download an ISO of 17134.1 with the Media Creation Tool. Or, rather, have it download the 17134.1 ESD and create an ISO of it for you. Which, technically speaking, is the correct description of the process. Whatever...same diff.
View attachment 100478

Um, no. The iso you download with the tool contains ESD and not WIM image, so it doesn't help.

 

[RejZoR]

In theory, only difference between ESD and WIM is compression technique, making ESD a lot smaller (but more CPU intense during installation). Also, majority of guides, like for DISM are written for WIM and do not work with ESD. I did see some guides where you can convert ESD to WIM using some built in Windows tool.

You can get WIM images (ISO) from here: http://windowsiso.net/

But they usually take some time to upload them.

 

[MrGenius]

Um, no. The iso you download with the tool contains ESD and not WIM image, so it doesn't help.

Seriously? Are you really that clueless?

 

[RejZoR]

If he's using WIM installed OS, ESD version will be problematic for certain things (like when using DISM).

 

[Octopuss]

Seriously? Are you really that clueless?

I don't even know what are you talking about, and I don't like your attitude.

 

[Octopuss]

Found a solution: https://www.intel.com/content/www/u...2/memory-and-storage/intel-optane-memory.html

 

[atanas dimitrov]

I am having a issue with this update,. I fallow the steps via windows update, DL the update, shows install. ask me to reboot pc. after reboot its start the update install pc reboot several times. On the last time, I get a message saying" Restoring windows to previous version". Then it takes me back to windows, and i get a message update could not be installed.
In windows update-control panel it shows update waiting for reboot. i click on it and does same thing. after install it restore to previous version. what is going on?
I have disable windows firewall for time being.
specs
Z97 Pro gamer MB 4790k @4.7 DDR3 2400 RAM Win10 x64 M.2 and SSD.

 

[Drone]

Maaaaaaaaan 1803 is pile of poo

Some people have problems with edge, others with ie, chrome, and other apps. Hangs freezes, crashes. Microsoft says they will fix this crap on May 8th

*sigh*

https://www.ghacks.net/2018/05/01/all-the-issues-of-windows-10-version-1803-you-may-run-into/
https://windowsreport.com/windows-10-april-update-pc-freezes/
https://windowsreport.com/windows-10-april-update-pc-freeze/
https://www.bleepingcomputer.com/ne...s-and-timeouts-after-windows-10-april-update/
https://www.windowslatest.com/2018/05/03/how-to-fix-freezing-issues-in-windows-10-april-2018-update/

 

[FordGT90Concept]

Can't say I've really had any problems.

 

[MrGenius]

Yeah...I've been getting random crashes(1-3 times a day) while using Edge. I also spent like a day and a half trying to figure out what/why/how the (Recovery Partition) is now an (OEM Partition). Did a bunch of update, downdate, update again, and clean installs to try and figure out what's up with that. Conclusion: Because it just is. And it doesn't really matter what it's called. It's the same thing either way. DISKPART still says its Type is Recovery anyway. So whateva. I guess I don't care that much. As long as it's still good for what it's good for(and it appears as though it still is). I just don't like the word "OEM" associated with my totally non-OEM retail Windows 10 Pro install. But I haven't found a way to do anything about it. So it is what it is I suppose...

Disk Management 1709

Disk Management 1803

 

[Hood]

@MrGenius - when you build a system, you are the OEM - it's a one-off prototype. Basically you're one person doing what normally takes a whole company, like Dell or HP.

 

[MrGenius]

That may be true. But there's supposed to be a difference between what's labeled as a "Recovery Partition" and what's labeled as an "OEM Partition". A "Recovery Partition" is supposed to be relatively small(< 1GB), and just be a convenient place to hold the Windows RE(Recovery Environment). Basically, just so the OS can run automatic startup repairs without needing to load anything from the installation media. An "OEM Partition" is, typically, relatively much larger(> 1GB), and is put there by actual OEMs(Dell, HP, Lenovo, etc.) so that the entire OS can be restored to factory settings, without needing to use the installation media. And an "OEM Partition" doesn't also hold the Windows RE. So if there's an "OEM Partition" there's also, technically, still a need for a "Recovery Partition". Because they're not supposed to be the same thing. Hence the different names. That's the way it's always been anyway. I don't know what they've decided to do now. But it doesn't make much sense. I hope it's something that gets put back the way it was. Because it's just going to lead to confusion otherwise. I'm sure I'm not the only one scratching his head and wondering W T F is this all about?

 

[RejZoR]

OEM Partition or Recovery partition is the same thing, they just call it differently now it seems. OEM Partition or Recovery Partition have the same function, restore factory system. It's only used by OEM's like HP, Dell and the likes. It's kinda redundant if you use a Refresh Function, plus Refresh doesn't restore all the OEM garbage.

I usually refresh such systems, delete the OEM partition and extend the normal one to gain some extra space.

 

[Octopuss]

Is there any point in recovery partition when I have homebuilt computer?

 

[RejZoR]

There is no 3rd dedicated recovery partition when you're installing Windows 10 yourself.

 

[atanas dimitrov]

so what to do after DL this, i do not want lose any data, i just want update to 1083, however i cannot, after install and reboot, it says restoring to previous version.

 

[MrGenius]

Is there any point in recovery partition when I have homebuilt computer?

For the convenience of not having to use the installation media for startup repairs. But you should be able to use your installation media to do whatever the recovery partition does(including startup repairs). AFAIK. I could be wrong about that though.

There is no 3rd dedicated recovery partition when you're installing Windows 10 yourself.

I'm not sure if I follow you there. But if you clean install Windows 10 there will be at least 3 partitions.

• (EFI System Partition)
• (Primary Partition)
• (Recovery/OEM Partition)

If you install from an OEM installation media there might(should?) be 4 partitions. Since there might(should?) be a Recovery partition and an OEM partition.

Back on topic...

Download May 8 CU KB4103721 x64 (326.5MB)

Brings system to 17134.48

List of improvements and fixes found here.

 

[RejZoR]

Don't mix up Windows Recovery partition with THE Recovery partition by OEM. One is always in front, OEM ones are at the end. You don't seriously believe those 350MB holds entire system backup and all the crap OEM's bundle with laptops? This recovery partition only holds basics to make system bootable and I think some partition information for partition recovery. And that's it.

First two are basically system recovery partitions, C: and D: are user partitions (although C: holds some system data like Windows itself).

 

[MrGenius]

Download May 23 CU KB4100403 x64 (426.7MB)

Brings system to 17134.81

List of improvements and fixes found here.

 

[MrGenius]

Download June 12 CU KB4284835 x64 (533.3MB)

Brings system to 17134.112

List of improvements and fixes found here.

 

[Drone]

KB4338853 Servicing stack update for Windows 10 v1803 x64 - June 26 (13.1 MB)
There are no prerequisites for installing this update.
You don't have to restart the computer after you apply this update.
This update doesn't replace a previously released update.

Cumulative Update KB4284848 Windows 10 v1803 Build 17134.137 x64 - June 26 (633 MB)

Improvements and fixes

This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

• Addresses an issue that causes the Video Settings HDR streaming calibration slider to stop working. This is caused by a conflict with the panel brightness intensity settings configured by certain OEMs.
• Addresses streaming compatibility issues with certain live TV streaming content providers.
• Addresses an issue where media content previously generated by Media Center doesn't play after installing the Windows 10 April 2018 update.
• Addresses an issue in which SmartHeap didn't work with UCRT.
• Addresses performance regression in App-V, which slows many actions in Windows 10.
• Addresses an issue that causes Appmonitor to stop working at logoff if the Settingstoragepath is set incorrectly.
• Addresses an issue that causes Appmonitor to stop working at logoff, and user settings are not saved.
• Addresses an issue where client applications running in a container image don't conform to the dynamic port range.
• Addresses an issue where the DNS server might stop working when using DNS Query Resolution Policies with a "Not Equal" (NE) condition.
• Addresses an issue with T1 and T2 custom values after configuring DHCP failover.
• Addresses an issue that causes the latest versions of Google Chrome (67.0.3396.79+) to stop working on Cobalt devices.
• Addresses issues with the Remote Desktop client where pop-up windows and drop-down menus don't appear and right-clicking doesn't work properly. These issues occur when using remote applications. Before installing this update, read KB4340846, “The Remote Desktop Services ActiveX control (mstscax.dll) does not match the version of the client shell”.
• Addresses an issue that causes a connection failure when a Remote Desktop connection doesn’t read the bypass list for a proxy that has multiple entries.
• Addresses an issue that may cause Microsoft Edge to stop working when it initializes the download of a font from a malformed (not RFC compliant) URL.
• Addresses an issue where some users may receive an error when accessing files or running programs from a shared folder using the SMBv1 protocol. The error is "An invalid argument was supplied".
• Addresses an issue that causes Task Scheduler tasks configured with an S4U logon to fail with the error "ERROR_NO_SUCH_LOGON_SESSION/STATUS_NO_TRUST_SAM_ACCOUNT".

Important
If you install from Microsoft Update catalog then install servicing stack update (KB4338853) before installing latest cumulative update.

 

[Drone]

New Windows is out. Refresh download link in the OP

 

[MrGenius]

New CU today too..

Download July 10 CU KB4338819 x64 (676.6MB)

Brings system to 17134.165

List of improvements and fixes found here.

Here's the download link for the new servicing stack update KB4343669 x64 (13.3MB)

Install before the latest cumulative update.

 

[Octopuss]

New Windows is out. Refresh download link in the OP

How did you find this? It appears to be Microsoft-made, considering the link. Do they actually release updated images?
I presume it's just with all the updates already integrated, or is there anything more to it?