[Forum FAQ]Start Menu Scroll Issue in Windows 10 Technical Preview Build 9926

Scenario:
When upgrading to Window 10 Technical Preview Build 9926 from Windows 10 Technical Preview Build 9879, you may notice that on the start menu, when you move mouse to the right side, it won’t scroll until you click it.
Solution:
This is because the value of the key DWORD
MouseWheelRouting which is under
HKEY_CURRENT_USER\Control Panel\Desktop values changed to 0 after upgrade.
Note:
Before you make changes to a registry key or subkey, we recommend that you export, or make a backup copy, of the key or subkey.
Press Windows logo key +R to open Run, type
regedit, and then press Enter to open Registry Editor.
Navigate to the key HKEY_CURRENT_USER\Control Panel\Desktop.
On the right side, change the value of the DWORD MouseWheelRouting
to non-0 and non-1, for example 2, 3, which is set to 1 by default.
Exit Registry Editor. 
Sign out and sign back.
Applies to:
Windows 10 Technical Preview Build 9926 upgrade version.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

same issue in build 10049.
It would help to be more specific in the symptom description.  E.g. using Narrator may help.  (Win-Enter).  Does it say what you are "seeing" (or should be seeing)?
FWIW I think it is relatively easy to reproduce symptoms which are related to this thread's description using Narrator (Start Screen without Search bar, Search bar without Taskbar, or Search bar with Taskbar but without Start Menu
when the only time that the Search bar should appear is when the Start Menu is there, for example) so that could also help specify what your real symptom is.  BTW there are horrendous delays when using Narrator.
Robert Aldwinckle

