Shutdown Error Build 10041

Whenever I select shutdown from the start menu my computer goes into the process of shutting down but then it has issues closing Microsoft .NET Framework and it brings my computer back to my desktop. I am not entirely sure how to resolve the issue. I provided
the error message I receive after it sends me back to desktop.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host
Server stack trace:
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.Runtime.Remoting.Channels.SocketStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.Runtime.Remoting.Channels.SocketHandler.ReadFromSocket(Byte[] buffer, Int32 offset, Int32 count)
at System.Runtime.Remoting.Channels.SocketHandler.Read(Byte[] buffer, Int32 offset, Int32 count)
at System.Runtime.Remoting.Channels.SocketHandler.ReadAndMatchFourBytes(Byte[] buffer)
at System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadAndMatchPreamble()
at System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadVersionAndOperation(UInt16& operation)
at System.Runtime.Remoting.Channels.Tcp.TcpClientSocketHandler.ReadHeaders()
at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at AlienLabs.CommandCenter.RemotingService.Domain.ApplicationLaunchWatcher.remove_ApplicationLaunched(ApplicationLaunchedEventHandler value)
at AlienLabs.CommandCenter.RemotingService.Domain.Classes.ApplicationLaunchWatcherHolder.unregisterApplicationLaunchedEvent(ApplicationLaunchedEventHandler eventHandler)
at AlienLabs.CommandCenter.RemotingService.Domain.Classes.ApplicationLaunchWatcherHolder.ReleaseWatcher(ApplicationLaunchedEventHandler eventHandler)
at AlienLabs.AlienFX.Controller.ControllerMainForm.closingApplication()
at AlienLabs.AlienFX.Controller.ControllerMainForm.formClosing(Object sender, FormClosingEventArgs e)
at System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e)
at System.Windows.Forms.Form.WmClose(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at AlienLabs.AlienFX.Controller.ControllerMainForm.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.6.42.0 built by: NETFXREL1
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
AlienwareAlienFXController
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/Program%20Files/Alienware/Command%20Center/AlienwareAlienFXController.exe
AlienLabsTools
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienLabsTools/v4.0_2.8.8.0__bebb3c8816410241/AlienLabsTools.dll
AlienwareAlienFXTools
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienwareAlienFXTools/v4.0_2.8.8.0__bebb3c8816410241/AlienwareAlienFXTools.dll
Alienlabs.CommandCenter.Tools
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Alienlabs.CommandCenter.Tools/v4.0_2.8.8.0__bebb3c8816410241/Alienlabs.CommandCenter.Tools.dll
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.6.42.0 built by: NETFXREL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System
Assembly Version: 4.0.0.0
Win32 Version: 4.6.42.0 built by: NETFXREL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.6.42.0 built by: NETFXREL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.6.42.0 built by: NETFXREL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.6.42.0 built by: NETFXREL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.6.42.0 built by: NETFXREL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
WindowsBase
Assembly Version: 4.0.0.0
Win32 Version: 4.6.42.0 built by: NETFXREL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll
PresentationFramework
Assembly Version: 4.0.0.0
Win32 Version: 4.6.42.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.dll
PresentationCore
Assembly Version: 4.0.0.0
Win32 Version: 4.6.42.0 built by: NETFXREL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/PresentationCore/v4.0_4.0.0.0__31bf3856ad364e35/PresentationCore.dll
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.6.42.0 built by: NETFXREL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.6.42.0 built by: NETFXREL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
AlienLabs.MasterIOBoard.Communication
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienLabs.MasterIOBoard.Communication/v4.0_2.8.8.0__bebb3c8816410241/AlienLabs.MasterIOBoard.Communication.dll
AlienFX.DeviceDiscovery
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.DeviceDiscovery/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.DeviceDiscovery.dll
AlienLabs.MasterIOBoard.Communication.Core
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienLabs.MasterIOBoard.Communication.Core/v4.0_2.8.8.0__bebb3c8816410241/AlienLabs.MasterIOBoard.Communication.Core.dll
AlienFX.Communication
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.dll
AlienFX.Communication.XPS
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.XPS/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.XPS.dll
AlienFX.Communication.Andromeda
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.Andromeda/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.Andromeda.dll
AlienFX.Communication.PID0x522
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x522/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x522.dll
AlienFX.Communication.PID0x521
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x521/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x521.dll
AlienFX.Communication.PID0x520
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x520/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x520.dll
AlienFX.Communication.PID0x518
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x518/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x518.dll
AlienFX.Communication.PID0x516
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x516/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x516.dll
AlienFX.Communication.PID0x515
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x515/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x515.dll
AlienFX.Communication.PID0x514
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x514/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x514.dll
AlienFX.Communication.PID0x513
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x513/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x513.dll
AlienFX.Communication.PID0x512
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x512/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x512.dll
AlienFX.Communication.PID0x511
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x511/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x511.dll
AlienFX.Communication.Core
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.Core/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.Core.dll
LightFX
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/LightFX/v4.0_2.8.8.0__bebb3c8816410241/LightFX.dll
AlienwareAlienFXModelResources
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienwareAlienFXModelResources/v4.0_2.8.8.0__bebb3c8816410241/AlienwareAlienFXModelResources.dll
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.6.42.0 built by: NETFXREL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
System.Xaml
Assembly Version: 4.0.0.0
Win32 Version: 4.6.42.0 built by: NETFXREL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xaml/v4.0_4.0.0.0__b77a5c561934e089/System.Xaml.dll
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.6.42.0 built by: NETFXREL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
AlienLabs.CommandCenter.RemotingService.Domain
Assembly Version: 2.8.8.0
Win32 Version: 2.8.8.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienLabs.CommandCenter.RemotingService.Domain/v4.0_2.8.8.0__bebb3c8816410241/AlienLabs.CommandCenter.RemotingService.Domain.dll
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.6.42.0 built by: NETFXREL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.6.42.0 built by: NETFXREL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
System.Data.DataSetExtensions
Assembly Version: 4.0.0.0
Win32 Version: 4.6.42.0 built by: NETFXREL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Data.DataSetExtensions/v4.0_4.0.0.0__b77a5c561934e089/System.Data.DataSetExtensions.dll
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.6.42.0 built by: NETFXREL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Hi Arbla,
Were you running any application or third party service in 10041 build?
For a clean installation, I do not receive any similar error information, I suggest your perform a Diagnostic startup which starts Windows with basic services and drivers only,
to check if this issue would be reproduced.
You can open Msconfig.exe to access System Configuration.
For your reference which works in Windows 10 as well:
http://windows.microsoft.com/en-in/windows/using-system-configuration#1TC=windows-8
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]

