New
#60
You might have a problem with your UUP2ISO copy because I just created an ISO using it and no error at all.
Perhaps you have something on your computer that is interfering with it, either way I think you should download the tool again it may solve the problem.Code:============================================================ Preparing Reference ESDs . . . ============================================================ CAB->ESD: amd64fre_Client_en-us_lp DIR->ESD: Microsoft-Windows-RegulatedPackages-WOW64-Package DIR->ESD: Microsoft-Windows-RegulatedPackages-Package DIR->ESD: Microsoft-Windows-QuickAssist-Package DIR->ESD: Microsoft-Windows-MediaPlayer-Package DIR->ESD: Microsoft-Windows-LanguageFeatures-TextToSpeech-en-us-Package DIR->ESD: Microsoft-Windows-LanguageFeatures-Speech-en-us-Package DIR->ESD: Microsoft-Windows-LanguageFeatures-OCR-en-us-Package DIR->ESD: Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package DIR->ESD: Microsoft-Windows-LanguageFeatures-Basic-en-us-Package DIR->ESD: Microsoft-Windows-InternetExplorer-Optional-Package DIR->ESD: Microsoft-Windows-Holographic-Desktop-Merged-WOW64-Package DIR->ESD: Microsoft-Windows-Holographic-Desktop-Merged-Package DIR->ESD: Microsoft-Windows-Holographic-Desktop-Analog-Package DIR->ESD: Microsoft-Windows-Foundation-Package DIR->ESD: Microsoft-Windows-EditionSpecific-Professional-Package DIR->ESD: Microsoft-Windows-EditionPack-Professional-WOW64-Package DIR->ESD: Microsoft-Windows-EditionPack-Professional-Package DIR->ESD: Microsoft-Windows-ContactSupport-Package DIR->ESD: Microsoft-Windows-Client-Features-WOW64-Package DIR->ESD: Microsoft-Windows-Client-Features-Package DIR->ESD: Microsoft.ModernApps.Client.professional DIR->ESD: Microsoft.ModernApps.Client.All ============================================================ Creating Setup Media Layout . . . ============================================================ ============================================================ Creating boot.wim . . . ============================================================ Using LZX compression with 2 threads Archiving file data: 870 MiB of 870 MiB (100%) done ============================================================ Creating install.wim . . . ============================================================ Using LZX compression with 2 threads Archiving file data: 7198 MiB of 7198 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 46 directories) Scanning source tree complete (1679 files in 91 directories) Computing directory information complete Image file is 4121001984 bytes (before optimization) Writing 1679 files in 91 directories to 16179.1000.170414-1642.RS_PRERELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO 100% complete Storage optimization saved 27 files, 245760 bytes (0% of image) After optimization, image file is 4124413952 bytes Space saved because of embedding, sparseness or optimization = 245760 Done. Press any key to exit. C:\UUPtoISO>
Has anybody had a problem with Windows Spotlight on the lock disappearing. It's only a bland blue (this started just before the update to build 16179. I've replaced it with a nice picture of Jupiter but I'd rather have a spotlight image
Had to revert to 15063, PowerPoint 2016 does not like any post 15063 build (see my thread: PowerPoint 2016 - All presentations blank - - Windows 10 Forums).
Functioning Office desktop apps is a deal breaker for me, cannot even think of using a build which makes them not working. At least for now it's only virtual machines for me to test Insider builds.
It would be interesting to find out what makes some seemingly similar systems react differently to some builds. I can be reasonably sure only for one instance that happened to me, a reaction to a GPU driver.