I upgraded ok with the update and successfully activated windows 10. I downloaded both 32bit and 64bit to usb using media creation tool as I wanted to clean install Windows 10 64bit on my 64bit compatible machine although am currently running 32bit windows 7 as that's what I had to hand when I built the PC. If I attempt to boot 32bit from usb it returns the error winload.efi missing. If I attempt to boot the 64bit version it just returns to windows boot manager.
Frustrated, I opted for the "reset this PC" function in settings instead as an alternative to the clean install and the reset failed, hung, then returned to the screen "what would you like to do". Once I selected "turn off PC" and it restarted and automatically continued the reset only to fail a second time. This time I choose to "return to windows 10" but it just hung. I had to rollback to windows 7 with repair dvd.
With windows 7 now installed again, I still cannot boot from either the 32 or 64 bit option in windows boot manager when I select to boot from the USB.It either returns to the boot manager or returns the winload.efi missing error.I have tried changing settings in bios to disable secure boot and fast boot but it makes no difference. I've read the Andre da Costa (sp?) wiki steps along with countless other how-to-clean-install windows 10 guides.
After upgrade Dell Inspiron 580 to win 10 the system boot option F12 seems disabled and the box will not boot from the alternate drives (cd then USB) enabled on the motherboard. F2 still brings up the system motherboard edit.
The failure to boot from cd defeats my drive imaging backup software.
I am unable to find a secure boot option on the motherboard, so I suspect the issue is something else.
Not much on the web about this failure. Some threads talk about disconnecting all USB and devices so you just have the core system...really? Should I call MS about this? I'm sure they are flooded with probs.
Attempting to upgrade to Win 10 I get through the entire process only to have it fail at the end and it gives this error code 80073B92-20009. This is going from Win 7.
I recently upgraded a Toshiba A300 laptop (2009 model) from Win7 to Win10. I use a 125GB Kingston SSD as primary and a 280GB Hitachi as a secondary internal hard disk, in place of DVD drive, inside a cradle. This is a single OS installation, no dual boot. When I cold boot (from power on) and after the Bios logo, the "MBR Error 1" appears on screen and stops booting. To bypass I do a warm restart (Ctrl+Alt+Del) and the second (warm) boot loads Win 10. Also booting is ok from a Restart. Again error message appears only after a cold boot.
As a teaser I have to mention that, whenever I remove the cradle with the secondary Hitachi hard disk, the error does not appear during cold boot !!!. That is the error message appears only if the second hard disk is installed. This is an annoying situation only and does not affect any other operation, except booting.
Yesterday I removed dual booting Linux and after that my Windows 10 won't boot up. I have tried everything. The cmd commands: bootrec /FixMbr; bootrec /FixBoot; bootrec /RebuildBcd; Bcdboot commands and everything. Then I tried Refreshing PC what says: Drive where Windows is installed is locked. Please unlock it.....
Startup repair just scans for a short period and then says: Couldn't fix the problem. I can't Access normal Recovery options, so I'm using a recovery flash drive. I have tried several Live CDs but none of them won't fix the problem. I can access the UEFI Bios, but idk what to change there. I don't want to fresh install Windows, unless it's the only option, because it contains important data.
I installed Windows 10 earlier but after about 10 minutes of using it my computer restarted itself automatically, and then it showed an error message saying that windows had "ran into a problem" on restart an it quotes the error code "0xc000007b".
I have taken a photo of it which can be seen here: [URL] ....
It then restarts again and gives me a list of options: [URL] ....
I am working on creating a new master image to deploy windows 10 64 to a new of different models throughout our organization. Currently I am having difficulties getting the drivers to be "auto Detected"
The Sysprep command I am using is : sysprep /generalize /oobe /shutdown /unattend:C:windowssystem32sysprep10answer.xml
When the PC boots after being sysprep it does not detect and install the drivers.
I have loaded the uncompressed drivers to C:windowsINF and created a folder called drivers. I set the permissions for pretty much anyone to have full control. If I manually point the driver install wizard to that folder they all install correctly. This previously worked in 7 32 bit without any thought.
I tried adding the driver path to Pass 2 and 5 in my answer file without any change.
I'm using windows 8.1 on ASUS N series laptop 64 bit, my windows got problem and after i updated to windows 10 and try to factory reset it, it got to 99% and say that the window has a problem, it cannot reset my windows and stuck in restart loops.
I've spam F9 and try to reset the pc again, but the problem still persist and i even try to solve it with the advanced options ( startup repair, system restore, system image recovery setting - all end up with this pc require administration account, and somehow my account is lost due to reset earlier) i even try to reinstall windows with CD but it doesn't detected.
It seems like i lost both my windows 8 and windows 10 on the laptop.
Inserted my new SSD to a SATA3 port and, next to my HDD 1TB, and went for a clean install right away. The system installed without problems (wiht the old HDD still attached), then i booted up the system (was a bit weird, because two versions were showing, however i formatted the old windows partition) and installed my programs. I saw that a 110 MB of data were still sitting on my old partition where the Windows 10 was earlier. Tried to delete those files but could not. However I shut down my pc and wanted to boot up again. Then it showed me a screen with "select proper boot device or restart computer". I went to BIOS to see if my SSD was set to primary boot device, but it was. But when i manaully select the boot device, my SSD, after starting up the computer, it boots into Windows and is running normally.
Can it be that there is no boot partition on my SSD and it wants to use the boot files from the HDD?? I also tried to unplug the HDD and boot up, but the same massage was showing up. But when i select the boot device manually it works.
I have a dual boot system in the following configuration:
HDD-0 = Win7 OS, HDD-1 = Win7 OS, WinXP OS. I have successfully booted into each of these operating systems - and the Win7 OS on HDD-1 is an exact clone of the primary OS on HDD-0.
I just upgraded the Win7 OS on HDD-0 to Windows 10 using the "Get Windows 10" process. I now get the new blue Boot Manger screen with all three OS's listed and I can successfully boot into Windows 10 and Windows XP. But I cannot boot into the Win7 OS on HDD-1 (which I could before the Windows 10 upgrade). How the upgrade even knew about the other copy of Windows 7, since it was not active and lives on another HDD is beyond me.
One strange thing - if I do a cold startup (power on) I get the new Boot Manger screen. But if I do a Restart from Windows 10, I get the old, black & white boot manger screen - and it does list all three OS's correctly, too.
The error message I get when trying to open (boot) the Windows 7 OS is: "LogonUI.exc - Entry point not found. RtlReleasePath could not be located in the ntdll.dll" And, like others, I now get the black screen with "Windows 7, Build 7601 This copy of Windows is not genuine (but it was yesterday before the Windows 10 upgrade on the other HDD).
And like others, I can start the Crtl+Alt+Del to get the screen with users, Task Manger, etc. And, I can run all my applications by manually starting them in a New Task and browsing to the exe file - like Firefox.exe or Word.exe So, it looks like Windows 7 started and may be running. I just can't get into it.
I think both issues, the LogOn and the "Not Genuine" are both related to the Entry Point no located in the ntdll.dll.
At this point I really don't want to reload Windows 7 since it appears to be running and all the apps can be run manually.
All this happened after the upgrade of the other Win7 on HDD-0.
Still trying to update to windows 10. Have updated windows 7 w/sp1 and have checked that my computer is ready for update 10. Everything goes great until final shut-down and restart.Then I get black screen with Blue Flag and locks up, will not go any further. After 5 hours of waiting tried turning off and it restarted and gave this error message: Instalation failed in the safe OS phase with error during Boot. 0xC1900101-0x20017
So far neither will Microsoft Camera HD3000 or Samsung Magican Rapid Mode operate within my Windows 10 Pro installation. It seems that there is no compatible software or drivers yet available for these apps.
The camera displays an image on the screen but will not snap a photo or do a video.
Magician does list many of the normal functions but shows a red X along side OS thus not allowing rapid mode to be executed for a primary SSD.
In my desktop I have two hard disks ( disk 0 and disk 1 ) . Disk 1 is a clone of disk 0 created by Macrium Reflect Disk 0 : ( C: ) windows 10 pro , upgrade from windows 7 , ( E: ) windows 8.1 pro , ( G: ) Storage partition Disk 1 : clone of disk 0
problem description : I see in msconfig / boot a wrong listing
windows 10 ( C:WINDOWS) : Current OS ; Default OS
windows 8.1 pro ( H:WINDOWS ) instead of ( E:WINDOWS )
Nevertheless the dual booting works fine as well as the shift between the disks via BIOS.
The question is , could I fix the situation using the EasyBCD of Neosmart Technologies to edit the bootloader ?
I see can change drive letter H: to E: and save the change , am I right or wrong ? or any other way ....
My laptop has dual boot - Windows 7 and Windows 10. My Win7 environment is my main working environment with lots of programs installed and important files. I installed the Win10 environment just to play around with 10 during the technical preview. Now, I would like to disable the 10 environment and upgrade the 7 to 10. Am I able to do this, or have I already "used up" my one upgrade on this computer's Windows license?
I notice that in Windows 7 I have not received the icon in the notification area that invites me to upgrade to 10. This makes me think I might have used up my chance to upgrade.
My end goal is to have a single Windows 10 environment. Note that the reason I want to upgrade my 7 environment to 10 is because I don't want to have to re-install all of my programs and files into the current 10 environment.
As I get ready to do a clean install of 10074 I am curious about the need to disable secure boot and fast boot options. If I do disable secure boot do I need to enable legacy boot?I have had limited success with previous installs to a 2nd hard drive and the problems that arose always seem related to dual booting.
In one instance I did a clean install of 10061 and had left secure boot enabled. In order to get dual boot working I had to disable secure boot, and upon rebooting I needed to change it back to secure. I then made Win 8.1 the default boot and then Win 10 would never boot from the menu, it would just take me back to the boot menu and I could boot into Win 8.1.
I'm making a image for installation of windows 10. I make a USB flash drive with WINPE. and once the device starts into WINPE, it will automatically start to install windows 10 by calling "dism /apply-image". Normally i just shutdown the computer after installation, but now i want to reboot the device and boot into the windows i just installed. But i can't, because if i reboot the device, it will boot into WINPE again and start another turn of installation of windows. How could i temporary boot into my windows 10?
After several weeks of testing I'm ready to go full on Windows 10 and want to get rid of Windows 7 but I have some partitioning issues I want to clean up. I currently have Windows 7 on drive 0 (360 GB) and Windows 10 on drive 1 (500 GB). Both are SATA drives and RAID is enabled in the bios but not active.
What I think I'd like to do is simply swap the drives physically so that Drive 0 has my current Windows 10 install on it and make it primary boot active etc. The drive with Windows 7 on it would become drive 1 and I would delete the Windows 7 partition and re-partition it with a clean empty partition just for extra space.
Second question, any advantage to using this drive configuration in a RAID setup?
I have a legacy 64 bit dual core desktop (ASUS mobo). I have several Sata hard drives in it with the 4th partition of my 1 Terabyte drive containing my Windows 10 Professional boot OS. After converting another similar legacy machine to a NAS device I took the old Windows 10 32 bit OS drive from it and tried booting the ASUS machine with it. Needless to say, the OS didn't like it and reverted to Windows 10 Pro Insider Preview edition (build 11082).
When I tried to restore the boot drive to the original one for this machine the master boot was missing.
I had just formatted another partition on the same drive that had contained a Windows7 installation that had failed. This partition may have contained the master boot record. So I booted to a command prompt from a USB drive and successfully ran the following commands:
bootrec /RebuildBcdbootrec /fixMbr bootrec /fixboot bootsect /nt60 SYSbootsect /nt60 all
After that the BIOS just says "An operating system wasn't found. Try disconnecting any drives that don't contain an operating system" This disk and OS are on the original machine it used to run on. As I understand it, Windows 10 tries to record it's key to somewhere in the BIOS. But the BIOS on these old machines don't provide such a facility. I don't understand what Windows 10 OS does with the key in this instance. If it was recorded in the BIOS then I'd presume that the other Windows 10 drive I attempted to use would have found it and used it. Or perhaps not, since it didn't like the new environment.
what I'm looking for is a way to get my original Windows 10 to boot again on the same machine it had always work on before, from the 4th partition of the 1 terabyte drive I'm using.
I wasn't sure which forum to put this into. I created a backup image on a usb hard drive. I wanted to be able to restore it using a usb recovery thumb drive. I used the create usb recovery tool and created the recovery flash drive. When I try to boot from the flash drive I get an error saying that the boot configuration data is missing or contains errors. I can boot up the laptop using the current windows install so it isn't referring to the hard drive. I have tried several usb drives and get the same message on each. Here is a screenshot of the message.
last few hours I spent trying to manually deploy Windows 10 on clean GPT disk but after applying image and rebooting I always end in unbootable state.
I manually setup drive like this:
Code:
select disk 0cleanconvert gptcreate partition primary size 350 #RE tools won't fit 300MB anymore :-)format quick fs ntfs label "Windows RE tools"assign letter tset id de94bba4-06d1-4d40-a16a-bfd50179d6acgpt attributes 0x8000000000000001create partition efi size 100format quick fs fat32 label Systemassign letter screate partition msr size 128create partition primary format quick fs ntfs label Windowsassign letter wlist volumeexit#no recovery image partition as per documentation it is no longer needed and followed by pretty common deployment:
After reboot I always end unbootable (as we talk Apple computer it means 1) no partition on Option or 2) folder with ? or 3) just gray screen, make your pick). There's a chance that Windows rely on some UEFI 2.0 feature, which is not available as the old guy has 1.2 only. Or maybe I missed some step somewhere.