Similar Messages

VSphere Client SSL error build 10041

So I'm seeing an odd error after upgrading to build 10041 (from 9926). The vSphere client (both 5.1 and 5.5) will no longer connect to my vCenter instance. I receive the following error
"vSphere Client could not connect to "<server>" An unknown connection error occured. (The request failed due to an SSL error. (The request was aborted: Could not create SSL/TLS secure channel.))"
Checking the event log I see Schannel 36888 errors with the following message: "A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 40. The Windows
SChannel error state is 813."
I managed to find out that error 40 means "handshake_failure". The error state (813) I haven't been able to find additional information on.
When I look at the vpxd.log file I see the following log lines which seems to confirm its a handshake error.
2015-04-02T13:26:08.442-05:00 [07548 error 'Default'] SSLStreamImpl::DoServerHandshake for SSL(TCPStreamWin32(socket=TCP(fd=38244) local=xxx:443, peer=yyy:64839)): SSL_accept failed with BIO Error
2015-04-02T13:26:08.442-05:00 [07548 warning 'ProxySvc'] SSL Handshake failed for stream TCPStreamWin32(socket=TCP(fd=38244) local=xxx:443, peer=yyy:64839), error: class Vmacore::Ssl::SSLException(SSL Exception: BIO Error)
Does anyone know if there were any changes around Schannel that would be causing a handshake error? I can't seem to find any additional information. It looks like vCenter accepts TLS 1.0, which in IE at least is enabled.

Hi Jeff,
I think we'd better involve the VMware side to further look at this issue.
For Windows 10 build 10049, you might need to notice the information below:
No access to Internet Protocol (v4 or v6) in 10049
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]

