Windows 10, Build 9926. No MP3 sound

Whenever Windows Update runs, it ruins MP3 sound. Sound works throughout my system, but not MP3.
I have tried ALL drivers for my mother board. I have a Gigabyte 970A-UD3P and the drivers for MP3 sound, just do not work. I have noticed that I have 2 SPDIF options, one TX0 and TX1. Having TX0 as my main playback device gives me Windows sound, sound through
YouTube but no MP3 sound. Which Windows Update can I delete to give me back my sound since no drivers seem to work?

I had some trouble getting sound into and out of Cortana. For diagnostic purposes at least perhaps you could try the solution to my Cortana problem. If this solution works then the problem I ran into is more general than I thought.
Install a new sound driver. Install one that is obviously wrong and you are sure will not work. Reboot. Reinstall the correct driver. Reboot.
I am not expecting this to work but it will provide another data point that may ultimaltely lead to a solution to your problem.

Similar Messages

Surface Pro 3 Display/Video/Graphics Driver Issues - DisplayPort, External Monitors, Windows 10 Build 9926

Surface Pro 3 - i5 with Intel HD Graphics 4400
Windows 10 build 9926
All Latest updates installed
Intel Graphics Driver 10.18.15.4079.
Latest system update released on Jan 22nd (which I understand is just the latest intel graphics driver?).
The display driver status has this error message: Windows has stopped this device because it
has reported problems. (Code 43) - I assume it's
reverting to the basic Microsoft driver when this occurs. Which explains why my displayport (External monitors) will not work.
I have uninstalled the driver completely (and deleted the driver files), tried the Windows basic driver,
and rebooted several times with no luck.
I cannot get my docking station displayport or the displayporton my surface pro 3 working.
According to Microsoft (see below), this is a known issue UNTIL you update to display driver
version 4079 - which I have.
Known issues on Surface after updating to Windows 10 January Technical Preview
On Surface Pro 2 and Surface Pro 3, the Mini DisplayPort won’t work on the Windows 10 January Technical Preview until you’ve installed graphics driver 4079 or later. Check Windows Update often for the most recent graphics driver.
On Surface Pro 2 and Surface Pro 3, you’ll notice poor graphics rendering on the Windows 10 January Technical Preview until you’ve installed graphics driver 4079 or newer from Windows Update. Check Windows Update often for the most recent graphics driver.
If you’re using video driver 3496, you may need to start in safe mode and remove that driver. Then restart Surface in normal mode and go to Windows Update to get the most recent graphics driver.

Hi Nicholas,
Similar issue has been asked here:
Surface Pro 3 restarting after a series of blank screens!
For error code 43, here is a reference:
Code 43: Windows has stopped this device because it has reported problems
For the current situation, please try to wait for the driver update, as display driver version 4079 didn't work well at your side, please submit this through Windows Feedback Tool.
Best regards
Michael Shao
TechNet Community Support

Windows 10 Build 9926 - Can't connect to this network in certain networks

I have been asked to ask this question here. The original thread can be found at:
http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_web/windows-10-build-9926-cant-connect-to-this-network/e9196f95-5570-4a92-8fae-d29d7d1416b2?msgId=b2246cb5-1038-40dc-98b6-249e8734eb7f
Hello
I have a Samsung 700T tablet.
Since I got the latest update 9926 I am having issues with my corporate network access. I have to type in my user name and password on the wireless connection. When I do I get "Can't connect to this network" message.
I have tried multiple drivers for the network card a "Intel(R) Centrino(R) Advanced-N 6235". I am currently using latest.
I am able to connect fine with my home Wifi.
On the "System" event log I get the following error message when I attempt to login no the WiFi.
"A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 42"
Any ideas?
I have checked and my card is set to use DHCP.
God bless,
Bruno
--- got this answer ----
Have you tried talking to your system administrator? We had a fun bug in our Cisco wireless access points and wireless controller that would
kick Win 8+ machines from even trying to connect. A very long firmware and software update process fixed it.
--- answered back ----
Hello DatAsian,
Thank you for your response.
This is a very large wireless network, and as far that I know I am the only one having this issue. My other devices on the same cube work fine. The only difference is of course Windows 10. The other machines are Windows 8.1 and Windows 7.
In the past this was caused by a driver, but I have gotten about 6 different version of my wireless driver and they all have this issue.
I read on the troubleshoot about entering the wireless configuration manually by using the "Hidden network" screen. The instructions go:
2. Tax or click to connect to a network
3. Tap or click Hidden network tap or click Connect and then enter the network info.
I cannot find this "Hidden network" text on the "Connect to a network" screen. Am I missing something? Do I need to check something that allows me to connect to Hidden network?
One thing that I forgot to mention. I need to enter my user name and password when I enter this wireless network, since this is Employee Own device network.
Any other ideas?
God bless,
Bruno
When I use an android device I had to do the following changes to the way the device connected to wireless:
EAP Method: TTLS
Phase 2 Authentication: PAP
Then I have to use my user name and password.
Is there a way to set windows to the same type of authentication?
Please let me know.
God bless,
Bruno

