Windows 10 Technical Preview - Balloon Notification displayed at upper left corner always ?

I am testing both Windows 10 Technical Preview for x86 (Version 6.4.9841), Windows 10 Pro Technical Preview x86 (Version 10.0.9926) and x64 ( Version 6.4.9860 ) and enabled the balloon notification via local group policy manager:
1. "User Configuration->Administrative Templates->Start Menu and Taskbar->Disable showing balloon notifications as toasts" set to "Enabled"
2. RE-BOOT.
3. When I plugged and unplugged an USB thumb drive, the balloon notification shown at upper left corner of screen always.
This is not right, as I have existing applications depending on balloon notification as well.
Please advise.
Regards,
Ricky Gai.

This web site is for helping visitors in writing software.
To send feedbacks to Microsoft about the preview, use the feedback app.
Visual C++ MVP

Similar Messages

I used to have a +.- displayed in upper left corner to click and change text size. My sister used my computer and now I can no longer find this feature.

I used to have a +.- displayed in upper left corner to click and change text size. My sister used my computer and now I can no longer find this feature

Do you still have all toolbars visible (View > Toolbars)?
Did you use an extension or the standard zoom buttons that you can find in the toolbar palette in the View > Toolbars > Customize window ?
Press F10 or tap the Alt key to bring up the "Menu Bar" temporarily.

Windows 10 Technical Preview: Hiding OneDrive in the Explorer left pane

The title is self explanitory, here's a diagram: http://imgur.com/FDlIpPp .
If you notice, on the first panel, onedrive is there. In the second panel, onedrive is gone. Could I make the second panel reality?

Hi,
I'm afraid there is no option to remove OneDrive in Winows 10. If I found a method in the future, I would post here.
Thanks for your understanding.
Roger Lu
TechNet Community Support

Get volumes displayed by default under Home when opening File Explorer in Windows 10 Technical Preview

Scenario:
In Windows 8.1, it is to display volumes under This PC by default when opening File Explorer, which is as shown in Figure1. However, in Windows 10 Technical Preview, it is not to display volumes under Home by default when
opening File Explorer, which is as shown as in Figure 2. This articles describes a workaround to get volumes displayed by default under
Home when opening File Explorer in Windows 10 Technical Preview.
Workaround:
This workaround is to edit some related Registry keys. Note: Please click
Yes in the User Account Control prompt to continue. What’s more, 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. In this scenario, please backup the key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer.
Click Windows icon and type Folder option in Search box, and click
Folder option to open it.
Under View tab, clear the checkbox Hidden extensions for known file types
in Advanced settings.
Create a Text Document, copy the following lines into it, rename it as
Fix.reg. Double click the file fix.reg and click Yes to run this file
Windows Registry Editor Version 5.00
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MyComputer\NameSpace\{1CF1260C-4DD0-4ebb-811F-33C572699FDE}]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MyComputer\NameSpace\{374DE290-123F-4565-9164-39C4925E467B}]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MyComputer\NameSpace\{3ADD1653-EB32-4cb0-BBD7-DFA0ABB5ACCA}]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MyComputer\NameSpace\{A0953C92-50DC-43bf-BE83-3742FED03C9C}]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MyComputer\NameSpace\{A8CDFF1C-4878-43be-B5FD-F8091C1C60D0}]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MyComputer\NameSpace\{B4BFCC3A-DB2C-424C-B029-7FE99A87C641}]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\HomeFolder\NameSpace\DelegateFolders\{20D04FE0-3AEA-1069-A2D8-08002B30309D}]
@="This PC"
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\HomeFolder\NameSpace\DelegateFolders\{d34a6ca6-62c2-4c34-8a7c-14709c1ad938}]
@="Favorites Folder"
Open File Explorer again, and the new view is shown as the below picture:
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

i think what he want is to change the Win + E shortcut to This PC.
I understand that is the goal. I've tried the registry hack, it works, but I found it left fragments of other files from "Home' scatter around in there too. We all been using this new version of windows for a few weeks now, built up a list of stuff
we have looked at, and that is why I said it's not the prettiest solution. It might have been okay if it was done just after a fresh install. In my alternative solution, you are bringing the This PC icon out to a more accessible place so you
don't have to use the File Explorer icon to get at the volumes i.e. hard drive view.
Personally, when I launch the File Explorer, I am expecting to be looking for something straight away on my hard drives and not be presented with a list of stuff that I have already looked at. That kind of thing should be left
in a Recent Folder sort of thing we use to see in the older versions of windows.

