I used the Decombobulator tool to troubleshoot the error and it spit out something to the tune of "We don't know what that DCOM error is"! LoL.
In the meantime, thanks for checking. Yours didn't look like my problem, so that is why I was double-checking.
In the meantime, I disabled port 135 using the tool until they figure out the RPC problem.
Last edited by EyeInTheSky; 08 Apr 2018 at 19:49. Reason: Correction
Yep, I've seen that DCOM error with no APPID on Win10 Home 1803 startup.DCOM error - Event ID 10016 pertaining to the Windows.SecurityCenter.WscDataProtection
Oh, i see i could simple click on the Upgrade Assistant, since i wasn't planning on doing a clean install, but rather an upgrade from what i am running now...then, no need to even create an iso file...just click on "use upgrade assistant".
I assume that's simply going to trigger the download to windows updater...Should that work ok???
Microsoft broke "disable web search" in Windows 10 version 1803 (on purpose)
https://www.ghacks.net/2018/04/07/mi...-version-1803/Windows 10 users and administrators who plan to upgrade devices running the operating system to Windows 10 version 1803, the Spring Creators Update, need to be aware that certain policies are broken currently in the new version of Windows 10.
In particular, the policy "Do not allow web search" has no effect when enabled on the device. The initial version of Windows 10 combined local search functionality with web search functionality when it came out.
One person in comments section says that policies still work in Enterprise and Education editions.
@Craig "no need to even create an iso file...just click on "use upgrade assistant"."
That option is usually the last one to get posted. As I said, I prefer to use the MCT, generate an ISO, control the install process and have a copy that I can keep and use like the Windows OS DVD that mfrs used to give you with a new computer, in what seems like ancient times now.
Yes, it should work - but experience on these forums has shown that upgrading using the ISO or USB can be the more reliable method. Plus you get to keep the install media should you need to use it again, on another machine, for repair purposes later or to re-run the upgrade should it have problems first time around. If you need to re-run the upgrade assistant you may well end up having to download everything again.
Hi All,
I thought I'd be adventurous a few day's ago and try and install the spring creators update on my desktop computer that's running Windows 10 Pro..Version 1709..Build 16299.334 . That was a big mistake, at least on my machine..the installation seemed to be going pretty smoothly, but when the system needed to restart / reboot it got stuck, and all I heard was one long 'beep' . I had to insert a windows installation disc to get past that and just opted to go back to the previous version that I had been running ( Version 1709..Build 16299.334 ). At this point in time I'll be very concerned when the spring creators update will be offered via the 'normal' windows update mechanism . Has this happened to anyone else ? I never received any error message, my system just locked up, I'm not running any third party ant-virus software.
David
I have three Release Preview Pro copies running without issues, (One system, the oldest, that has some pre-existing hardware issues took a few tries but that was expected).
I have re-enabled SMB1 and all is now OK on network side
I think that people will have issues in some cases and I would advise anyone who does to wait a week or so and let the usual release time rush to clear
Quote
