Creators Update Fail

[greycloud]

Completed update; I had some concerns but haven't even gotten that far.
After update......no Start menu! LOL. Click on the window icon and nothing. Re-booted a few times; nothing. Can't get the Start menu no matter what I do. Anyone else?
Nice work, Microsoft.

 

[BonzaiDuck]

Hope you've been making scheduled backups of your boot disk.

Macrium Reflect has literally saved my ass on this through my "Build 1703" difficulties.

Did you update from within Windows Update of Build 1607? or did you download the ISO or use the direct MS link to install it?

What you describe makes my own experience -- extensively documented in other current threads -- a success. I finally got to the point where Windows Update for Build 1607 was again working as expected. I'm just going to wait a bit before even attempting to install Creators Update again.

 

[PingSpike]

Completed update; I had some concerns but haven't even gotten that far.
After update......no Start menu! LOL. Click on the window icon and nothing. Re-booted a few times; nothing. Can't get the Start menu no matter what I do. Anyone else?
Nice work, Microsoft.

Its the Creators Update. Microsoft was sick of all the complaining about the start menu so you have to create your own start menu now.

 

[RLGL]

Install problems MS has free support

 

[Ketchup]

Haven't seen that on any of my installs. Does the right-click menu on the start button work?

 

[RLGL]

Google is your friend

 

[Puffnstuff]

Completed update; I had some concerns but haven't even gotten that far.
After update......no Start menu! LOL. Click on the window icon and nothing. Re-booted a few times; nothing. Can't get the Start menu no matter what I do. Anyone else?
Nice work, Microsoft.

You might try a DISM repair but read up on it first over at the 10 forums.

 

[RLGL]

Does the right-click menu on the start button work?

Yes it does.
All the issues I have had with the preview program have been due to hardware. You may be better served if you download the ISO and start fresh.

 

[greycloud]

Did you update from within Windows Update of Build 1607? or did you download the ISO or use the direct MS link to install it?

From within the OS (1607) prompts.

Its the Creators Update. Microsoft was sick of all the complaining about the start menu so you have to create your own start menu now.

LOL.

Does the right-click menu on the start button work?

After the update, no, mine did not work. Right or left click on the Start Menu window icon produced only the momentary spinning "background process" indicator for about two seconds, then nothing.

You might try a DISM repair but read up on it first over at the 10 forums.

Thanks....I will check it out. I'm in no hurry so I'll let the update settle in for a bit. I should know better by now not to immediately jump on large MS upgrades when they are first released.

Thanks all for the replies.

 

[Elixer]

Clean install the Creator's update, they have released ISOs.

 

[Makaveli]

^^ I would try this.

i've installed it on my main desktop and a laptop no issues.

 

[BonzaiDuck]

^^ I would try this.

i've installed it on my main desktop and a laptop no issues.

I took a different approach. The original installation of Win 10 and the Anniversary build leaves Win Event Log errors reported on other forums specific to Windows, and I went to a great deal of trouble researching them and cleaning them up. They have not reappeared with the Build 1703 installed through Windows Updates. If I had any troubles installing through the direct link to Build 1703, they weren't due to the difference in installation methods.

Somehow, I think these difficulties with annual new builds of Win 10 are going to break the demand that mainstreamers once had for desktop systems. You could wonder how the OEM handle this with their "extended support." I wouldn't have the slightest idea. I haven't bought an OEM system since 1994.

 

[greycloud]

Clean install the Creator's update, they have released ISOs.

Yep, I think that's the way to go.
Going to back up some settings and export some files, then it's clean slate time.

 

[BonzaiDuck]

Yep, I think that's the way to go.
Going to back up some settings and export some files, then it's clean slate time.

I would most likely still tell someone else to clean-install.

For myself, a relentless obsession for tuning my Win 10 installation and making a variety of software work together seemed worth the trouble.

I think it can be a lot of trouble. But what one has may also have been a lot of painstaking trouble to create over many months.

Today, I feel victorious. Also, the new Build 1703 does something I hadn't noticed before in Win 10. Frankly, I thought the default size of a Hiberfil.sys would be 16GB for 16GB of RAM. The preferred tweak to this, worrying too much about SSD writes, is to set it at 50% which is the minimum. But Win 10 gives you a "Full" hyberfil.sys of 40% of RAM, with a "reduced" setting of only 20%. The former supports hibernate, sleep and fast-startup; the latter only supports fast-startup.

So . . . I'm still gloating after this . . . I've got dual-boot Win7/Win10. I've identified an anomaly in Win 10 startup related to non-standard, non-NTFS volumes on the boot-system disk, but it so far seems benign. [To get rid of it, I only need to abjure using PrimoCache caching of my HDD to my 960 Pro caching volume. There seems to be a small but growing knot of people over at the Romex Forums who have a common boot-time message about "Diagnosing, scanning, repairing" a GUID.

If the system boots, there aren't any red-bang events in the logs related to start-time and storage, and the caching works flawlessly, well -- benign seems to be the right word.

A few more things to do with this system, and I think I'll feel really good. Very good indeed.
==== AN UPDATE TO THIS POST ========

The last anomaly I could discover has disappeared. This was the symptom where even in properly working dual-boot, Win 10 throws a "Diagnosing, scanning, repairing {GUID} volume . . ." before reaching the pre-logon display. Repairing the Samsung driver through Control-Panel->Programs and Features, then uninstalling/reinstalling the Magician 5.0 software -- seemed to resolve it all. This may work for some people with some hardware and some OS installs. But easy enough to do as a possible fix.

 

[sm625]

You think you got it bad, try this:

I got no internet after doing the update! WTF microsoft. How is this company still in business? They just set a new low.

I have 3 network adapters and none of them will connect. Kernel CPU usage is maxed out for 20 minutes. OS is completely destroyed.

 

[Puffnstuff]

You think you got it bad, try this:

I got no internet after doing the update! WTF microsoft. How is this company still in business? They just set a new low.

I have 3 network adapters and none of them will connect. Kernel CPU usage is maxed out for 20 minutes. OS is completely destroyed.

You need the new CU which addresses loss of connectivity.

 

[sm625]

You need the new CU which addresses loss of connectivity.

So I upgrade to the CU, which breaks my network and destroys my kernel, and your solution is... I need the CU? Ok. I'll take that into consideration...

 

[Puffnstuff]

You might try reading up on what the new CU addresses before you comment on it.

 

[RLGL]

There are some issues with Broadcom adapter drivers