Update Operation Fatal Error when installing Technical Preview Build 10041 Upgrade

I posted this in the Microsoft Community forums and was redirected here.
Below is the original post (URL: http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/update-operation-fatal-error-when-installing/6eaff1b9-0223-4357-afc8-884382590e82 )
Hello,
In trying to perform an upgrade install of the Windows 10 Technical Preview Build 10041 (as is the latest available for direct download as of my writing), I am running into a problem I cannot find mention of anywhere else on the web.
I fall into two categories with regards to this build: A) Product tester who actually needs to test application performance under Windows 10 on bare metal, B) Semi-crazy techie who loves using (usable) beta software as his primary environment ;)
so it is rather important to me that I get this working on my machine in some non-virtualized respect. I am reluctant to do a full/fresh install if installation problems are happening, because my Windows 8 product key has been f***ed up from the
start (likely some random database corruption) and I've had to utilize phone support to get around an "unknown error" the last two times I've had to use it. So, for fear of that key completely crapping out on me, I don't want to move to Win10 unless
I'm confident it will install and I can stick with it (for better or worse) through the end. Problems within the Preview after I install it I can deal with.
So, I first tried to install the Preview through the standard Windows Update method. The installer took about 7 hours (but from reading lots of internet discussions, stupidly long install times in that range seem to be a common problem with
this builds separate from it actually failing). During the reboot between the "Setting up Devices" (Or is it Setting up Drivers? I forget) and "Taking Care of a Few More Things" (Again, possibly paraphrased), for about a split second, underneath
the Windows logo and throbber, some error like this appeared:
Fatal Error Performing Update Operation # of ##: ERROR CODE
It only appeared for a fraction of a second, and I had no chance of reading the precise numbers or error.
However, the installer then seemed to continue, and went until the main circle was at 100%. As soon as 100% hit, however, the screen went black for something like 30min. Then, I briefly saw "Attempting to recover installation" before "Restoring
your previous version of Windows." And I was, quite impressively considering how far along that installer was, back in Windows 8.1 completely unharmed.
I tried again by burning an ISO and doing a disc upgrade install. I let that one run overnight and was asleep for the error, but I was back in Win8.1 in the morning, so I can only assume a similar thing happened there.
As for my system specs, I'm running on a MacBook Pro 9,1 under Boot Camp. I am upgrading from Windows 8.1.2 Pro with Media Center. I have found other online accounts of people quite successfully installing Windows 10 on Macs, so that isn't the issue.
Does anyone have any clue as to what this error might have been/be, and how I might fix it? Or at least have it on good authority that a fresh installation would be unaffected (meaning it's software-related)? If not, I can try installing to a VHD,
which would at least let me product test on bare metal, but wouldn't have the harddrive space to be my daily driver and would probably only get used occasionally.
Thanks in advance to anyone who can help!
So far, I have the yet-to-be-tried idea of a clean boot prior to installation.
If anyone here has any more specific ideas, lemme hear 'em.
Thanks!

To the individual who proposed this as an answer to my problem: It's not even applicable. I specifically stated that I was trying to avoid doing a clean installation (at least without knowing more about the problem at hand). An answer saying to do the thing
you're trying to avoid doing is not an answer. You can see my last reply for the current status of this issue. 6-8 hour blocks of time in which I can't use my computer (as is required to install build 10041) aren't super common for me, but I haven't abandoned
this thread. There have simply been no more updates. If your motivation as a mod was that you simply don't like there being unanswered threads on this forum, then perhaps you could attempt to contribute rather than arbitrarily marking the first reply as an
answer.
I will continue to update this thread as I try new things and get more information.
Thank you.

Errors "A media driver your computer needs is missing." or "Windows cannot install required files" upon attempting to install Windows 10 TP build 10041 64-bit

I'm attempting to install Windows 10 TP build 10041 [64-bit]
I am currently being prevented from installing by a "A media driver your computer needs is missing." error, which occurs fairly early in the process. I've interpreted further text in the message as a suggestion that it's a DVD, USB or some other
similar driver issue. However, as I've been able to attempt each install through booting from DVD and USB, I'm not convinced this is the issue.
I'm currently installing to a 128Gb SSD drive. I have installed Windows 10 TP on my laptop's SSD with no issues.
On a few occasions the installation has continue with the installation, and then failed at about 6% with the following error:
"Windows cannot install required files. Make sure all files required for installation are available, and restart the installation. Error code 0x8007045D". I have not removed the installation USB or DVD.
I did not have this issue when installing build 9841, so am currently assuming this is an issue with build 10041.
Apologies if this query has been posed before, a search did not show up this issue.
Any advice would be greatly appreciated.

Hi Michael,
Thanks for trying to assist!
I attempted removing/deleting partitions and formatting the SSD as part of the install process. I have also tried installing via USB and DVD with the same issues.
As part of the troubleshooting, I attempted to install a different OS. I was able to successfully install Linux Mint 17.1 with no issues. This further solidifies my impression this is an issue with Windows.
I will try a different USB port, appreciate the suggestion, didn't think it would make a different given the various methods already attempted.

Windows 10 TP Build 10041: fbl-impressive 10041 Enterprise is not be installed Error 0x80070241

I have running Win 10 Enterprise TP build 10041 and downloaded Windows Update fbl_impressive 10041 Enterprise.
The installation failed with the error message 0x80070241.
What is to do?
xb9$EF,3

Czer
Try updating from the ISO. Instructions for making one here
Wanikiya and Dyami--Team Zigzag

Windows 10 TP Build 10041

Hi Insiders
I have downloaded and installed build (10041) but when it boots to set up the settings it sits on 30% i have left my laptop on all night and still on 30%.
I shutdown and restored to 9926 now i have a error when updating 0x800705b4 i have searched and is has to do with the realtek semiconductor corp. update for realtek high definition audio.
but I see -fbl_impressive 10041 Professional in the update and i cant get it because of this error with Realtek

There is an article posted by John W [MSFT] in another forum. He is also a Microsoft employee.
One of the topics he wrote about was : Realtek driver installation timeout issue (error 0x800705b4)
He suggested a "workaround".
excerpt..............
Issues that should be fixed but didn't make it into Build 10041
Unfortunately we missed integrating these fixes into the Windows Insiders Build by
one day, however the fixes work in our testing and will be in the next build:
1. Realtek driver installation timeout issue (error 0x800705b4) - Excellent workaround here:
http://kb.stonegroup.co.uk/index.php?View=entry&EntryID=289
Note : the workaround involves registry editing. Be careful and follow the steps to the letter.
I don't know your computer skill level, if you are not comfortable doing registry editing, DON'T do it.

Problem with System Metrics SM_CXSIZEFRAME + SM_CXPADDEDBORDER in Windows 10 Preview (Build 10041)

Maybe this forum is the wrong place to ask something about Windows 10 Preview, but I did not find a dedicated place to report
programming problems as opposed to user problems:
I program/maintain a 32-bit desktop (WIN32 API) application and try it now on Windows 10 Preview build 10041. I calculate the size of a window border with the help of the GetSystemMetrics function, using the constants SM_CXSIZEFRAME and SM_CXPADDEDBORDER.
Originally, I only used SM_CXSIZEFRAME. This returned 4 pixels instead of the expected 8 pixels that I got on all previous windows versions up to Windows 8.1. Then I learned that already since Windows Vista one is expected to add the value of SM_CXPADDEDBORDER
to get the full border size. (SM_CXSIZEFRAME alone only continued to work on Vista and beyond thanks to a little compatibility hack by Microsoft, with SM_CXSIZEFRAME still returning the full border size and SM_CXPADDEDBORDER returning
yet 0, at least for 32-bit programs like mine.)
Assuming that Microsoft finally switched off that compatibility measure on Windows 10 I query and add SM_CXPADDEDBORDER now as well. Unfortunately this does not solve my problem, as that system metric returns 0.
Just to be on the sure side, I declared my program to support Windows 10 by using an embedded manifest and using the corresponding <compatibility> / <supportedOS> line with the Windows 10 GUID - this did not help either.
As querying and adding those two system metric values is rather trivial (no need to include code in this question, I think), I don't have the slightest idea what
I could do wrong here, this looks like Preview bug affecting 32-bit programs to me...

I regret to inform you, that you have to live with this error for ever. Microsoft won't fix it... we reported an error of the Windows Error Reporting system (exists since Windows 8) and provided a reproduction (an application with one printed page of code,
so very small and easy). It has never been fixed. 3 developers at Microsoft are involved and they confirmed, that it's a bug ... but... no chance. It's a strange company... I don't know what they mean with "we listen to our customers".
PS: ja, nöd grad hilfriich mini Kommentär, aber die Type triibed eim eifach in Wahnsinn!! ... schinbar nöd nur öschtlich vo Bade, sondern au weschtlich
Rudolf

