Hello, Does anyone know is this something new in IE11 in this build? I mean those back and recent pages toolbar buttons. I believe this screenshot should show them. Spoiler
when installing this version with uup iso in bios mode, it creates 3 partinions, 1 50mb boot, 1 system partition, 1 470mb recovery, its new, windows 7 image backup fails due to first small 50mb partition has some one test this scenario with Techbench dump new isos? saludos
It's not UUP related, 19041.84 Techbench ISOs have the same problem. Best will be to create a win10xpe iso, boot it and use macrium reflect to create an image. https://forums.mydigitallife.net/threads/winpe-build-your-own.78922/
In the current situation, we might be seeing a replay of essentially ignoring the Summer release (20H1) and gearing up for the Fall release (20H2)
Yes I took this one (with the link of the 1st post) If I want to stay with a (basic) build 19041.1, do I have to stay with the UUP build ? The ISO that Microsoft will make available when the 2004 version is released will be in 19041.xxx I suppose
MSFT already released a 2004/20H1 ISO/ESD, it's 19041.84, since the re-release (msft considers it the official release) of 1809 as being 17763.107 they released 1903 as being 18362.30, so no first ISO/ESD release of any build without pre-integrated updates since then. UUP is the only option to get 18362.1 and 19041.1.
Yes I use ISO 18362.1 (UUP) to have the 1909 I'm just surprised at the date of the files from 19041.1 (December 2019) Thanks
Just updated to 20H1 from 1909. So far so good. Notepad, WordPad, and DiskCleanup work fine... GPU temp shows in the Task Manager as well. According to MS, it only works with discrete GPUs for now. (saw a few people above had issues with those programs). WSL2 is cool and runs fast. I did have trouble in direct conversion from WSL 1 so just uninstalled Ubuntu and reinstalled from the Store. However, it now requires Hyper V to be enabled, which means some apps such as Ryzen Master and Bluestacks don't work. I don't think it is MS's fault, though. Not many cosmetic changes, which is good (or bad, depending on your preference). Didn't notice much diff in overall responsiveness.
2004 (april 2020) and décember 2019 18362.1 (1903) has a date of March 2019 Nothing annoying, just surprised at the release so early EDIT : I tried ISO 19041.1 (UUP) and ISO 19041.84 (Insider) By integrating CU .153, some Manifests files and corresponding files are not updated with the 19041.1 (compared to the 19041.84), some examples Code: 19041.1 => 19041.153 : WinSxS\Manifests\amd64_netfx4-presentationnative_b03f5f7f11d50a3a_4.0.15805.0 WinSxS\Manifests\amd64_netfx4-workflowserv..ormancecounters_dll_b03f5f7f11d50a3a_4.0.15805.0 WinSxS\Manifests\amd64_netfx4-wpfgfx_b03f5f7f11d50a3a_4.0.15805.0 Code: 19041.84 => 19041.153 : WinSxS\Manifests\amd64_netfx4-presentationnative_b03f5f7f11d50a3a_4.0.15805.101 WinSxS\Manifests\amd64_netfx4-workflowserv..ormancecounters_dll_b03f5f7f11d50a3a_4.0.15805.101 WinSxS\Manifests\amd64_netfx4-wpfgfx_b03f5f7f11d50a3a_4.0.15805.101 So it's not just CU .84 integrated into ISO 19041.84 ?
Were you connected to the Internet during the upgrade? How about Paint? (I mean the classics Paint) Please also could you compare IE in this build with IE in 1909 if you still remember it? Do you have those extra "back" and "recent pages" toolbar buttons? Thank you.
@abbodi1406Hello, can this be a concern? EDIT: Just missed this one before writing the above. I just thought tistou77 should included KB4534170 when integrading. OK so it's fine. Take care.
I hope this is good time to install this build. With number of advanced users here giving positive feedback, it is safe to install this build on main machine. What do you think is the road map for announcing this build out of Insider Preview?
Nobody knows, given the worldwide special circumstances, how this goes. I would wait till the defrag/optimize bug is fixed.
Apart from that there seems to be no serious problems with this build and current version. (I hope there are not.) . This impression I have gathered by reading through this thread.
What is this bug? Seams everyone except me have this what they call bug. Guys/Gals, maybe you just need to make sure your IDE ATA/ATAPI controllers drivers are compatible with this build? As said before and even posted a picture (I am now regret of doing it, actually!) I'm not having any issue with my Samsung SSD 950 NVMe drive. I also connected at least 3 different SATA SSDs for servicing them to my Intel SATA AHCI Controller and I had no such issue. (Using Intel AHCI driver version 17.7.0.1006) And of course no issue when defragmenting mechanical drives either. Please, somebody without showing a picture, tell me what's this defrag/optimize issue all about?