New
#180
@lmod If you have the option in Vipre, unregister it in Windows. That's what I did with MBAM, and all is fine, both run with all options.
All worked perfectly on my laptop. I have no idea why the files were not there on the Oracle VM but they were not.
I'll try it again by putting 15031 back n the VMthen upgrade to 15042 and see what happens.
Could it have anything to do with UUP being off on the VM? I know it shouldn't but ...
I don't want to start a fight or an argument, I am just stating some facts:
- For Windows upgrade it's absolutely completely totally irrelevant if the system being upgraded is a physical or a virtual machine. A virtual machine behaves and is in every aspect of upgrade as any physical machine
- Saying that in UUP upgrade method the Insider build upgrade files (including 10+ ESD files) were not in a specific subfolder in C:\Windows\SoftwareDistribution\Download is absolutely not true. In build 15042 upgrade that specific folder was / is d00630587706295696417aabf4685ed4
- Without those files in said folder upgrade is / had been impossible.
I repeat: it is not possible to upgrade to Windows 10 Insider Build 15042 using UUP method / Windows Update without having those upgrade files in folder d00630587706295696417aabf4685ed4. It is absolutely impossible.
Kari
Nope, no fight, just discussion :)
As I said, the laptop went smooth and all worked perfectly. ISO generated and saved along with the zipped up UUP folder.
Thanks for all your work on this Kari. It's been a great help throughout the Insider program.Code:=============================================================================== Convert CAB > ESD . . . =============================================================================== =============================================================================== Creating Setup Media Layout . . . =============================================================================== =============================================================================== Creating boot.wim . . . =============================================================================== Using LZX compression with 2 threads Archiving file data: 871 MiB of 871 MiB (100%) done =============================================================================== Creating install.wim . . . =============================================================================== Using LZX compression with 2 threads Archiving file data: 7088 MiB of 7088 MiB (100%) done =============================================================================== Adding winre.wim to install.wim . . . =============================================================================== =============================================================================== Creating ISO . . . =============================================================================== OSCDIMG 2.56 CD-ROM and DVD-ROM Premastering Utility Copyright (C) Microsoft, 1993-2012. All rights reserved. Licensed only for producing Microsoft authorized content. Scanning source tree (1500 files in 54 directories) Scanning source tree complete (1705 files in 99 directories) Computing directory information complete Image file is 4085874688 bytes (before optimization) Writing 1705 files in 99 directories to 15042.0.170219-2329.RS2_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO 100% complete Storage optimization saved 20 files, 516096 bytes (0% of image) After optimization, image file is 4089067520 bytes Space saved because of embedding, sparseness or optimization = 516096 Done. Press any key to exit.
Thought I remembered seeing a post in this thread that said roll back wasn't working.
I just tried it and was successful going from 15042 back to 15031. Took less than 10 minutes.
Turned UUP off again via the registry change and I just started toe 15042 upgrade again.
Will see what happens this time.
I had to roll back to AU on my gaming machine again. Every 15xxx build so far has been a disaster in terms of gaming for me so far. This build had games dropping down to 1 FPS ever few seconds, making them unplayable. Filed feedback before rolling back, so hopefully it catches Microsoft's eye.