Window 10 build 10041 does not work with Intel 82579V Gigabit Ethernet on ASUS motherboard

I originally posted this question here:
answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_update/window-10-build-10041-does-not-work-with-intel/6729892f-83aa-4822-b20a-ea84f4fd06c7
and was asked to post it on this forum...
I updated a computer I have which is a quad core i7 that I built and includes an ASUS motherboard with Intel 82579V Gigabit Ethernet built in. Windows 10 preview 9926 worked fine with this network adapter. Window 10 build 10041 does not, and I have tried
it twice so far. I even went as far as buying a Thunderbolt-Gigabit Ethernet Adapter (Broadcom, sold by Apple)... and while it installed the driver automatically, it did not work either. Each time you try to view the properties of either of them, it locks
up or give an error. In fact, doing much of anything with the Intel adapter icon assures you of not being able to do a clean reboot... have to kill power. I have finally gone back the previous version 9926, which has its issues but no where near as bad
as not having any network connectivity! Does anyone have this issue and a workaround?
Note, there are two images on the windows 10 preview forum that I posted this question on. I could not post the full link as I was getting a message here that links and graphics are not allowed.

Thanks Roger, I posted the following yesterday in the other thread (thinking it was this thread - confusing after they moved it here)... It may be that the new driver fixes the issue that 10041 has with it, but I have not tried that yet. If I do I will update
this... Thanks!
I have more information about this, which basically exonerates any issue with the Intel 82579V Gigabit Ethernet hardware or software. I have 3 computers with Windows 10 preview so I have multiple angles to see issues from. With this I have found a culprit
(but I suspect not just the only culprit) in this above mentioned problem...
10041 build combined with installing (or attempting to install) CISCO VPN Windows 7 64bit 5.0.07.0440-k9 client causes the issue mentioned above. I confirmed this on a completely different machine with a totally different Ethernet adapter. First machine
is an ASUS motherboard in a tower system I built, with the Intel 82579V Gigabit Ethernet hardware built in. Second machine is a Gateway Laptop from 2008 which has a Marvell Yukon 88E8057 PCI-E Gigabit adapter built in. Build 10041 will work fine with my 2008
laptop, including the MS VPN client (which I have tested). However, if you attempt to install or even uninstall the Cisco client you will have to do a recovery to a restore point (as I have done twice) in order to get your network working again. Installing
or attempting to install (because it never even does install properly and times out), CISCO VPN client will render your entire network unusable. Going back to a restore point saved me and I am still running 10041 but I can't use CISCO VPN client any longer.
I could with build 9926, including on all 3 machines. I now have 9926 on two machines and 10041 on only the 2008 laptop.
Hopefully this above information helps someone resolve the issue. I will also mention, even though my network is working on the 2008 laptop, I still can't go into the Control Panel\Network and Internet\Network Connections and right mouse click on the Marvell
Yukon 88E8057 PCI-E Gigabit adapter icon. I get an error when clicking on Properties menu popup : "An unexpected error has occurred". So something is still up with my network adapter driver or windows software, but it could be a side effect of all
that has happened with the Cisco software install attempts under 10041.
Another note: CISCO Anyconnect also has the issue.

