@all: i almost chekced every method available(safemode, powershell1,2, services, eyplorer.exe, UAC rights...), except of the "health point image" thing, that's to come.
But i thought it might be worth mentioning that the problem occurs on my account wich is a domain user !
The standard windows account user works flawlessly. So the "base system" shouldn't be the source of the problem then, right ? What differs this two usertypes, maybe a worthfull question to think of.
Thanks for the thread, best regards, me (-:
i found another method, which did not work for me, but it may be worth a try for smbdy of you too:
taskbar, start menu, cortana not working in Windows 10 (FIX)
Somebody mad a little .bat file with all the steps integrated. For a strange reason i dont have the :
location anymore, and i cant find the install.wim on the USB stick made with "Media Creation Tool", therefore this is not working yet:Code:C:\$Windows.~WS\Sources\Windows\sources
So, let me try to summarize what already has been tried without success:Code:DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess
1. Restart the service
2. Restart Explorer.exe
3. Boot in safemode
4. Powershell script 1
5. Powershell script 2
6. Change security leve on UAC
7. DOCB's registry key check
8. The 10Services.bat from kickiteasy
Is there some way to file a bugreport or so in the microsoft world ?
ps: is bthere a way we can join this 2 discussions, since theyre about the same topic ?
Windows 10 Start Menu, metro apps, and taskbar icons not working - Windows 10 Forums
Hi all, just to let you know:
finally my "solution" was to create a new user. That worked for me. best regards, me (-:
Try creating Win10 Install media and use that to perform a Refresh
Windows 10 ISO Download (TenForums.com)
Refresh Windows 10 (TenForums.com)
Many issues seem to be related to .NET 3.5 migration, you might try turning off .NET 3.5 in
Control Panel > Programs and Features >Turn Windows features on or off
De-select .NET 3.5
Then Refresh Win10
If necessary, you can turn .NET 3.5 back on after the refresh, but the current .NET 4.5 (.6?) should provide the necessary bindings.