Notification of expiration of Windows Server Technical Preview

Today the system gave me notification that the current build would expire on April 15, 2015 and that the computer would start restarting then. Will there be issued an update to the current Windows Server Technical Preview build by then or should the system
just be deleted at its expiration date?
Vladimir Shipitsyn

Hi,
Thanks for your post.
The reality is that we haven’t had a new build since the original.
Maybe an update will be released at some point in the near future that extends the lifespan of the current build (at least the lifespan without shutting down every few hours) beyond 15 April.
I think we could focus on the MS website if there is any updates.
http://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-technical-preview
Regards.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

When adding features, "Add features to Windows 10 Technical Preview" dialog displays error "Couldn't add features"

The process for adding features by selecting "Add features to Windows 10 Technical Preview" from control panel fails with error "Cannot add features. Your previous edition of Windows has been restored, but you should contact Microsoft support."
This occurs after entering the key and the system attempts to reboot and apply updates. During the reboot, the updates begin to apply, fail after a certain percent, then roll back. After rollback and logging in again the above mentioned error message is displayed
in the "Add features to Windows 10 Technical Preview" dialog. Build 9926. Any tips on how to fix this?

On Sun, 8 Feb 2015 11:40:59 +0000, ZigZag3143x [MVP] wrote:
Understood. I attempted the same thing and it was successful.
I've also done this with no problems.
Paul Adare - FIM CM MVP

Pavilion dm3 AMD switchable graphics (HD4000&HD5000) in Windows 10 Technical Preview

Basically it is a continuation of my previous topic:
http://h30434.www3.hp.com/t5/Notebook-Display-and-Video/Pavilion-dm3-AMD-switchable-graphics-HD4000-...
Users of HP laptops with switchable graphics HD4000/HD5000 will face the same problem after upgrade to Windows 10.
The earlier we'll start to discuss and find the solution for this sort of laptops the higher chance that we will be able to use our laptops in Windows 10.
I use Windows 10 Technical Preview now and I try to find the correct driver for my laptop.

Hello there mate got g510 iam on windows 10 insider preview build 10159 and it runs smooth! about the driver thingy i found it the most easy to do beyond all the other devices out there all u have to do is downlaod and install the last build from here : https://mega.nz/#!hUc2SSDI!9VRPiak8tS90rKbbVEEA0MCn5QbI8YgWRA_gCkFmcrY make sure to clean install it by 8gb at least flash driver and u are good to go ps: upgrading from older builds can make crashes and black screens after the amd driver installed so just make clean install for ur own good after u are done u can check for windows updates and it will take the intel and amd drivers that supports the wddm 2.0 plus the conexant audio and bluetooth ,Elan touchpad , the last stable ones comes with the updates and trust me its the most stable ones ive used so far the remaining unknown device and the pci is for the power manager and the intel imanagement engine u can use windows 8.1 x64 drivers for those sorry for the bad english tho xD

Windows 10 Technical Preview Enterprise Build 9879 Product Key

Hi
Does the Windows 10 Technical Preview Enterprise 9879 uses the same product key as build 9841???

I would have been totally satisfied if the final release was B9860.
I have installed the TP on all my pc's. I have 3 desktops and a laptop that I did clean installs for on spare hard drives.
I also cloned the Windows 8.1 systems from each of them - and upgraded to Win 10 TP to see how it would handle the variety of applications I have on each.
One minor issue was that a diagnostic application I prefer to use - lost some of it's capability to display certain components like CPU specs.
The audio had been working exceptionally well up to B9860. Then I had one major issue on one of the desktops - when the audio stopped working right. Microphone audio was passed to the speaker output correctly - but NO audio
was passed from Windows Media Player or Winamp. But it did pass audio thru to the speakers from a music editing application which I use.
Even more strange was that when I moved that hard drive to another desktop which has similar motherboard - the audio works perfectly. Both have VIA audio devices.
I also installed Win10 TP Enterprise on a hard drive and had the same results as above when booted up on those two desktop pc's. Whatever evidence I could extract has been passed back to Microsoft.
On checking I find the Win10 TP and Enterprise use the same key.
Otherwise - as you say - Windows 10 is GREAT. So I can't wait for the final release.
btw: I have done about a dozen different installs and never had to enter the install key when installing any of the Win10 systems. I have the general Win10 TP B9841 ISO burned to a DVD and each install had to be upgraded to the next build available.
The Enterprise comes as B9879 and I burned that ISO to a USB3 Flash Drive. Much better performance - and re-usable. So I will not be using DVD's in future.