No Password entry option Windows 10 build 10041 (and 10049) unable to log in

Hello. I upgraded using the automatic process from within Windows 7 home premium. I'm using an All-in-one machine with 4gb RAM and 3.10ghz Core i3.
Initially I had a local account with no password, which automatically logged me in from start up. Everything ran smooth and well. I switched to a microsoft account which requires a password, in order to install apps from the Metro store.
I shutdown overnight, and return the next morning, and I'm faced with the usual screen. A large image, few icons. I swipe upwards on screen or press space to move along and log in. My username is presented to me, but the password input field is missing.
It says "Andrew" and has my email beneath it, but the password box is just not there. I clicked the screen randomly but nothing showed up. I've tried typing anyway but still nothing.
This left me comlpletely unable to sign in and use windows. In dire need of a PC to use, I activated a workaround which allowed me to use cmd without logging in and used the /active command on the hidden administrator. This is the only accessible use of
my PC I've got, and my files are buried deep within C:/users/..... and so on.
As per the title, I also had this issue in build 10049 but I had to revert back since I locked the PC using window+L out of habit, and I couldn't log back in. I reverted back to 10041 since having restarted the PC from being locked out, I encountered
boot loop.

Andrew754,
Are you saying that you are now in build 10041, and that you are unable to login because there is no option to enter the password ?
If yes, have you tried...... press Ctrl + Alt + Delete keys ?
Will that bring you back to normal sign in screen ?

