Windows 10 preview build 10049 BIG PROBLEM

hello,
i got a very big problem after updating to build 10049. after the installation was complete my laptop restarted and i got a black screen with in the botom right corner the build number 10049. after a couple of hours the laptop restarts itself but it keeps
getting on this black screen.
i tried a iso of windows 10 preview latest iso build on a usb stick but with every solution i try: format, repair it keeps getting the same error that there is a problem with unmountable bootdevice.
even using my official windows 8 dvd gets the same problem
i'm lost. i dont know how to solve this problem.
can someone please help me with this?

This is not a one off, it is repeatable on brand new disks.
I previously had the original win10 preview build installed on this hard drive = no problems.
I then did a fresh install of build 9879 from CD. Install completed untill it got to the reboot phase = it would not reboot - the hard drive was not recognized in the bios anymore.
tested broken hard drive in another computer = works
tested broken hard drive in 2nd connector on my laptop = fail (still not seen by bios).
tested a few other sata disks I have laying around on both connectors of my laptop = pass.
upgrade my bios as there is one version higher than I had. = fail (still not seen by bios).
boot from broken hard drive on another computer and finish the OOB portion of the win 10 preview install = pass
So it seems clear that the hard drive is still working, but just not recognized on the original computer. It is only 2 months old so I get it replaced under warranty. Replacement disk is recognized by bios, yeah! I then restore image of broken hard drive
to this replacement. Disk is still recognized by bios. I boot up from this disk on my laptop. It works OK until first reboot, then is not recognized by bios anymore.
Computer = Toshiba Satelite P305 PSPC8U-01400Q
Hard disk = WD blue 1TB model: WD10JPVX-22JC3T0
Note: also with windows 8 running on this computer and the broken hard drive installed in second connector, windows also does not see it, neither through disk manager nor through diskpart command line. But if I boot up in Linux from a bootable USB flash
drive, then I can see the (broken disk) on this same computer. Yes I can see it and I can read and write to the filesystem, even though it is still not seen by the bios.
HI
Disable PUIS (Power-Up In Standby) with HDAT2.EXE With PenDrive BOOT MS-DOS

Similar Messages

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

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

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

Windows Preview Build Settings Missing/Unavailable from Build 10049

The Preview Build settings has been missing from 10049. I have tried doing Windows Update registry change to enable that option in the Windows Update through settings and also through the control panel but still no success. Please tell me how can i look
upto that?

The Windows Registry version trick doesnt work in build 10049 and after runnning the registry script also there is no windows update option available. You cant just manually select updates to install. Its really a tough job updating your computer.
Moreover, the concept of fast rings and slow rings when a product is under development is useless as the latest updates should be processed simultaneously for everyone and the users should be allowed to download the ISO of the latest builds released on fast
rings via windows update. The windows update mechanisms should be changed.

Problems in Windows 10 Technical Preview build 10049

Start menu not working
Cortana not working
can not use apps
What are the solution for these problems?
M I the only one who is facing these problems??

Hi Alex;
I now have what seems to be the answer. After being frustrated with all the answers I've seen here and on the web. I came across something else. It was a knowledge base article for windows 8 and 8.1 # kb2798317.
After checking all the permissions it seemed the group ALL APPLICATION PACKAGES was no where to be found on those directories and I remember that early in the process of trying to get the powershell scripts to work I needed to change the
settings in WindowsApps so I could see everything(yes I'm an admin but that didn't matter)
That group was not on the access list. Only Trustedinstaller?????????? Anyway after adding the new group in that and program files and windows like the article said. I rebooted the machine and after several attempts at each ALL THE APPS ARE
RUNNING! Even Cortana woke up and the Windows update screen works. I was able to get into and run the Beta Store (finally able to downloaded new Music and Video) and the Feedback Tool is working as well.
I just need to log in as the other user I created and see what happens there...
Thx
Happy Camper :-)

Error upgrading windows 10 build 10049 from 10041 error 0x80070012

i don't know how i can fix this error. i got the same error when trying to fix the store beta issue with mail, calendar and people apps.
ps sorry for my English.

Follow this method which is posted in Insider Hub :
In this build, the Mail, Calendar, and People apps may be broken due to a licensing issue with the Store Beta. To get these apps working again, you need to follow these steps:
Open powershell as administrator
Run the command Get-appxprovisionedpackage –online | where-object {$_.packagename –like “*windowscommunicationsapps*”} | remove-appxprovisionedpackage –online
Re-install Mail, People and Calendar from the Store (green tile)

Problem with build 10049

My notebook installed the latest update windows 10 preview build 10049. When it was installed, every time after the startscreen the screen turns blue and the notebook restarts. On the screen was a message it had problems with the ??.sys file. After installing
backwards the 10041 Build i can not see an update to the 10049 build anymore. Can someone help me?

Hi,
Yes, pleaes make sure to change to to "Fast", if still no help, then please check the registry, make sure its value shown as below:
Open regedit.exe
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability
Ensure the following values exist:
{value name}, {value type}, {value data}
BranchName, REG_SZ, fbl_impressive
ThresholdOptedin, REG_DWORD, 1
ThresholdRiskLevel, REG_SZ, low
Delete all other values
Open Settings > Update & recovery > Windows Update
Tap or click Check for updates
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]

