In contrast with what we saw few pages back, this post is pure gold! Relax kid, your English is good enough.
Along the way to getting a stable 10074 system myself, I noticed that immediately following a refresh reinstall I did from a 10074 disk media boot, my start menu was simply not working. This was before I installed KB3062095, actually. What I did was to simply mount the 10074 iso inside a Win10 boot and ran setup from there, again. (This gives you the equivalent of an old XP "repair reinstall".) It's better than a "refresh" because unlike the refresh option in Win10 it allows you to keep *all* of your installed programs--not just a few of them. It took about an hour for the repair reinstall, and after that, no problems with the start menu in 10074 (at least that a simple log-out/in won't instantly correct.) Installing KB3062095 after that did not negatively affect my start menu at all, and completely solved all of my other problems relating to the AMD 15.4b Catalysts stopping, and then restarting--frequently in some games. All problems I'd had with the start menu deploying in a full-screen game also vanished. Now, I'm running the WDDM 2.0 drivers with the 2015.0401.236.2774 CCC without any major issues. 10074 is very much a beta build......and a work in progress. It's still very rough around the edges as I've discovered. But, try the "repair reinstall"--it worked for me, and it surely can't hurt. Mistakes that may have been made in your initial 10074 install because of bugs here and there manifesting can often be corrected by a repair reinstall operation.
Great thing about the way Win10 is shaping up is that we can configure it like we want to use it--and are spared the Apple philosophy of "Our way or the highway"... Just because Microsoft puts an icon or two in there doesn't mean anyone is forced to use the store or even to keep their store icons visible on the desktop. Use of tiles everywhere is completely optional. Win10 is shaping up far better than Win8/8.1 turned out. xBox live junk is controlled by services--which I have disabled. I even like the start menu with this build. I'm very encouraged by what I've seen so far.
Since when did Microsoft stop supporting regular Microsoft Accounts for the Enterprise version? I was told to login with a school or work account, and they did not seem to be able to accept my Office 365 Business / Hosted Exchange account because of some unknown error so I was forced to create a local account... And directly after installation it seems like none of the start-menu icons are working? Cortana / search is not doing anything. I can't access Windows Update through Run -- Control Panel and the Settings.app is not launching as I have to access it through the start-menu and none of the shortcuts in the start-menu seems to be working.. EDIT: Now I'm able to click icons in the start-menu and cortana / search is starting to work but I'm getting a "runtimebroker.exe" "-Invalid value for registry" for about anything I try to launch... I guess it might have something to do with the fact that I'm using a local account instead of a Microsoft one but how am I supposed to logon to my Microsoft Account when they require a school or work account during the installation? ..
Nevermind.. A reboot of both the installation and Hyper-V seems to have solved most of my problems and even though Microsoft did not accept regular Microsoft Accounts during the installation you are still able to link your local account to a regular account from within Windows. Why they won't let you do it during the install process and force you to create a local one is beyond me.