Civilization V stopped working after installing build 10041

After installing build 10041, civilization V crashes when loading a game.
This worked perfectly just before the installation and fails after.
anybody else experiencing this issue? Any solutions?
My guess is that it is a directx issue but I can't be sure.
Just to prevent the questions being asked, it is a 100% legit version of Civilization installed over steam.
I tried reinstalling directx and reinstalling CIV V. Both failed. Drivers updated. Also failed.
Gal Ben Yair

Please provide us with your Event Viewer administrative logs by following these steps:
Click Start Menu
Type eventvwr into Search programs and files (do not hit enter)
Right click eventvwr.exe and click Run as administrator
Expand Custom Views
Click Administrative Events
Right click Administrative Events
Save all Events in Custom View As...
Save them in a folder where you will remember which folder and save as Errors.evtx
Go to where you saved Errors.evtx
Right click Errors.evtx -> send to -> compressed (zipped) folder
Upload the .zip file to Onedrive or a file sharing service and put a link to it in your next post
If you have updated to win 8.1 and you get the error message "the system cannot find the file specified" it is a known problem.
The work around is to edit the registry. If you are not comfortable doing this DONT. If you are, backup the key before you do
Press Win+"R" and input regedit
Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels. Delete "Microsoft-Windows-DxpTaskRingtone/Analytic"
Wanikiya and Dyami--Team Zigzag

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.

Enabled Hyper-V causes "System thread exception not handled" BSOD in builds 10041 and 10049

I had a Windows 10 TP build 9926 installation with Visual Studio 2013 Community Edition installed, when build 10041 was released Windows Update tried to install it but after restart it got BSOD with "System thread exception not handled" text and
reverted back to 9926 with error code 0xC1900101-0x40017. I tried update from ISO, got the same BSOD. Tried clean installation, it worked.
I decided to install software and restart the system after each installation and discovered that installing Visual Studio 2015 CTP6 caused BSOD after restart if and only if emulators were included. Installation of Visual Studio 2015 CTP6 without emulators
and then installation of Tools for Windows 10 also caused BSOD with "System thread exception not handled" error after restart.
So I thought that it was Hyper-V related and disabled hardware virtualisation in BIOS settings. It worked, system successfully booted, but, of course, Tools for Windows 10 setup showed up and told me about fail in UAP for Windows Phone package.
So, my hardware is Gigabyte GA-A75N-USB3 motherboard with AMD A8-3870 APU with integrated graphics, Intel SSDSA2CW080G3 80GB SSD and 8 GB RAM.
Steps to reproduce are to enable "Virtualisation" item in BIOS settings, install Windows 10 Technology Preview Build 10041, install Visual Studio 2015 CTP6, install Visual Studio Tools for Windows 10 Preview, restart the system and
see blue screen with white text of description of "System thread exception not handled" error.

Same issue, MSI A75MA-G55 AMD Fusion Socket FM1 with A8-3850 APU, 16GB RAM. Hyper-V worked in 9926, but broke in 10041 and remains broken in 10049. I have found that if you get in this BSOD loop, you can boot to Safe Mode and Un-install Hyper-V
to recover. 10041 was an update to 9926, and 10049 was a clean install.

Dell Bluetooth 365 not detected in Windows 10 Technical Preview (Builds 10041 and 10049)