Hotfix KB 3053898 for using Hyper-V in Build 10049

Go to Windows Update and install KB3053898.
support.microsoft.com/kb/3053898
The hotfix is to resolve the issue of " You cannot enable Hyper-V after performing a clean install of Windows 10 Technical Preview Build 10049, nor after upgrading to Build 10049 from a build that did not have Hyper-V enabled."

Hi David,
My Dell 8 inch tablet is stuck at 98% downloading this update for the last few days. Can you help me understand how I can either push this to 100% and let it install, or else stop the update? I don't think I can move to the latest version of Windows
10 without fixing the problem with this update first.
Thanks,
Vincent

Windows10 tech preview build 10041 doesn't get updated for some reason

is there a way to force an update? I believe there were a couple of updates , but for some reason my build didn't get updated
tx,
D

Hi,
At least, we have preview build 10049 now, if you want to experience it, then you can change the install speed to "fast" in Settings\Update&Recovery\Windows Update\Advanced Options. If you don't want to experience it, then leave the setting
in "Slow". If you've already set to fast and didn't get any updates, then pleaes check the following registry:
Open regedit.exe
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability
Ensure the following values exist:
{value name}, {value type}, {value data}
BranchName, REG_SZ, fbl_impressive
ThresholdOptedin, REG_DWORD, 1
ThresholdRiskLevel, REG_SZ, low
Delete all other values
Open Settings
> Update & recovery > Windows Update
Tap or click Check
for updates
System also has a built-in troubleshooter, launch control panel\All control panel items\Troubleshooting\System and Security\Windows Update, run this troubleshooter.
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]

Big Problems in Email in Full Screen Mode

Just came across a big problem. When Email is in full screen mode, new emails and replies don't have customizable toolbars. I need access to my Address Book icon because it has groups that I often forward emails to. In regular mode, I have customized the toolbar via the View Menu to include the Address Book icon (plus added lots of other icons). In full screen mode, all the extra icons are not available.
Also, in Full Screen Mail, you can't move the new/reply email window -- which is a big problem if you want to view to the email underneath.

I tried, but the feedback page (Mail Menu/Provide Mail Feedback) does not allow typing comments. By default, infomation about my Mail Setup is included, but I cannot add a comment.

VPN doesn't work at build 10049

VPN has worked at previous builds but not anymore at build 10049.
When I choose VPN-network provider whole Settings-windows shuts down.

Hi fiantsirk，
There have been some known issues in Windows 10 build 10049:
No access to Internet Protocol (v4 or v6) in 10049
VPN configurations might be affected, folks here have found out some ways to make it work (3rd-party software related), you may check at :
https://social.technet.microsoft.com/Forums/en-US/261392a2-3914-4518-acb4-065a0a635f58/build-10049-breaks-openvpn-there-are-no-tapwindows-adapters-on-this-system?forum=WinPreview2014General
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]

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

Problem installing Windows Technical Preview build 9926

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

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

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

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

Failed to Install The New Preview Build. Installation Failure: Windows failed to install the following update with error 0x80246007: FBL_AWESOME1501 9926 Professional.

Hello,
I'm having issues upgrading my Windows 10 Technical Preview installation build 9879 to a newer build that's become available late January 23rd.
I am installing the new upgrade in a Hyper-V virtual machine and get the following error:
Failed to install the new preview build, please try again later. 0x80246007
What could be the problem?
Previously I've had messages that Windows cannot be upgraded on a computer with less than 2 Gbyte of RAM. That's a Hyper-V VM with dynamic memory and I was highly surprised to see this error; never had this before. Had to set 2048 Mbytes as a minimum memory
for this VM. Now that I have this 80246007 error code.
When looking up System log, the following error messages are listed multiple times:
Installation Failure: Windows failed to install the following update with error 0x80246007: FBL_AWESOME1501 9926 Professional.
The errors are returned for the Event ID 20 by WindowsUpdateClient
in task category Windows Update Agent..
I reviewed the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability
registry key as suggested in Windows
Insider stuck on build 9841 - "No new preview build was found", and here is what it shows:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability]
"BranchName"="fbl_awesome1501"
"ThresholdRiskLevel"="low"
"ThresholdOptedin"=dword:00000001
Note, when attempting to install the downloaded update from a native boot, installation starts with no errors.
However, since setup is not supported for a natively booted VHD files, it does not proceed further showing a message that installation on virtual drives is not supported.
Looks like Setup is having problems installing in a Hyper-V virtual machine.
Possibly, some ESD files got corrupted during downloading? Is it possible to remove them and re-download missing files? (I, however, noticed that Windows seems to re-download upgrade files after you restart 9879 and attempt to check for a new build.
Any clue why installing under VM causes 9926 to fail?
Thank you in advance.
Well this is the world we live in And these are the hands we're given...

Hi,
According to the error message, this problem seems like update package installation failed during system upgrade.
You can try to remove ESD file which locate at boot of C drive and upgrade the system again for test.
On the other hand, make sure the system 9879 installed all Windows pushed updates before system upgrade.
Roger Lu
TechNet Community Support

Windows 10 preview build 10049 BIG PROBLEM

Similar Messages

Maybe you are looking for