on dells you can reboot, press f2, f9 or f12 to see the option where you can choose from what device to boot up.
Your all ready ma'am, turn off, better to uninstall Anti-Virus if you have it, in Command ADMIN prompt run sfc /scannow that cleans errors on partition, then go fer it, lol
Without reading back through all this, does Lakerfanaways have the iso extracted to a flash drive or what? Did he use Rufus to make it uefi bootable? If so, do the F2 thing again and change boot mode, and there disable safe boot. Save and shut down. Then he should just do F12 the same way as he finally got F2 to work and, if the flash drive is uefi bootable, he should see it as a choice. Those 8700s boot so fast that you have to hit the keyboard keys before during and after you turn it on. He should be able to get a boot menu up though. Machine gun that F12 key with one finger while turning on the tower with the other hand (or borrow a hand).
He's a she. Okay, I missed that. Still think SHE should use a Rufus uefi bootable flash drive instead of the dvd.
Can we all get clear on this so everybody can stop asking same thing over and over. @lakerfanalways IS A SHE Any other language just let me know
Still the same breech birth we talk about? Doggie learned to love skilled ""Support Techs"" the last days, hope there will be found at least one in the end. My Favorite so far: "Ahh, i can see you're trying to install Windows 10, please install Win 7 and go the upgrade path".
You mean you don't like chatting with the script kiddies?.... (Join the club.) Gratefully, I have no recollection of the last time I might've done that.
Since am newbie can not start new thread yet and search doesnt work right now I have a question if anyone also gets BLACK SCREEN or BLUE SCREEN when the computers loading up after power on? I was using win7/8.1 on this hw without any problem, but on W10 I get black screen before the login screen for long minutes, sometimes followed with blue screen errors very similar to errors in windows 8 (I have never experienced them - only know they happens from google search). W10 is a clean install (after previous upgrade from W8.1 to get activation working). I have a SLI system, but got already 4th nVidia driver version and still happening. Today I have installed (clean) W10 Home on brand new laptop and it was doing the same black screen for long minutes, no blue screen, then restarted itself and loaded fine. On this black screen I am talking about there is no mouse cursor or anything. Seems like the video card doesnt get anything to display but monitor is detecting a signal as it stays ON. Anyone? Thank you
C:\Windows\system32>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios. The log has 12MB what happend that there are errors? I did not tweak the windows at all and it is clean installation so? Will another clean install fix this?? )
Hi, is anyone getting the restart loop in Win10? I'm getting it, but just when I have Intel Virtualization Technology ENABLED, if I DISABLE it, it boots just fine. Also, this issue occurred right after I installed Visual Studio 2015. Help please!
There's still many bugs with the current NVIDIA drivers and SLI esp. for Kepler users. Your going to have to run a single card until the drivers mature.
Try opening control panel, device manager, go down until you see display adapter's, click on it, it will now show which driver is installed, right click on it, select uninstall, remember which card it is, reboot, Windows will install another driver, hopefully not the same one
@Tito, or any other mod. Can you lock this thread? PPL just use it for chatting now. There's not really a lot I can do with the OP.
If it asks, it cannot find the needed files on the Server. Sometimes it detects files wrongly and is confused by itself (huh ... a shadow). Needs to check the CBS log, to see where it fails.