When I installed Windows 10 build 10041 on my 2009 Dell Inspiron 1545 laptop my Bluetooth 365 stopped working. On investigation I saw that Bluetooth had disappeared from Device Manager completely, but no yellow '!' was apparent anywhere. When I checked the BIOS the Bluetooth card was present. I researched the issue for a couple of hours and realised that Dell did not have a Bluetooth 365 driver for anything later than Windows 7. (That Windows 7 driver had worked in Win 8/Win 8.1). I discovered that the card is made by Broadcomm and is also used by Lenovo in some of its laptops. I downloaded the following driver from Lenovo's support site and installed it. When prompted, click the 'update software' button, and a further installation will run. If you wish, have Device Manager open and you will see the drivers and devices install.
support.lenovo.com/.../ds031759
It worked perfectly and my Bluetooth card was detected and configured and now all my Bluetooth devices work with Windows 10.
The Dell 1545 with Bluetooth is a great workhorse PC and it would have been a shame if it could not have been used with Windows 10. I hope it is not a sign of forced obsolescence by Dell, and that they will release Win 10 drivers for this venerable old laptop. It is a shame to have to go to a competitor for a driver. Judging by my web research there are many of this model still in everyday use. I trust this will be of use to other users.

There is a universal Broadcom Bluetooth Update which would cover this also:
http://www.broadcom.com/support/bluetooth/update.php

Dell XPS Touchpad Driver No Longer Working in Build 10041. Was fine with Build 9926

First of this is an old Dell, but from Vista through to Windows 8.1 Update, and then the initial Windows 10 Tech Preview Builds the Mouse Drivers have been OK. Its not so much the core mouse driver, but the feature extensions in the Accompanying driver bundle
that have stopped working. i.e. the ability to control finger scrolling and tapping, etc.
The Dell supplied drivers for my laptop (XPS M1330) ended with Windows 7 32bit, However, newer Dell laptop models had compatible, fully functioning drivers that could be installed. That was until build 10041.
So my questions are:
1. Anyone found a compatible driver for a Dell XPS with the Alps/Synaptics Touchpad model?
2. If MS Staffers read this, I understand that the model for Windows 10 is... "if it worked in an earlier Windows it will work in Windows 10", so, is this likely to be fixed?
Other than this issue, which is very irritating because working with a very limited mouse is a pain when the mouse supports other touch features, my Windows 10 experience has been really good.
Cheers,
Pete

Hi Alex,
I found a semi-compatible driver for the Synaptics Touchpad, which is found searching for Dell KB R293038.exe
This driver provides basic two finger touchpad scroll support and chiral scroll. It doesn't support advance Windows 8/8.1/10 swipe features.
Importantly this driver does not support two finger/chiral scroll gestures in Windows Modern Apps like the Store, or Project Spartan, or any other Windows Modern Apps.
Hopefully the Windows 10 Tech Preview Team will be able to work out what they changed that broke the Synaptics Touchpad gestures for so many people posting about the issue on these forums.
Cheers,
Pete

Windows 10 build 10041 32bit crashed hp envy x2 tablet/notebook black screen

Hello all,
Upgraded from Win 8 to 8.1 the 10 preview build 10041 (32bit), online upgrade (as machine will not boot from usb), worked well for one day. Then I changed update option from 'only notify me of available updates' to 'automatically install updates for windows' or somesuch.
For two days, can only get black screen using all combinations of shift/ctrl/fn/windows key with f2/f8/f9/f10/f11 keys.
Holding the power button down for brief or long period. With mains power lead inserted or not. With tablet connected to base or not. Ran down the battery, no change.
I suspect the problem is due to the Win 10 O/S is perceived as an alien O/S by the system. Prior to updating to Win 10, I was unable to boot from usb or access legacy boot.
My machine:
HP envy x2 pc
product number c8c42pa#abg
serial number 4cn2480dgk
Bios was updated from f12 to f13.
Thanks in advance, AA

Hi,
Did you read the following Agreement before installing Windows 10 preview ?
https://insider.windows.com/Home/TermsOfUse
Specially section 4.
Regards.
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

Shutdown Error Build 10041

Similar Messages

Maybe you are looking for