It's also not really an issue for laptops. Simple really, don't plug in a LAN cable and skip the wifi setup if Windows even installed a driver for it. "Problem" solved!
Hehe well I when I arrive at this stage my first and only answer is NO for everything, of course disconnected from WI-FI and Ethernet and continuous Act start Windows by running by calling Regedit and disabling Enable LUA and in DWORD = 0, I also take advantage to disable Hyperboot, I fix the bug of the drives in duplicate if I am with only the installation Pendrive in Explorer appear 2 ??? And finally I create a key in HKLM\Software\Windows\CurrentVersion\Explorer called Serialize with the Dword named StartupDelayInMSec with the value = 0 Restart the machine and run to gpedit.msc for the proper "instructions on how Windows should work but it is not yet finished also you need to change several things In Task Scheduler and also in Services.msc restart again in this way it is now possible to start using the system installing drivers etc...
where can I download this file? --- Windows 10 (business editions), version 1903 (updated Sept 2019) (x64) - DVD (Turkish) [ID: 85762] --- 353343ad67d58d77fe88fec8624f7c529bdad45d *tr_windows_10_business_editions_version_1903_updated_sept_2019_x64_dvd_5d2dc467.iso
@xrasimx start reading/learning about SmartVersion | Tools + Scripts Code: en_windows_10_consumer_editions_version_1903_updated_sept_2019_x64_dvd_ef2f7737.iso [tr-tr]_tr_windows_10_consumer_editions_version_1903_updated_sept_2019_x64_dvd_b699a844.svf [tr-tr]_tr_windows_10_business_editions_version_1903_updated_sept_2019_x64_dvd_5d2dc467.svf ps.
Hello everyone, I have clean installed 18363.356 build. Windows update, under settings, is showing "your device is missing important security and quality fixes". There is only one optional CU (kb4524147). This critical warning in red text didn't appear in 18262.xxx build, irrespective of the updates required. Does anyone too have this situation? Or something is wrong with the installation?
OK, so we know about the OOBE not having Offline Account. That sucks but hey, Microsoft. I just had it go to the next level. I powered on my work PC this morning (An old install, I've been lazy, it's still in 18362.356), and during *login* it threw me to the same OOBE screen wanting me to use a Microsoft account. Oy veh, looks like I get to warn the team for what to do when users run into this.
It's a good possibility that msft will announce the 1909 EP going public at tomorrows patch releases but if they try to keep up the scam of a new build this year, they normally would do it at an MSFT event.
You probably didn't select 18363.388 but 18362.388, i showed that the UUP dump conversion shows 18363 in it's iso filename.: https://forums.mydigitallife.net/th...10-uups-with-ease.75052/page-150#post-1552407 And here is the simple story about the fake/mock 1909/18363 build: https://forums.mydigitallife.net/th...pc-19h1-2-release.79259/page-282#post-1551877 ps, installing home or home sl in a company environment?
I'm not on 18363. This is my work PC, which is production, so I don't put Insider on it. It's a plain-jane consumer level install. It's several months old, so for it to just randomly be like NO NO YOU ACTUALLY WANT AN MS ACCOUNT NOW caught me off guard, and will catch other employees off guard.
You are running Home or Home SL on company systems? And if they are already using it, how would it catch them off guard? The admin sets the devices up for the employees, i hope?
This is Windows 10 Pro. Which just makes it more weird. Like I said, a several months old, matured, used five days a week for several months, not new, not new, NOT NEW, machine, used daily, for months (get it yet?) suddenly prompted me on login to use a Microsoft account.
It doesn't concern Home N, Pro, Edu, Edu N, Profws, pro n fws. enterprise, enterprise n, ltsc or ltsc n. Except Home N, all offer the "setup for an organisation" and next local domain join option is available, Home N has the option "use a local account" available. And it can't happen on an already installed system, only when new installing. The only thing that can cause the switch from a running local account to an online account is when somebody signed in at a MSFT app and not using the option to only sign in at that specific app and not for the whole windows.
Hello everyone, clean installed 18363.356 (19h2) (CU to 18363.388.) Hard disk keep whirring for a lot of time. CPU usage, disk usage are minimal (nothing abnormal). Does anyone too have this issue? However, hard disk whirring was also the case with 18362.356 (19h1), but it was fine after update to 18362.388.
If a user is on 18362.388 and wants to go to 18363.388 they should just install -KB4517245-x64.cab via dism.exe as this appears to be a feature update will this be on windows update also will there be a new 1909 18363 ISO Thanks
Yes, that's how it's done since 18362.32x+ and yes it could be possible that we get the new refresh iso with the mock 18363 build. There already is an official 18363.327 IP ISO and a 18363.356 ESD prerelease. And by UUP you can create any available build iso too.