Hi Alex,
I have the similar problem with Bruno, using the
certificate network.
The Event View show message of the Wired-AutoConfig as below:
Information 1:
Network authentication attempts have been resumed on this network adapter.
Network Adapter: Intel(R) 82579LM Gigabit Network Connection
Interface GUID: {************************}
Information 2:
Wired 802.1X Authentication was started.
Network Adapter: Intel(R) 82579LM Gigabit Network Connection
Interface GUID: {********************}
Connection ID: 0x2
Error:
Wired 802.1X Authentication failed.
Network Adapter: Intel(R) 82579LM Gigabit Network Connection
Interface GUID: {******************************}
Peer Address: ************
Local Address: ************
Connection ID: 0x2
Identity: -
User: -
Domain: -
Reason: 0x70006
Reason Text: The network does not support authentication and 802.1X is enforced in the profile
Error Code: 0x0
Information 3:
Network authentication attempts have been temporarily suspended on this network adapter.
Network Adapter: Intel(R) 82579LM Gigabit Network Connection
Interface GUID: {*************************}
Reason Code: The network does not support authentication and 802.1X is enforced in the profile
Length of block timer (seconds): 1200
everything find with Windows 7 and 8.1
days searching the internet but nothing makes sense.
looking forward to your help
Thanks!

RDS - Issue using Windows 10 build 9926 as Virtual Desktop Infrastructure on Hyper-V 2012 R2

We currently have a production Windows 8.1 as a VDI/RDS on Hyper-V 2012 R2. On testing the last build of Windows 10 (98??) we had no issues deploying this in same RDS as pooled desktops.
The latest build 9926, although correctly sysprep-ed (either by removing AppX modern apps that have been updated, or not connecting the template to the internet), the build is only ever partially successful. Some VMs build others do not, and the ones that
build cannot be managed via RDS/Server Manager, functions such as logging a user off with server manager, result in an error. (WTS API failed)
Build Error on connection Broker - Microsoft-Windows-TerminalServices-SessionBroker
VM host [HOSTSERVER05] failed to execute VM Provisioning operation [Task: To perform post processing actions at VMHostAgent:] for virtual machine [VDI-W10-57] in pool [VDI_Advanced_Te], Error: [Error code: 0x88130221.]
Any guidance on how to troubleshoot this would be greatly appreciated, although I suspect something regarding the auto-deployment/unattend and management systems though RDS no longer works with the latest Windows 10 build.
Already posted this in the
Windows Insider Program site, but was asked to re-post here. Thanks

OK, I've carried out some more testing on the client site and have been able to move a couple of existing VMs from their 2008 R2 Hyper-V server to the new 2012 R2 server.
Both VMs are Windows 7 SP1 with the RDP 8.0 update installed and I can connect to them from a Thin Client running RDP 7.1 and a laptop running RDP 8.0.
When I add the RemoteFX vGPU to them both I can still connect from both devices but, as suggested, when connecting from the laptop with RDP 8.0 I don't get the vGPU performance (but the vGPU is still shown in the device manager).
It all looks good at the moment but I'm still concerned as to why I was unable to connect to the first VM I moved over (it was complaining about a error in the License network communication or similar).
I'll keep testing and post anything else that might be useful.
Cheers for now
Russell

Windows update Build 9926

Windows update is not working correctly when set to "Notify to schedule restart" while on a metered network. After a restart it indicates that everything is up to date even though prior to restart there were updates available to download. Possibly
an option to download over a metered connection should also be available much like in Outlook.