Hardware Development Kits for Windows 10 Technical Preview now available!

Install the latest tools to build, test, and deploy drivers; test and measure your hardware running Windows; and customize, assess, and deploy Windows 10 on your hardware.
These tools are now available for Windows 10 Technical Preview:
Visual Studio 2015 CTP 6
Visual Studio Tools for Windows 10 Technical Preview
Windows SDK for Windows 10 Technical Preview
Windows Driver kit (WDK) 10 Technical Preview
Windows Hardware Lab Kit (HLK) Technical Preview
Windows Assessment and Deployment kit (ADK) Technical Preview
Become a
Windows Insider to get the latest Windows 10 technical preview and the latest hardware development kits and tools.
Get
the WDK samples from GitHub
Check out the
Windows Driver Framework source code. It’s now open source and available on GitHub!
Known issues
Be aware of these known issues (as of 3/23) in this release:
Windows SDK
After you install the Windows SDK, Windows 10 apps might not build successfully with
Visual Studio 2015 Community Technology Preview (CTP) 6 due to a of a metadata problem. Although you should not install the Windows SDK if you are doing app development, you can use the following workaround to build an app
successfully:
Exit Visual Studio.
Open a command prompt as administrator.
Run the \Program Files (x86)\Windows Kits\10\bin\x86\GenerateUnionWinMD.cmd script.
Windows ADK
When installing to Windows 7 PCs, run ADKSetup.exe in administrator mode.
WDK
Currently, WDM templates do not build
Driver deployment to target PCs won’t work if the
Display name used in the Device Configuration dialog is different than the
Network host name. In this release, verify that these names are the same.
Target creation of mobile devices causes Visual Studio to become non-responsive.

Hello ,
May I know ,where is the HLK download link
Is it likely HLKSetup.exe ??thanks
Windows Hardware Lab Kit (HLK) Technical Preview

[Forum FAQ]Tips on Upgrading Windows 10 Technical Preview from Build 9841 to 9860

The new Build 9860 for Windows 10 Technical Preview has been released recently. Here, I would like to share some experience on upgrading Windows 10 Technical Preview from Build 9841 to 9860.
Tip 1: How to use Refresh option to upgrade.
Scenario
In order to upgrade to Build 9860, the new preview build should be downloaded firstly:
PC settings-> Upgrade and recovery->
Preview builds, which is as shown below.
If there are multiples PCs which are running Windows 10 Technical Preview Build 9841 need to be upgraded, you may just want to use one copy of downloaded preview build to upgrade all of them instead of downloading the new build on each PC.
Solution
If you have upgraded one PC from Windows 10 Technical Preview Build 9841 to 9860, the downloaded preview build (install.esd) can be used to upgrade other PCs. Here we can use install.esd to export the install.wim, then this intall.wim can be used as a recovery
image.
Step 1: Understand the basic information about install.esd.
Install.esd file is located at C:\ $WINDOWS.~BT\sources folder at first. When the upgrade is finished, it would be copied to
C:\RecoveryImage folder. Here is the information in setupact.log which contains information about setup actions during installation:
2014-10-28 19:03:38, Info SP Moving file D:\$Windows.~BT\Sources\Install.esd to D:\RecoveryImage\Install.esd
What’s more, the command Dism /Get-Wiminfo /Wimfile:<path_to_install.esd> is used to display the information about the file install.esd:
Step 2: Export the file install.wim.
The following command is used to export Windows 10 Technical Preview Build 9860 image:
Dism /Export-Image /SourceImageFile:<path_to_install.esd>
/SourceIndex:4 /DestinationImageFile:<path_to_install.wim> /Compress:recovery
Step 3: Copy exported install.wim to other Windows 10 Technical Preview Build 9841 computers, and set the recovery image.
For example, the install.wim has been copied to C:\image folder, the following command is used to set the recovery image:
Reagentc /setosimage /path C:\image /index 1 /target C:\Windows.
Step 4: Use Refresh option to upgrade your PC.
Go to
Update and recovery setting under PC settings, choose
Refresh your PC without affecting your files:
Note:
Applications needed to be reinstalled.
System would use the exported install.wim to refresh Windows 10 Technical Preview from Build 9841 to 9860:
Note: If you use install.esd to refresh directly, just need point the index location as 4:
Reagentc /setosimage /path C:\image /index 4 /target C:\Windows. However, install.wim is easier for deployment, such as creating bootable USB, WDS and SCCM deployment.
Tip 2: Workground to upgrade native boot VHD.
Scenario
Many users use the method native boot into VHD to test Windows 10 Technical Preview. However, there is a limitation on native boot when using VHDs:
If you boot from a VHD, you cannot upgrade the Windows version in the VHD to a newer version. This article describes how to upgrade VHD system Windows 10 Technical Preview from Build 9841 to 9860.
Solution
Step 1: Upgrade in Hyper-V.
Use Hyper-v to create a new virtual machine, and use your native boot VHD
as an existing virtual hard disk:
If booting from this virtual disk directly, it would fail to start due to lacking of boot files. You can use Windows 10 Technical Preview Build 9841 ISO file to repair the startup issue:
You can boot intosystem successfully in Hyper-v, then the upgrade process would be supported.
Step 2: Create Native Boot to VHD.
When the upgrade is finished, shut down the virtual machine, use the same way to create Native Boot to VHD:
Mount the 9860 native boot VHD file.
Use the following command to create boot entry for VHD system: Bcdboot
v:\windows (v: represents the mounted virtual disk drive letter).
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hi Arman mohseni,
From my observation, if I click download now, it would create a BITS task:
We can use following command to check:
Import-module bitstransfer
Get-bitstransfer –allusers
From the output, we can see the system account created a BITS job for transferring, under the C:\Windows\Software Distribution\download, we can get the temporary downloaded file, which is approximately about 2.5G.
After we restart, and go to C:\Windows\Software Distribution\download, the temporary file is gone.
If I click the download again, the BITS would create a new task, a new temporary file, if we compare the JobIds of the two times downloading, they are totally different.
On the other hand, if we download a windows update, the JobId would be kept, and the temporary files would be kept, too.
Alex Zhao
TechNet Community Support

