Windows 10: Win10 sysyprep and start menu

Does anyone know if Microsoft has acknowledged the fact that sysprep breaks the start menu, cortana and search?

:)

 

win10 cannot open start menu and cortana menu, powershell went wrong.

Hello,



Thank you for posting your query in Microsoft Community.



You may download the Windows 10 ISO and create a Media Creation tool and then perform Startup Repair.



Refer to the following link:

Download Windows 10

(Refer to the section "Installing Windows 10 using the media creation tool
" in the above article for creating the tool).



Once you have the installation media, follow the steps:

• Start your computer from the installation media. Insert the disk or USB stick and restart your computer. If you see a message asking you to “Press any key to boot from DVD,” do so. If you don’t see the message, you might need to
  change the boot order in your computer's BIOS settings so that it first starts from the disk or USB. When you see the 'Install Windows' page, tap or click 'Repair your computer' link to start the Windows Recovery Environment.
• In the Windows Recovery Environment, on the Choose an option screen, click 'Troubleshoot'.
• Click, ‘Advanced Options’ and then click on 'Startup Settings' and select ‘Restart’.
• After this complete the repair and see if you are able to boot in to your computer.

Refer the link for reference:

Change startup settings in Windows 10

http://windows.microsoft.com/en-us/windows-10/change-startup-settings-in-windows-10#v1h=tab02



I hope this helps you. If you have any further query in future, feel free to contact us. We will be happy to help you.



Thank you.

 

win10 cannot open start menu and cortana menu, powershell went wrong.

when i try to open powershell ,it says





In case of you guys cannot read this,let me show
my pool English.

Em.. it says

windows powershell was stopped, with the exception:

"System.Management.Automation.Runspaces.InitialSessionState" type init value cause an exception.

My system totally got mess up, cant open picture and nothing happened when i right click the tasks on the taskbar.

And then i thought it maybe something goes wrong with the powershell, and i got some advices,such as:

run

dism/online /cleanup-image /scanhealth

dism/online /cleanup-image /restorehealth

But it went wrong again---with Error:1392 File or directory damaged and cant not read.

Help me,plz,i dont wanna die...

 

The only scenario I have seen that the Sysprep does that is if you sysprep an existing Windows installation wich contains active user accounts. When sysprepped as it should be done, in Audit Mode prior to creating any user accounts, sysprep works as it should and does not cause Start and Search issues.

A workaround to be able to sysprep an existing Windows installation is to activate the built-in admin account and sign in to it signing out from all existing accounts, deactivate all user accounts except the built-in admin, then sysprep. After the sysprep in OOBE create a dummy admin account, sign in, activate the deactivated user accounts and you are ready to go.

The above workaround can be seen in action in this video about using Sysprep to relocate the Users folder on an existing Windows installation:

[youtube]OGNqR8lylzk[/youtube]

Video from the thread Windows 10 instructional videos by Ten Forums members - Windows 10 Forums.

 

Kari,

That is the exact scenario I am in. We create several users, make config changes and sysprep.

When it comes out of sysprep, the users would be all setup and we could install some software and be done (if additional software was needed).

Overall, we want to advoid having to activate and deactivate users and so on. This would require someone who knows what they are doing to go in and make these changes.

When you are in a environment where you need to get the computer's to end users (sometimes shipped right after imaging) they need to be ready to go (turn on, log into one of the several accounts and your good to go). This worked fine in xp-win8.1


Just hoping Windows fixes this.

 

In that case you should do it all in Audit Mode prior to creating any users, and create users in the answer file. After the sysprep simply capture the image for deployment. In this way all user accounts will work without any whatsoever issues with Start and Search.