also see this link
https://social.technet.microsoft.com/Forums/en-US/2446b840-3f8a-4365-bcf0-01025510a309/solved-windows-update-does-not-work-in-domains-with-wsus-error-0x80070057-and-no-updates-show?forum=WinPreview2014General
windows update has some little changes compared to previous build version, and ConfigMgr/WSUS isn't aware of this strange OS, so the registry trick could be the workaround, since this is a preview version, I think there will be some updates
http://www.systemcenter.ninja/2015/01/windows-update-missing-from-classic.html

Cry for help: build 9926 windows update errors: 0x80240438 0x80244019

lately I'm stuck with build 9926
when I check for updates it works, and it even downloads some updates according to the logs
but, that's about it , it's not updating anything.
tried all the solutions on the internet
I synced with the appstore.
but noting...
microsoft... are you ready to do a webex with me ? and solve this ?
here is some of the logfile from file:
"C:\Windows\SoftwareDistribution\ReportingEvents.log"
{EE67F390-701B-4854-A8CC-4CEB3286A7DF} 2015-03-18 23:40:05:911+0200
1 148 [AGENT_DETECTION_FAILED]
101 {00000000-0000-0000-0000-000000000000}
0 80240438
TrustedInstaller MCR Failure
Software Synchronization Windows Update Client failed to detect with error 0x80240438.
{55A19B50-6899-44B2-9F0F-FFE14B3FE27B} 2015-03-18 23:44:25:732+0200
1 148 [AGENT_DETECTION_FAILED]
101 {00000000-0000-0000-0000-000000000000}
0 80240438
Dynamic Update Failure
Software Synchronization Windows Update Client failed to detect with error 0x80240438.
{899A21E6-D8DE-4155-8963-AFE8080BDD9F} 2015-03-18 23:44:59:195+0200
1 148 [AGENT_DETECTION_FAILED]
101 {00000000-0000-0000-0000-000000000000}
0 80240438
Dynamic Update Failure
Software Synchronization Windows Update Client failed to detect with error 0x80240438.
{DCDC8F70-8099-4FA4-97E7-43C36F5368D1} 2015-03-18 23:45:10:107+0200
1 148 [AGENT_DETECTION_FAILED]
101 {00000000-0000-0000-0000-000000000000}
0 80240438
Dynamic Update Failure
Software Synchronization Windows Update Client failed to detect with error 0x80240438.
{C64C44D7-F35C-4DF7-9E6C-C19400AEC88E} 2015-03-18 23:50:53:941+0200
1 148 [AGENT_DETECTION_FAILED]
101 {00000000-0000-0000-0000-000000000000}
0 80240438
UpdateOrchestrator Failure
Software Synchronization Windows Update Client failed to detect with error 0x80240438.
{C702CE4C-F06D-483D-8499-EC01C5E94E81} 2015-03-18 23:53:58:191+0200
1 148 [AGENT_DETECTION_FAILED]
101 {00000000-0000-0000-0000-000000000000}
0 80240438
UpdateOrchestrator Failure
Software Synchronization Windows Update Client failed to detect with error 0x80240438.
{8BF69B20-4AB5-48CB-ADA6-51D0A307322C} 2015-03-19 00:03:46:225+0200
1 148 [AGENT_DETECTION_FAILED]
101 {00000000-0000-0000-0000-000000000000}
0 8024402c
AutomaticUpdates Failure
Software Synchronization Windows Update Client failed to detect with error 0x8024402c.
{F93F393E-47E3-439D-BF2F-C626FCF78949} 2015-03-19 00:03:50:023+0200
1 147 [AGENT_DETECTION_FINISHED]
101 {00000000-0000-0000-0000-000000000000}
0 0
AutomaticUpdates Success
Software Synchronization Windows Update Client successfully detected 3 updates.
{69438178-7069-4792-AF02-FF50A2BF11AA} 2015-03-19 00:04:37:647+0200
1 147 [AGENT_DETECTION_FINISHED]
101 {00000000-0000-0000-0000-000000000000}
0 0
AutomaticUpdates Success
Software Synchronization Windows Update Client successfully detected 2 updates.
{3DED2228-2046-4A39-B839-C7BE632FFAFD} 2015-03-19 00:04:45:278+0200
1 147 [AGENT_DETECTION_FINISHED]
101 {00000000-0000-0000-0000-000000000000}
0 0
AutomaticUpdates Success
Software Synchronization Windows Update Client successfully detected 3 updates.
{CC0DB0F0-4C4E-4EE2-B7EA-787E20F95959} 2015-03-19 00:04:51:481+0200
1 148 [AGENT_DETECTION_FAILED]
101 {00000000-0000-0000-0000-000000000000}
0 8024402c
AutomaticUpdates Failure
Software Synchronization Windows Update Client failed to detect with error 0x8024402c.
{BD00D6ED-7C99-4C1A-9855-4346D46A13AA} 2015-03-19 00:05:10:166+0200
1 189 [AU_UNSCHEDULED_INSTALL_READY]
102 {00000000-0000-0000-0000-000000000000}
0 0
AutomaticUpdates Success
Content Install Installation Ready: The following updates are downloaded and ready for installation. To install the updates, an administrator should log on to this computer and Windows will prompt with further instructions:
- drm
{00658682-7DDF-43E8-8AD6-689A50ACD0F8} 2015-03-19 00:05:18:847+0200
1 189 [AU_UNSCHEDULED_INSTALL_READY]
102 {00000000-0000-0000-0000-000000000000}
0 0
AutomaticUpdates Success
Content Install Installation Ready: The following updates are downloaded and ready for installation. To install the updates, an administrator should log on to this computer and Windows will prompt with further instructions:
- drm - VCLibs 12 Preview
{6A05284D-27F5-4EA9-A615-810C190A2F86} 2015-03-19 00:05:24:980+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{E0711B88-4FC2-40C1-BB02-AD541708D409} 2015-03-19 00:05:25:207+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{26C87A3C-85C1-4A34-9F96-E80EFEA8E6CD} 2015-03-19 00:05:27:826+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{0AB1F0C6-7EFE-4227-BE72-4B63683A71FA} 2015-03-19 00:05:28:032+0200
1 167 [AGENT_DOWNLOAD_STARTED]
101 {EC7D0E7D-BB3F-4674-AF02-A32293A19F5F}
1 0
AutomaticUpdates Success
Content Download Download started.
{4064BECB-FDF4-4160-83DA-62766D7101F9} 2015-03-19 00:05:28:103+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{935F6118-7E74-4E24-BE48-50980031F8E9} 2015-03-19 00:05:28:295+0200
1 167 [AGENT_DOWNLOAD_STARTED]
101 {BFFF18AE-83DC-4661-BE5A-ABDD585A5157}
1 0
AutomaticUpdates Success
Content Download Download started.
{625A9F42-B81F-4B15-981D-4109C303AB01} 2015-03-19 00:05:28:357+0200
1 162 [AGENT_DOWNLOAD_SUCCEEDED]
101 {D6ABD84B-D769-46D2-BDB9-E942DA9F8CEB}
1 0
AutomaticUpdates Success
Content Download Download succeeded.
{8DECCDE7-A741-49A7-92ED-908018BF48E7} 2015-03-19 00:05:28:358+0200
1 162 [AGENT_DOWNLOAD_SUCCEEDED]
101 {2E895204-66E8-482D-8184-AFE29C3DD719}
1 0
AutomaticUpdates Success
Content Download Download succeeded.
{299D3FF5-72FD-4EC2-A27D-96C380FFB06A} 2015-03-19 00:05:49:013+0200
1 147 [AGENT_DETECTION_FINISHED]
101 {00000000-0000-0000-0000-000000000000}
0 0
AutomaticUpdates Success
Software Synchronization Windows Update Client successfully detected 2 updates.
{7EF8F36D-1B21-4D24-8E8C-80CAE968CC93} 2015-03-19 00:05:57:589+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{0CE20454-71A9-4CEF-93DA-AA853AEB9A03} 2015-03-19 00:05:57:835+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{9D08DD20-16D7-46BD-8C6B-BAE6E37FF66B} 2015-03-19 00:05:58:370+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{46C47722-09F0-40CA-B50C-C4529D3AE438} 2015-03-19 00:05:58:450+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{18E7A41D-60A7-4CEF-A82A-0092B5CCF63C} 2015-03-19 00:06:00:686+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{744A5A7F-EB06-4319-8FB8-06138823A23F} 2015-03-19 00:06:00:906+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{B3AEF57C-0FBD-4B03-B225-E4A0166AA47E} 2015-03-19 00:06:01:027+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{FE3EC6F7-99D1-436C-8492-9E7EFA9479CF} 2015-03-19 00:06:01:331+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{42829509-DFC5-4ADE-A8E6-325F7DD8D99A} 2015-03-19 00:06:11:955+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{830D44A1-4B7F-4C10-B3A3-7D2099515618} 2015-03-19 00:06:12:277+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{23364FAC-813D-48A9-BED0-9BEF7CCF1388} 2015-03-19 00:06:12:371+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{FC526749-C1A3-4703-BE92-9F26EB13B573} 2015-03-19 00:06:14:250+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{1AF3930D-A9F7-4641-9ECB-1CE140B41B90} 2015-03-19 00:06:14:405+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{E878B745-E246-4BB6-86FE-B7CA17B1D4AD} 2015-03-19 00:06:14:516+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{5115A0BD-FB49-4F57-9479-58EC8B2413E5} 2015-03-19 00:06:14:715+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{202870B5-4F10-485E-B721-BC00D09BA551} 2015-03-19 00:06:16:011+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{CE50F467-6671-46EE-AFB1-3D131A43DE70} 2015-03-19 00:06:16:340+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{06207896-59E0-4D98-885D-EE68B5E8AAF9} 2015-03-19 00:06:16:447+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{78E23EED-D6BF-4F66-90DF-3684163A980C} 2015-03-19 00:06:16:697+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{4ABC18A2-72D0-4008-9ADC-269C9BD827C8} 2015-03-19 00:06:16:897+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{DF095BC0-4C61-4A67-9946-751BC8CB9652} 2015-03-19 00:06:17:097+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{04BAFD9F-41A4-40D7-A42B-1C9A6C8EB418} 2015-03-19 00:06:17:330+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{0CBCEE49-AACA-4FEA-A98B-7D85D15B0BAE} 2015-03-19 00:06:17:546+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{D9E189B6-613A-4D9B-A835-243906C45C27} 2015-03-19 00:06:17:931+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{B25B5435-DA55-4F98-B129-1796058051FC} 2015-03-19 00:06:38:092+0200
1 189 [AU_UNSCHEDULED_INSTALL_READY]
102 {00000000-0000-0000-0000-000000000000}
0 0
AutomaticUpdates Success
Content Install Installation Ready: The following updates are downloaded and ready for installation. To install the updates, an administrator should log on to this computer and Windows will prompt with further instructions:
- Microsoft.Reader
{7FC04992-3A7E-4895-8080-992629F54256} 2015-03-19 00:06:38:092+0200
1 189 [AU_UNSCHEDULED_INSTALL_READY]
102 {00000000-0000-0000-0000-000000000000}
0 0
AutomaticUpdates Success
Content Install Installation Ready: The following updates are downloaded and ready for installation. To install the updates, an administrator should log on to this computer and Windows will prompt with further instructions:
- drm - VCLibs 12 Preview
{3B2FD168-7585-42B7-942C-181651EF2842} 2015-03-19 00:06:38:109+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{31A13FC3-4EE4-4F76-BFCE-D723C6DFCAEF} 2015-03-19 00:06:38:294+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{1C05D134-7228-428C-870F-677D793F4CB4} 2015-03-19 00:06:38:490+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{BDD87834-5281-4427-9E2C-ED8C3C17C3C6} 2015-03-19 00:06:38:516+0200
1 162 [AGENT_DOWNLOAD_SUCCEEDED]
101 {EC7D0E7D-BB3F-4674-AF02-A32293A19F5F}
1 0
AutomaticUpdates Success
Content Download Download succeeded.
{DED48689-2F07-4965-9F52-C7885778B82A} 2015-03-19 00:06:39:141+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{8710E362-0FD4-42F4-8489-932AA5731578} 2015-03-19 00:06:39:639+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{F82D5E5C-E84D-4E47-8791-2681BA6F440D} 2015-03-19 00:07:14:766+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{50EF2781-FB16-47A1-9826-19F0E52F4253} 2015-03-19 00:07:14:773+0200
1 189 [AU_UNSCHEDULED_INSTALL_READY]
102 {00000000-0000-0000-0000-000000000000}
0 0
AutomaticUpdates Success
Content Install Installation Ready: The following updates are downloaded and ready for installation. To install the updates, an administrator should log on to this computer and Windows will prompt with further instructions:
- Microsoft.Reader - microsoft.windowscommunicationsapps
{33F9699F-AEDC-413F-95B9-E76015F0E825} 2015-03-19 00:07:14:773+0200
1 189 [AU_UNSCHEDULED_INSTALL_READY]
102 {00000000-0000-0000-0000-000000000000}
0 0
AutomaticUpdates Success
Content Install Installation Ready: The following updates are downloaded and ready for installation. To install the updates, an administrator should log on to this computer and Windows will prompt with further instructions:
- drm - VCLibs 12 Preview
{4351600E-D070-4431-84CE-34FB1109D4DC} 2015-03-19 00:07:14:774+0200
1 162 [AGENT_DOWNLOAD_SUCCEEDED]
101 {BFFF18AE-83DC-4661-BE5A-ABDD585A5157}
1 0
AutomaticUpdates Success
Content Download Download succeeded.
{FFFCFC30-061C-46E6-8DD4-6285888D76FD} 2015-03-19 00:07:15:067+0200
1 148 [AGENT_DETECTION_FAILED]
101 {00000000-0000-0000-0000-000000000000}
0 80240438
UpdateOrchestrator Failure
Software Synchronization Windows Update Client failed to detect with error 0x80240438.
{B2CA6BDB-DB4B-4B1B-A016-9EE4B1D103AA} 2015-03-19 00:21:30:391+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{586F4FE2-C760-4861-BE9F-0D41375A6857} 2015-03-19 00:21:30:435+0200
1 168 [(null)]
101 {2332A99D-854E-4844-9B4D-8E43EE5A191A}
1 0
AutomaticUpdates Success
Content Download Download queued.
{A8166E7D-EF9B-4DBF-AA6A-33C902392926} 2015-03-19 00:23:36:845+0200
1 148 [AGENT_DETECTION_FAILED]
101 {00000000-0000-0000-0000-000000000000}
0 80244019
UpdateOrchestrator Failure
Software Synchronization Windows Update Client failed to detect with error 0x80244019.
{CFAE4B73-8337-4A28-8E62-34AFBA6459A2} 2015-03-19 00:24:30:326+0200
1 148 [AGENT_DETECTION_FAILED]
101 {00000000-0000-0000-0000-000000000000}
0 80240438
UpdateOrchestrator Failure
Software Synchronization Windows Update Client failed to detect with error 0x80240438.
{E8108901-47D2-4F23-91C8-31175089B009} 2015-03-19 00:24:32:772+0200
1 147 [AGENT_DETECTION_FINISHED]
101 {00000000-0000-0000-0000-000000000000}
0 0
WSAutoUpdate Success
Software Synchronization Windows Update Client successfully detected 3 updates.
{1B2E37CF-F050-4CED-A90D-1BD717F2C3E0} 2015-03-19 00:25:43:823+0200
1 148 [AGENT_DETECTION_FAILED]
101 {00000000-0000-0000-0000-000000000000}
0 80240438
UpdateOrchestrator Failure
Software Synchronization Windows Update Client failed to detect with error 0x80240438.
{041F8319-F24B-4438-9022-9B9CDB0095B5} 2015-03-19 00:26:20:900+0200
1 148 [

Hi Erez,
Could you please share us the WindowsUpdate.log file here?
From the information youposted, it seems to be Windows Update can't check for the updates, you may try to run Windows Update Troubleshooter first, it that didn't help, run the following command using the Windows 10 9926 ISO to repair:
DISM /Online /Cleanup-Image
/RestoreHealth /source:WIM:F:\sources\install.wim:1
/LimitAccess
F: Drive stands for the mounted Windows 10 build 9926 ISO.
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

DragAcceptFiles Working in Windows 10 TP build 9926 But Not Working In build 10049 and build 10061

This is a cross post from
https://social.technet.microsoft.com/Forums/en-US/a63519d4-ba7a-46c1-bb34-ad034b836964/dragacceptfiles-working-in-9926-but-not-working-in-10049-and-10061?forum=WinPreview2014General. The moderator suggested I post this here:
My company has a software product that accepts dragged items. In all versions of Windows from XP through Windows 10 build 9926 that functionality has worked fine. However, with build 10049 (possibly 10041 which I did not test thoroughly before going
to 10049) and now 10061 that functionality stopped working. The application calls DragAcceptFiles to enable drag drop messages. In addition, either ChangeWindowMessageFilter is called on Vista or ChangeWindowMessageFilterEx is called on Windows
7 and higher for the messages WM_DROPFILES, WM_COPYDATA, and WM_COPYGLOBALDATA. This was working fine on Windows 10 build 9926. Now when I attempt to drag an item to our software product, I get the "Don't" symbol (circle with line through
it) and no WM_DROPFILES messages are received. The application is unchanged with only an upgrade to the Windows 10 build performed. As a sanity check, I created a brand new VM running build 9926 and the functionality worked fine. I then upgraded
the VM to 10049 and it stopped working. The following day I upgraded to 10061 and it is still broken. Is there are new filter or restriction in place since build 9926 on DragAcceptFiles that would be stopping the traditional drag drop procedure
from working? This is very frustrating because there is a dearth of information on Windows 10 API changes and since this appears to be some kind of recent change, I am out of ideas of where to look for answers. I can duplicate this problem on the older
platforms by simply calling DragAcceptFiles with the second parameter set to false. In that case, on Windows 7 for example, I will get the "Don't" symbol just I am getting now in the Windows 10 TP with the argument set to true.

DragAcceptFiles is now working again in 10074 so whatever the problem was, it has been fixed.

Win 10 Build 9926 Virtual Machine hangs at "Getting Ready" screen.

Clean installing Build 9926 as a Virtual Machine with VMware Player (non-commercial version).
On a Windows 8.1 system with 8GB RAM and Quad Core Q9300 CPU.
Install gets to the "Getting Ready" screen and just hangs for ever. Not frozen.
Installing from ISO file from a separate drive, not DVD.
Same thing happens with VirtualBox
Previous build worked fine.
Thoughts?
Thank you.

It's a driver thing. If you disable audio it will be good and the install goes on. That was the case in my situation. Once Windows 10 build 9926 is installed enable audio again to install it. Or leave it off if it's not compatible.
In VMware Windows 10 build 9926 will install audio but with the option off in VMware you won't hear sound. After you enable it you will hear sounds from Windows 10 ;)
ps. If disabling audio in VMware does not do the trick, disable temp. other hardware such as the NIC and enable it again in VMware options after Windows 10 is successfully installed.

Error sfc /scannow in the build 9926, Help!!!

I installed (in italian)in clean install
the new build 9926 for Enterprise from
iso file, and running
sfc/scannown i by
the following error and stops at 9%
Windows Resource Protection: Can not perform the requested operation.
I tried to restore the system without any updates,
but the error persists. Also
using Dism /online /cleanup-image /Restore health,
gives me error!
Thank You
Windows 8.1 Pro 32-Bit Media Center ASUS P5G41T-M LE Ram 4GB

Already done, but also making a new
clean install with the iso file, the problem persists.
Will have helped to make matters worse
the KB3035129; see here:
http://winpreview.com/2015/01/29/recap-important-update-kb3035129-arrives-windows-10-build-9926 and
http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_update/error-0x80246017-after-kb3035129-update/0d702a0d-b41a-48ad-9fff-4e12a9072285
Hello
Windows 8.1 Pro 32-Bit Media Center ASUS P5G41T-M LE Ram 4GB

RSAT Tools won't install (the update is not applicable to your computer) in build 9926

Trying to install Remote Server Administration Tools in Windows 10 Technical Preview build 9926
Downloaded WindowsTH-KB2693643-x64.msu
Gives error "the update is not applicable to your computer"

Hi SeanSauve,
The below is the information I quoted from the system requirements part on the download page:
Supported Operating System
Windows 10 , Windows 10 Tech Preview , Windows 8.1
**Remote Server Administration Tools for Windows 10 Technical Preview can be installed ONLY on computers that are running the second release of Windows 10 Technical Preview.** Remote Server Administration Tools cannot be installed on Windows
RT, computers with an Advanced RISC Machine (ARM) architecture, or other system-on-chip devices.
Remote Server Administration Tools for Windows 10 Technical Preview runs on both x86- and x64-based editions of builds 9926 and later releases of Windows 10 Technical Preview, including all updates. This release does not run on Windows 10 Technical
Preview builds that are older than 9926. Download and install the version that matches the architecture of the computer on which you plan to install the administration tools. If you are not sure whether your computer is x86- or x64-based, see
How to determine whether a computer is running a 32-bit version or 64-bit version of the Windows operating system.
Remote Server Administration Tools for Windows 10 Technical Preview is available only in United States English (en-US) for this release.
IMPORTANT: Remove all older versions of Administration Tools Pack or Remote Server Administration Tools—including older prerelease versions, and releases of the tools for different languages or locales—from the computer before you install Remote
Server Administration Tools for Windows 10 Technical Preview. Only one copy at a time of Remote Server Administration Tools can be installed on a computer. If you have upgraded to Windows 10 Technical Preview from an older release of Windows, you will need
to install Remote Server Administration Tools for Windows 10 Technical Preview on the computer; no earlier releases of Remote Server Administration Tools are still installed on a computer that you have upgraded to Windows 10 Technical Preview.
Remote Server Administration Tools for Windows 10 Technical Preview includes support for remote management of computers that are running the Server Core installation option or the Minimal Server Graphical Interface configuration of Windows Server Technical
Preview. However, Remote Server Administration Tools for Windows 10 Technical Preview cannot be installed on any releases or installation options of the Windows Server operating system.
Earlier releases of Remote Server Administration Tools (such as those for Windows 8.1) are not available--nor do they run--on Windows 10 Technical Preview.
Server Manager is included with Remote Server Administration Tools for Windows 10 Technical Preview; GUI-based tools that are part of this release of Remote Server Administration Tools can be opened by using commands on the Tools menu of the Server Manager
console. To use Server Manager to access and manage remote servers that are running Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2, you must install several updates on the older operating systems. For more information
about requirements for using Server Manager to manage remote servers, see
Manage multiple, remote servers with Server Manager.
More information, see:
Remote Server Administration Tools for Windows 10 Technical Preview (January 2015)
Please check and see if your current build is Windows 10 build 9926, and the system language, RSAT should not be able to install on the other language versions of Windows 10 other than EN-US.
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

Error 0x80070050 while updating Windows 10 TP Enterprise Build 9926

Hello. I'm currently using Windows 10 TP Build 9926.
Windows Update & Recovery tool indicates that there is new build of Windows 10 TP (Build 10041). Also there is update for Windows Defender (1.193.3002.0). But when I'm trying to install them process stop with error 0x80070050. Any suggestions pls?
Thank you in advance

Hi,
@ ALF_er, this version is for Windows 10 Pro Technical Preview 10041 build, it is recommended to perform a clean install, if you need the enterprise version for test, here is a workaround:
Forum FAQ] How to use Windows Imaging and Configuration Designer to upgrade from Windows 10 pro to Enterprise Version
https://social.technet.microsoft.com/Forums/en-US/c91fe33d-5097-46d4-81b1-57e36ca31409/forum-faq-how-to-use-windows-imaging-and-configuration-designer-to-upgrade-from-windows-10-pro-to?forum=WinPreview2014Setup
@ david hk129, yes, currently, there is no 10041 build Enterprise ISO release, we may need wait for a short time.
Regards,
Alex Zhao
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

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

How do I enable all sound files wav,MP3 on windows 7 64-bit change system sounds

How do I enable all sound files wav,MP3 on windows 7 64-bit change system sounds it will only give me the option to choose wav?

Windows 7 uses .wav (wave) files for the sound events. The default folder that Windows 7 uses to store the sound files in is located at C:\Windows\Media.
You cannot use a MP3 file but there are lots of (WAV to MP3 converters) available on internet which can help you to convert MP3 to wav serving your purpose of changing system sound.
//Click on Kudos and Accept as Solution if my reply was helpful and answered your question//
I am an HP employee!!

[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

Windows 10 technical preview latest build 9926 won't rise

After install cisco vpn client windows 10 technical preview latest build 9926 won't rise, only black screen and mouse arrow ?????How to fix it ?

I used the option to refresh the pc
that is uninstalled everything
except win10 OS(even
office 2013).after that
the system is started.
It is still a problem installing
cisco vpn client ..... how to solve.
Any suggestion...

Windows 10, Build 9926. No MP3 sound

Similar Messages

Maybe you are looking for