Discussion in 'Operating Systems' started by Extraordinary, Mar 28, 2019.
Cant seem to install the update from the ISO keeps coming up something about a driver or service.
let's see how many guinea pigs die this time before testing on humans ^_^
Anyone have en_windows_10_business_editions_version_1903_x64_dvd_37200948.iso or en_windows_10_consumer_editions_version_1903_x64_dvd_b980e68c.iso uploaded for non-MSDN subs?
Is that what you're looking for?
does the consumer version meant to be home and pro and the business meant to be enterprise ?
Thanks a lot mate, that was exactly what I was looking for.
Bloody hell, no MCT till late May means that I'll have to download a dubious ISO from some file sharing service. It's like MS is forcing us all into the hands of hackers and cybercriminals.
And no one is forcing you to update earlier. You can wait a month if you want, the reason why they put MCT on hold is they want to incorporate May CU into the final build.
Also there is nothing wrong with WZor and https://rg-adguard.net/ links or file sharing service they are using. All files are straight from MS and MD5 Hash identical to files on MS servers.
They are no more hackers and cyber-criminals than people who post clean driver repacks here.
Sure. But I have time now, may not be the case in a month.
Judging from what CUs did to 1809 I see zero reasons to be waiting on this.
Well, yeah, that's one option I guess.
If you have time now then just create a bootable USB with Rufus and install the current build. I couldn't just update on top of existing 1809 due to some driver incompatibility. Had to go for a clean install and everything went fine. That's like 2-3 hours of backing up files, downloading ISOs and drivers, writing to USB, installing, moving files back to system volume and messing with all sorts of settings. Boring, but it was worth it.
I never update. Doesn't worth it, too many issues.
Must be you then. I have had zero issues updating since initial release. In fact, I updated from 8.1 to 10.
Yeah, it's definitely me. This is why there are issues with permissions and drivers even when updating a clean installation of a previous Windows release. Couldn't be just, you know, crappy MS updating procedure.
You must have high chance of luck... I've tried every major build and find issues every time, it's getting to the point now where I'm just sick of it and wish Microsoft would just put out a good version of Windows 10.
Or it's because I avoid the Start Menu and use Start10
I wish the issues were only related to the Start Menu....
I can vouch for Wzor, even though hes a crazy russian dude, his iso's are never compromised and his images are always a direct conversion of the ESD download.
Also, i didn't have the 1809 file deletion issue, but there were definitely functionality problems on launch that Chastity seems to have entirely forgotten.
Default app changes crashing the settings ui
trying to load the file type manager doing the same
oh, if you use a virtual drive, don't update to 1903, the simulated sata controller in use by Alcohol and Daemontools these days is experiencing a "controller error" and the simulated ahci device code 10's - this is related to the Retpoline support thats default in 1903, i could even repro it under 1809 with retpoline manually enabled, so waiting on these tools to update.
I wanted to update my Surface Pro 4 but aparrently my hardware isn't compatible yet. A bit of a shame as my Surface Pro 4 has been running poorly ever since the update to 1709 but oh well.
No, I just didn't have the pleasure of experiencing. I also remember the number of people affected was a vocal minority. But it did happen and it was addressed.
I updated. Tested, and X-FI Titanium HD support is COMPLETELY broken. Until Creative releases a new drover, 1903 is unusable for me