Missing Start Icon & other Critical Issues - the SOLUTION for OEM PCs

JimWynne, a Microsoft Insider pointed out to me that as my PC is OEM*** they (HP in my case) should resolve my problem - Windows Updates screwed up my new Win10 PC.

I contacted HP via their new & improved HP Support Assistant on my desktop and they resolved my problem. Below are the steps that they carried out when they took over remote control of my PC.

Lesson to be learnt? 1. Don't assume that the average customer knows that the OEM have to resolve such problems under the terms of their OEM agreement. It's taken nearly three months for someone to point this out to me. 2. Don't assume that the same average customer even knows what OEM means so, with your permission, I'll post info on that in my follow-up post. Meanwhile I'll let you experts pore over HP's solution to see if it can be used or amended to be used for others here with this problem - PS I didn't need to take Step 3.

Step 1:
Right click on the START button and select COMMAND PROMPT (RUN AS ADMINSTRATOR)
Type dism /online /cleanup-image /restorehealth
Restart the PC after it completes 100%(This would take some time please wait)
Reboot Pc

Step 2:
Press Windows Key + R on your keyboard.
Key in PowerShell and hit Enter.
Right click on the PowerShell icon on the taskbar and select Run as Administrator.

Now paste the following command in the Administrator: Windows PowerShell window and press Enter key:
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}

Wait for PowerShell to execute and complete the command. Ignore the few errors (in red color) that may pop up.
When it finishes reboot

Step 3:create a new local user account
Please open the below link
Create a local user account in Windows 10 - Windows Help -

I would describe an OEM PC as what many (most?) ordinary customers have - usually bought 'off the shelf/ready to go', with software such as Windows, browsers, anti-virus etc already pre-installed by the manufacturer for you.

To check if your PC is an OEM, go to Settings*** > System > About. In Product ID there should be three groups of five numbers followed by a group of five letters. If your PC is OEM, that'll appear in the last group. If it's OEM you should contact the manufacturer of your PC (eg HP) and they have to help you.

(If it's not OEM, sorry!)

*** If you have no Start Menu there are other ways to get to Settings. Win+i may or may not work. Or you can right-click a space on the bottom task bar > Properties > Customise then click on the back arrow Top Left and you're at Settings.

I've also seen a Settings icon at the top of a screen but I can't find it again! Anyone know where it is?

Hi, just curious- the Powershell command has typically broken a number of universal apps since build 10586 came out.

Could you confirm you don't get any listed with '@' before them in the Start Menu? I've not seen a hint MS has fixed this so far. Thanks!

dalchina said:

Hi, just curious- the Powershell command has typically broken a number of universal apps since build 10586 came out.

Could you confirm you don't get any listed with '@' before them in the Start Menu? I've not seen a hint MS has fixed this so far. Thanks!

I haven't found any Apps beginning with @, dalchina. It was HP that did all the work.
BTW My version is now 10586.164

To DENCAL

"Any reader on this forum could have easily have rectified this problem with a simple download of an ISO."
Lots of 'ordinary' users come here for help and I see no evidence whatsoever that "Any reader on this forum could have easily have rectified this problem with a simple download of an ISO." Just read some of the many other threads posted here. Anyway ,I doubt if many 'ordinary users' would even know what an ISO is. Or are you suggesting that this Forum is only for Teccies?

"What has this got to do with an OEM?" Have you actually read my posts? I wrote "a Microsoft Insider pointed out to me that as my PC is OEM they (HP in my case) should resolve my problem." That couldn't be any clearer, could it? And the Title should give you a clue.

"Doubtful advice, which could do harm to another computer." Clearly you have great technical knowledge and expertise but how can you possibly say that you are right and HP are wrong? Especially when you haven't read what I written. Please tell me why you say it could do harm to another computer and I'll take it up with HP. Oh yes - it probably would harm a Win8 Lenovo OEM.

Sorry but I'm furious. You need to learn some manners, with the greatest of respect.

DeaconFrost said:

That isn't going to be very helpful to anyone, especially when you haven't even used the quote option. I'm not trying to start the argument, just making an observation that firing at the people who respond to you won't get anyone anywhere.

Now, back to the topic, no one of any skill level, should be surprised that an OEM system has issues out of the box with the original install. It has always been the case, going back 20 years or so, that the first step in using an OEM system is to perform clean install. In the business world, it's done the moment the PC is unboxed, using an image of some kind. At home, images probably aren't being used, but it still is the best thing to do. No, the ordinary user may not feel comfortable doing so on their own, but the readers on a tech forum aren't the typical users. Even ones here who say they aren't tech-savvy are still well ahead of those who aren't here looking for help.

I have never, in all of my years, turned to an OEM for a software issue on a non-server. Too many variables, and most often their solution will be to reload using the recovery option. Most of the time, going to an OEM for software support is a complete waste of time.

I apologise for my earlier rant and for messing up the 'Quote' but I came here with a solution for those with an OEM PC. You say you have never done that but I've had three months of hell with a new Win10 PC that became 'unfit for purpose' because of a Windows Update. A Microsoft Insider on that forum told me that anyone with a problem on an OEM PC should go to the OEM manufacturer to get it fixed.

Let's say someone else with the problem came here tomorrow and read that a Microsoft Insider was saying go to the OEM and you say the opposite how could he/she decide? It's so confusing for anyone needing help - and it ought not to be.

And then for the other expert to say what he said, (raining on my parade is the polite phrase, I think) when it's clear he/she hadn't even read the title, let alone the content, is too much imho. Such a negative reply, with no evidence to back it up.

Seeing the response my feeble attempt to help has had, I won't bother again. I'll leave it to the experts. Nor will I come here for help if tenforums is only for teccies. All I WILL say is that the Insider's advice worked for me and I now have a PC that works. Every other workaround here and in the MS forum has failed after a while , if at all. Look at the dozens of users still coming here for help!

PS As an expert you will obviously be comfortable with a 'clean install' but with respect how many typical users will have heard of a clean install, that it's the first thing you should do when you buy a PC off the shelf. Not many I guess.