Similar Messages

  • Is Windows Technical Preview Build 9926 Last Build before Release (PC) ??

    As @ Mar 14 2015 - My WIN10 build Installations (9926) no longer have "Preview Builds" option,
    in Update & Recovery Menu (PC Settings)
    Build 10036 announced by rumour mill...
    Dell Precision 490 Desktop Intel XEON X5365 (Quadcore) x 2 Chipset X5000 321x/3221ESB Southbridge AMD Radeon HD7750 HDD ST3000DM001 3TB HDD ST2000DM001 2TB SSD OCZ Vertex 3 120GB SSD OCZ Vector3 128GB x2 RAID 0 Offline WD10EALX 1TB Barracuda 7200.10 250GB
    USB 3.0 WD MyBook 1230 3TB USB 3.0 WD MyBook 1130 2TB

    Microsoft Community got there first...
    http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/is-windows-technical-preview-build-9926-last-build/bb0bed43-4d64-4e1b-acaa-fee158f034ce
    Thanks Andre da Costa
    Dell Precision 490 Desktop Intel XEON X5365 (Quadcore) x 2 Chipset X5000 321x/3221ESB Southbridge AMD Radeon HD7750 HDD ST3000DM001 3TB HDD ST2000DM001 2TB SSD OCZ Vertex 3 120GB SSD OCZ Vector3 128GB x2 RAID 0 Offline WD10EALX 1TB Barracuda 7200.10 250GB
    USB 3.0 WD MyBook 1230 3TB USB 3.0 WD MyBook 1130 2TB
    We only reply to questions posted in TechNet forums.
    We don't go to MS Community and find out if the same question has been answered or not before we post the replies.
    There is no such thing as who gets "there" first.

  • Problem installing Windows Technical Preview build 9926

    I am not able to install the Technical Preview on my computer. Everything looks fine and in the end it says "applying computer settings" and counts the percents before it reboots again.
    During the boot it says evaluation build 9926. Then it says Restoring the old windows as it was before... I can't get this to work.
    This is the windowsupdate.log file and the last attempt of installing at the end of the file. 21st of march.
    https://onedrive.live.com/redir?resid=EFA0853808EA8416!80492&authkey=!APrJtEAGwfnZydU&ithint=file%2clog

    PH
    Do you know that you can make an ISO to install 10041 and not have to install 9926?
    http://microsoft-news.com/download-windows-10-build-10041-iso-image/
    Wanikiya and Dyami--Team Zigzag

  • Windows Technical Preview Build 9926 update

    Hi,
    I am trying to update my Windows 10 TP installation and it seems that it fails to download.  I am behind a proxy server in the office with no way around it.  Windows Update fails with error 0x80072ee2.  What I have picked up is that I can
    get the update list if I set a proxy server in BITS using "bitsadmin /util /setieproxy localsystem proxy1:port "bypass list".  However bits fails to download the updates returning either Error or Transient_Error.  Can you please assist
    with this issue?
    Regards,
    Riaan
    EDIT: I set proxy settings of each bits download job to PRECONFIG and the updates downloaded and installed.

    Hi,
    Did you set the proxy server via IE? Do you mean that the Windows Update Client ignore the proxy settings? To make Windows Update use the proxy setting, please execute the following command from cmd
    Netsh winhttp import proxy source=ie
    You can refer to this following KB for "how Windows Update finds proxy settings"
    How the Windows Update client determines which proxy server to use to connect to the Windows Update Web site
    http://support.microsoft.com/kb/900935
    Yolanda Zhu
    TechNet Community Support

  • [Forum FAQ] How to show Windows Update in Control Panel in Clean Installation of Windows 10 Technical Preview Build 9926

    Scenario
    If you performed a clean installation of the new Windows 10 Technical Preview Build 9926, you would find Windows Update is only available in
    Settings and is hidden in Control Panel by default. However, Windows Update is still available in Control Panel if it is an upgrade version of Windows 10 Technical Preview Build 9926.
    Solution
    After the comparison of the two different version, the differences is the following registry:
    HKLM\SOFTWARE\Microsoft\WindowsUpdate\UX\IsConvergedUpdateStackEnabled
    In clean installation version:
    In upgrade version:
    The method to make Windows Update show in Control Panel in the clean installation of Windows 10 Technical Preview Build 9926:
    Edit the REG_DWORD value of IsConvergedUpdateStackEnabled from 1 to 0.
    Applies to
    Clean installation of Windows 10 Technical Preview Build 9926
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    We’ve seen a few forum posts talking about changing registry keys to alter the update experience we shipped in Technical Preview build 9926. There are a couple of reasons that we don’t recommend doing things like that.
    First, the default experience is what we’ve tested across not just the Windows 10 team, but across all of Microsoft before we released it to you. That doesn’t mean that you won’t still find bugs, but it’s definitely the code that’s been most thoroughly
    tested. Changing things back to older versions is risky because the combination of those old settings with the rest of Windows 10 is not something that’s been validated or supported, so we can’t predict the side effects. It’s possible that changing registry
    settings related to update could cause a machine to no longer be able to get new updates or Technical Preview builds.
    The other reason to avoid changing the default update experience is that a lot of update-related code is actually being re-written in order to scale across the variety of different device types Windows 10 will support. Since Technical Previews are
    a work-in-progress, some code that may still be in build 9926 won’t actually ship in the final version of Windows 10 that we provide to all our customers, so trying to re-enable that code temporarily won’t provide a way to accurately assess Windows 10’s update
    capabilities.
    We want to hear your feedback! We’re sharing Technical Preview releases early so we can understand exactly how customers are using our software and make sure we are designing our experiences to address those scenarios. The more
    specific the feedback, the more helpful it is for us – saying “I hate the new Windows Update UI” isn’t very useful, but when we see “I need to be able to tell Windows Update to grab updates from WU itself and not from my internal corporate server, so the new
    Windows Update UI is painful for me”, we can actually understand what changes we could make to solve those specific problems. We can’t promise to fix everything that everyone asks for – and sometimes what one customer wants is exactly what another customer
    doesn’t want – but the more you can help us understand why you want something changed, the better we can try to meet those needs.
    Thanks for listening, and we look forward to hearing your responses.
    http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_update/warning-disabling-the-new-windows-update-ui-may/dc846517-eca0-4960-b0ff-1eb7227223f5

  • About the error: "The account is not authorized to login from this station" when you access NAS devices from Windows 10 Technical Preview (build 9926)

    Scenario:
    With the release of Windows 10 Technical Preview (build 9926), some users may encounter an error message of “The account is not authorized to login from this station” when trying to access remote files saved in NAS storage. In
    addition, the following error log may also be found via Event Viewer:
    Rejected an insecure guest logon.
    This event indicates that the server attempted to log the user on as an unauthenticated guest but was denied by the client. Guest logons do not support standard security features such as signing and encryption. As a result,
    guest logons are vulnerable to man-in-the-middle attacks that can expose sensitive data on the network. Windows disables insecure guest logons by default. Microsoft does not recommend enabling insecure guest logons.
    Background:
    The error message is due to a change we made in Windows 10 Technical Preview (build 9926) which is related to security and remote file access that may affect you.
    Previously, remote file access includes a way of connecting to a file server without a username and password, which was termed as “guest access”.
    With guest access authentication, the user does not need to send a user name or password.
    The security change is intended to address a weakness when using guest access.  While the server may be fine not distinguishing among clients for files (and, you can imagine in the home scenario that it doesn’t
    matter to you which of your family members is looking at the shared folder of pictures from your last vacation), this can actually put you at risk elsewhere.  Without an account and password, the client doesn’t end up with a secure connection to the server. 
    A malicious server can put itself in the middle (also known as the Man-In-The-Middle attack), and trick the client into sending files or accepting malicious data.  This is not necessarily a big concern in your home, but can be an issue when you take your
    laptop to your local coffee shop and someone there is lurking, ready to compromise your automatic connections to a server that you can’t verify.  Or when your child goes back to the dorm at the university. The change we made removes the ability to connect
    to NAS devices with guest access, but the error message which is shown in build 9926 does not clearly explain what happened. We are working on a better experience for the final product which will help people who are in this situation. 
    As a Windows Insider you’re seeing our work in progress; we’re sorry for any inconvenience it may have caused.
    Suggestion:
    You may see some workarounds (eg. making a registry change restores your ability to connect with guest access).
    We do NOT recommend making that change as it leaves you vulnerable to the kinds of attacks this change was meant to protect you from.
    The recommended solution is to add an explicit account and password on your NAS device, and use that for the connections.  It is a one-time inconvenience,
    but the long term benefits are worthwhile.  If you are having trouble configuring your system, send us your feedback via the Feedback App and post your information here so we can document additional affected scenarios.
    Alex Zhao
    TechNet Community Support

    Hi RPMM,
    Homegroup works great in Windows 10 Technical Preview (9926 build), when I invited my Windows 10 Technical Preview (9926 build) joined in HomeGroup, I can access the shares smoothly:
    My shares settings is like this:
    Alex Zhao
    TechNet Community Support

  • Windows 10 Technical preview Build 9926 To Go

    I Have 5 hard drives with 4 operating systems Win 7 Both 32 & 64 Bit Win 8.1 & Win 10.
    Win 8.1 Was a 120 gig SSD, Cloned to a 240 gig SSD.  After that my Win 10 became Win
    10 To Go.  How can I get it so its not Win 10 To Go?  It will not update to the next build
    because it wont update to a USB device, witch its not.

    Would you care to do a clean install by downloading build 9879 Enterprise ISO, burn it to a bootable DVD or Flash Drive and then install ?Enterprise version has everything in a non- enterprise version plus a few extra features gear towards business
    people. You don't have to use them at all.
    If that is acceptable, here are the links :
    Windows 10 Enterprise build 9879 64-bit
    ISO image
    Windows 10 Enterprise build 9879 32-bit
    ISO image

  • WM_INPUT message no longer sent in Windows Technical Preview build 9879?

    I had software that relied on the WM_INPUT message and it used to work with previous builds (and Win 8.1). I needed it for remapping a wireless keyboard's fn key to CTRL key (I was using an Autohotkey script which captures WM_INPUT).
    But now looking at the messages sent when typing in the keyboard in a win32 app, only the button down and up are being sent. What changed? how to work around it?
    Now I am using a hacky combination of user32.dll's SendInput and some methods from setupapi.dll to read/send the special key values.

    Hello ibalhashim,
    From your description, do you mean that after remapping the fb to ctrl, then only the button down and up are being sent?
    If it is, please share us how you have remapped the keys and please test if removing the remapping operations, the WM_INPUT message would restore. This would help narrow down this issue to see if it is caused by the remapping operations or the win32 app.
    Regards.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Officejet Pro K550 in Windows Technical Preview

    The most recent update to Windows Technical Preview Build 9879 keeps stopping the print spooler when the Officejet Pro K550 is attached. It worked fine in the previous builds. Any ideas? I need to keep the USB cable disconnected until I want to print and then uninstall the printer each time or keep restarting the print spooler each time I want to print anything.
    Thanks

    Hi,
    Try running Windows Update and check if any driver update is available, any drivers for the Technical Preview are only available from Microsoft Update servers.
    If the issue persists, you will need to wait till an update will become available by microsoft, as a beta OS you are likley to experience this kind of issues, devices hasn't have been tested much, as well as the entire operating system.
    Shlomi
    Say thanks by clicking the Kudos thumb up in the post.
    If my post resolve your problem please mark it as an Accepted Solution

  • [Forum FAQ]Microsoft account sync settings in Windows 10 Technical Preview

    Summary
    Since Windows 8, Microsoft has introduced Microsoft Accounts. When you sign in to your PC or device with a Microsoft account, you
    can check email anytime, get Apps from the Windows Store,  and keep all your favorite stuff—devices, photos, friends, games, settings, music, and so on—up to date and in sync.
    From the release of
    Windows 10 Technical Preview, many users have upgraded to this new OS. You may would like to keep the personalization settings, such as Desktop, Themes, Start screen, Tiles and so on. It is smart to achieve this with the help of Microsoft accounts.
    Solution
    This article describes how to implement synchronization settings with the help of Microsoft accounts by an example.
    Note: The previous OS has connected to a Microsoft account and has been configured related sync settings.
    Example: In Windows 8.1, the layout of Start screen is shown as below, two extra icons have been pinned to the Start screen: Facebook which is needed to be installed manually and
    Control Panel which is a built-in item by design.
    Note: Start menu is been used by default in Windows 10 Technical Preview, if you want to switch to Start screen, please right click
    Taskbar\Properties\Start Menu, which is as shown below, uncheck the option
    Use the Start menu instead of the Start screen, then sign out and sign back.
    Steps
    Press Windows Logo +C, click
    Settings\Change PC Settings\OneDrive\Sync settings, and then turn on
    Sync your settings on this PC.
    Configure corresponding settings according to your demand. The settings of this example are shown as below:
    Connect the same Microsoft account in Windows 10 Technical Preview, configure the same sync settings, wait for several minutes, or restart Task Manager, sign out and sign back, restart. The setting configured in the previous system
    would be synchronized to the new OS, which is shown as below:
    From the picture above, we can find that the layout of Start screen is almost the same with the one of previous OS, Facebook and Control Panel are also synchronized to the Start screen in Windows
    10 Technical Preview. However, since Facebook is not a built-in app, you need to click the icon to install it before using it. Here we can see that the synchronized apps have not been installed.
    In this example, Background and Lock screen have also been synchronized, and the Taskbar has also been placed to the left edge just like the configurations in the previous system which is shown as below:
    Additional Resource
    If you want to get the latest IT News about Windows 10 Technical Preview, please join
    Windows Insider Program .
    Frequently asked questions about Windows 10 Technical Preview, please refer to:
    https://social.technet.microsoft.com/Forums/en-US/ce7dade5-f119-4eb1-a5c7-5f25c04eb038/qa?forum=WinPreview2014General
    Any questions or feedback, please visit the TechNet Forum at
    https://social.technet.microsoft.com/Forums/en-us/home?category=WinPreview2014
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Thank for the write up.  I have "streamlined" the process to make it forward compatible with the new Tech Previews.
    I am using the following.
    - MDT 2013
    - Windows 8.1 ADK
    - Additional edits to LTIApply.wsf as detailed in original
    article with some modifications listed below.
    - Custom DISM script (link)
    1) Edit LTIApply.wsf and change the following code.
    Old Code
    If Left(oEnvironment.Item("OSCurrentVersion"), 1) >= "6" then
    New Code
    If ((Left(oEnvironment.Item("OSCurrentVersion"), 1) >= "6") or (Left(oEnvironment.Item("OSCurrentVersion"), 2) = "10")) then
    Then remove the following code and replace with the new code.
    Old Code
    Elseif Left(sOSBuild, 1) < "6" then
    iRetVal = ApplyImage( "nt52" )
    New Code
    Elseif Left(sOSBuild, 1) < "6" and Left(sOSBuild, 1) > "2" then
    iRetVal = ApplyImage( "nt52" )
    When it comes to DISM, no need to change the current structure.  Use the script at the following location and it will pull the DISM files from the Windows 10 WIM file automatically for you and apply them to the installation session.  Does
    not modify your MDT 2013 ADK in any way.
    A very smart guy figured this out, many kudos to Frank Lesniak for coming up with this little trick.
    http://blog.westmonroepartners.com/make-the-microsoft-deployment-toolkit-mdt-2013-able-to-deploy-windows-10-windows-server-vnext-and-hyper-v-server-vnext-technical-preview/
    After making only these changes, I am now able to deploy Windows 10 Technical Preview builds 9879 - 10061.
    Enjoy!  :)

  • Pin Programs on the Windows 7 Taskbar & Start Menu with Group Policy (Windows Server 2008 R2)

    Dear ALL,
    I want to Pin Programs on the Windows 7 Taskbar & Start Menu with Group Policy (Windows Server 2008 R2) as per below description. Can someone please help me how to proceed and achieve this. 
    Pin the following applications to the Taskbar:
    Outlook
    Pin the following applications to the Start Menu:
    Outlook
    Excel
    Word
    Internet Explorer
    Software Center
    Regards,
    Amit Kumar Rao

    https://www.google.de/search?q=windows+7+pin+to+taskbar+vbs
    Martin
    Mal ein
    GUTES Buch über GPOs lesen?
    NO THEY ARE NOT EVIL, if you know what you are doing:
    Good or bad GPOs?
    And if IT bothers me - coke bottle design refreshment :))

  • I have some windows minimized. When I try to open up another window from the start menu, even the minimized windows open up.

    When I first open up a window from the start menu, just one window opens up. But when others are at the bottom (minimized) and I go to open up a new window from the start menu, all the minimized windows open up, too.

    That can a problem with the Ask<i></i>.com toolbar (Tools > Add-ons > Extensions)
    See:
    * [[Troubleshooting extensions and themes]]

  • Known Issue: The XAML designer in VS and Blend will crash when opened in Windows 10 Technical Preview Build 10049

    Following the installation of Windows 10 Technical Preview Build 10049, the XAML designer in Visual Studio and Blend will crash when opened.

    We now have a patch you can install to work around the following issue: “The XAML designer in VS and Blend will crash when opened.”
    This is only intended to be used with the Windows version 10049, and Windows SDK version 10030.
    Download the following
    patch to a temp folder
    Unzip the files  into a TEMP folder.
    Exit Visual Studio if you have it opened.
    From an  administrative command prompt, run the batch file: XAMLUpdate10049.cmd.
    That should do it.  If you have any issues, please post questions to the
    Tools for Windows Store apps forum.

  • Known Issue: The XAML designer in VS and Blend will crash when opened in Windows 10 Technical Preview Build 10061

    Following the installation of Windows 10 Technical Preview Build 10061, the XAML designer in Visual Studio and Blend will crash when opened.

    We now have a patch you can install to work around the following issue: “The XAML designer in VS and Blend will crash when opened.”
    This is only intended to be used with the Windows version 10061, and Windows SDK version 10030.
    Download the following
    patch to a temp folder
    Unzip the files into a TEMP folder.
    Exit Visual Studio if you have it opened.
    From an administrative command prompt, run the batch file: XAMLUpdate10061.cmd.
    That should do it.  If you have any issues, please post questions to the
    Tools for Windows Store apps forum.

  • Hyper-V Not Enabling on Build 10041 of the Windows Technical Preview

          
    So I am running build 10041 of the Windows technical preview. I am not able to enable the Hyper-V Platform. Here are the steps:
    Go to Control Panel -> Program and Features -> Turn Windows features on or off - > Select Hyper-V Platform Checkbox.
    Windows will perform the install and request a restart.
    While restarting, I will get the updating windows message and at about 95 % it gives me a message to the tune of "Unable to update windows" and it roll backs the changes and restarts. No Hyper-V.
    Note that I can install the Hyper-V tools with out any issues just the Hyper-V Hypervisor and Hyper-V services will not install.
    Anyone have any ideas?

    So I am running build 10041 of the Windows technical preview. I am not able to enable the Hyper-V Platform. Here are the steps:
    Go to Control Panel -> Program and Features -> Turn Windows features on or off - > Select Hyper-V Platform Checkbox.
    Windows will perform the install and request a restart.
    While restarting, I will get the updating windows message and at about 95 % it gives me a message to the tune of "Unable to update windows" and it roll backs the changes and restarts. No Hyper-V.
    Note that I can install the Hyper-V tools with out any issues just the Hyper-V Hypervisor and Hyper-V services will not install.
    Anyone have any ideas?
    Can't provide an answer, but I have the same problem. I'd originally let my 9926 build, with Hyper-V installed and working, upgrade to the 10041 build. After installation things seemed OK, until I noticed I had no network connections working. They were all
    still there, but I had no network access and trying to view the properties of either my physical NIC or the Hyper-V switches just gave me an error.
    I tried uninstalling Hyper-V, but after doing that Windows wouldn't boot at all. It'd begin to start up, get almost to the login screen, but then die and reboot. I decided a rebuild would probably be best anyway, so I chose to do a Refresh when it offered
    me the advanced repair options.
    The Refresh mostly went well, the PC is running better now with a clean install, but I'm now stuck in the same situation where the Hyper-V server won't install. It installs, reboots, gets part way through configuring, then claims to fail and backs it all
    out again. No real diagnostic info presented as to why.

Maybe you are looking for