Booting Windows 10 Technical Preview an from SD Card

Hello!
I am interested in running the Windows 10 Technical Preview on my Late 2013 MacBook Pro with Retina Display. I have downloaded the .iso image, and copied it to a 32GB Class 10 UHS-1 Micro SD Card w/ adapter. Is it possible to boot from the SD Card (by holding the Option Key at startup) and install Windows 10 on the SD Card? My goal is to not use Bootcamp or partition my hard drive in any way, but to be able to use all of my MacBook's CPU, RAM, etc. without being slowed down by a VM like VirtualBox, and be able to take out the SD Card with no risk whatsoever when not in use, and even possibly use it on other computers.
Is this possible?
Are there any risks?
Driver issues with the MacBook's built in Keyboard or Mouse?
Thanks!

http://www.howtogeek.com/191054/how-to-create-bootable-usb-drives-and-sd-cards-f or-every-operating-system/
Ten second Google search.

Windows 10 Technical Preview bug

On 8.1 just installed 10. On first start everything was ok... it was until restarted... . When tried to login again everything on laptop display was black... In the bottom right part was language bar, that contains only help button...
Best wishes,
Ivan Spahiyski

It is highly recommended when installing Windows 10 Technical Preview to ensure that all devices are fully up-to-date with the latest drivers from the system or device manufacturer. Please update the video driver to see if the issue appears with the latest
drivers installed.
Brandon
Windows Outreach Team- IT Pro
Windows for IT Pros on TechNet

T540p problem with resume from sleep Windows 10 technical preview

On Windows 10 technical preview the resume from sleep problem shows up again. With 8.1 I solved it with drivers.
I'm running lattest BIOS and Intel and nVidia drivers.
Also on Windows 10 the fingerprint software causes endless loop as logon screen cannot be displayed because of fingerprint software crash.
I know this is technical preview but I'd like to let you know of problems so you fix them by release time.

so please help me how to roll back to windows 8.1
http://windows.microsoft.com/en-us/windows/preview-backup-restore

Windows 10 technical preview problem with lumia 730, wifi is not working and how to rollback to windows 8.1 please help

I installed windows 10 technical preview on my lumia 730 and now iam facing problem
1) unable to connect wifi
so please help me how to roll back to windows 8.1
in the forums it was written that if u have windows recovery tool then it is possible , but iam not able to find windows recovery tool.
Please help me my mail id [email protected]

so please help me how to roll back to windows 8.1
http://windows.microsoft.com/en-us/windows/preview-backup-restore

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 - Balloon Notification displayed at upper left corner always ?

Similar Messages

Maybe you are looking for