Thanks. I've been hitting that goddamn "check for updates" button for last 4 days. You haven't received KB4135051(17134.5) yet, right? EDIT: Downloaded the iso-svf combo as soon as it got released. Just wanted to upgrade using WU this time around.
It works on Windows 7 X64. I tested only option 1-Create ISO with install.wim. My mistake was i did not downloaded all the files from the pack with Download using aria2. Thank you for a great help.
yep that's right I haven't received that update yet through windows update -as it is still listed as via the insider program so as not received a general release But I have it from this site as a cab & I know how to install it as I got the info from TECHNOMAN but decided to wait With the help from TECHNOMAN & others on this site I had a update for build 17133.5 that took that to 17133.73 & with their help I learn how to do it But here The link for info on -KB4135051 https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-290#post-1431341 just make sure you download correct version x64 or x86 or arm64
sometimes i communicate poorly, my joke wasn't tied to ltsb/ltsc. my joke was separate about "windows 10 s" or s-mode, which i think is bad as ...well...something. regards to ltsb/ltsc, i actually use it in one of my machines. that machine rarely boots to windows so i ended up to ltsb and in this scenario all the unnecessary garbage is out. still i don't recommend ltsb/ltsc for most users. my view is that enterprise is better when removing unnecessary parts.
You aren't the only one having inter-machine network issues. On top of the Win10 > Win10 stuff I tried integrating a new Raspberry Pi W print server into my mix and had all sorts of headaches that turn out to probably be no fault of the Pi. I found that by creating a \\machinename shortcut to the 17134 Win10 boxes and Pi spooler I could get to them even if they were not visible in Network\machinename.
Do people here understand that many people BUY software and not easily switch? Or that saying, install this or use that is not really helping with the problem?
i can confirm the 32bit 1803 working with x58...but for 64bit stuck at logo... i am trying to fix the 64 bit installer...it is installing now...i will keep posted...wish me luck 64 bit 1803 on x58 motherboard
The built in depender is slower when scanning on the fly. For example when opening a folder that has a lot of files. All the tumbnails for the files will show blank icons longer when opening folders then when using avira. With avira the file icons loads instantly
Installer? Just deploy windows with gimagex/imagex, or dism (or the monkey proof WinntSetup by JFX), use the installer if you're installing win3.11 In 2018 the setup.exe has just one function, in place upgrades.
I would unnistall and install again, downloading the most updated offline installer, disabling windows defender before installation.
Afaik and it has always been so, installing a 3rd party AV will disable/reduce the working of the native windows Defender by default.
I have the exact same problem with an Asus Rampage III Extreme Motherboard too with Intel i7-960 cpu so an second model here 0xC1900101-0x20017 The installation failed in the SAFE_OS phase with an error during BOOT operation UPDATE After some research, most older ASUS board+Intel with VT-d enabled won't update/even boot (like mine). If you use virtualization, BE WARNED. I disabled VT-d in bios and upgrade and boots went fine!