Is Win10 All There?
-
But what else could change the order? I don't think there's anything; hitting DEL to enter the BIOS is the only way I know. All I did was to get up and go for my dinner leaving everything as it was. I think Visual Studio was open at the time.
Like Rob suggested, my first thought would be the cmos battery flaking and your bios resetting to default.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
-
xiecsuk wrote:
Has anyone else experienced unexpected behaviour with Win10?
At the risk of being a broken record, nay, nay, and thrice nay. I'm almost at the point of wishing I had so I could join the 'big boys club'! If the boot order was changed in BIOS then would that not suggest that it was not Windows that was the problem? I'm not aware of anything in Windows that can reach back into the machine boot.
I am not a number. I am a ... no, wait!
9082365 wrote:
I'm not aware of anything in Windows that can reach back into the machine boot.
Me neither, but the last week I ended up removing the CMOS battery and plugging it again into my father in-law computer as even nobody-knows-what-happened-here the computer was unable to continue after the POST display at the beginning and he promised me that he had not touched anything apart of Windows... :~
[www.tamautomation.com] | Robots, CNC and PLC machines for grinding and polishing. [YouTube channel]
-
Having had problems with an unlicensed copy of Win8 that was installed on a new machine I bought a few years ago, I purchased a pukka copy of Win10 Home and installed it. I must say I like it very much, including Edge. However, I get unusual things happening from time to time. They are usually not that important. Things like desktop icons of automatically started programs suddenly start disappearing off the desktop only to re-appear perhaps a week later. Last night, however, I thought the system had gone. My wife called me for dinner so I just left the system as it was and went down to join her. When I had finished, I went back to my office and the screen was off, as I would have expected after such a time period. I twiddled the mouse expecting the screen to display the last desktop image. However, I got a message indicating that it was trying to boot from a non-bootable disc partition. I did a restart and went into the BIOS and checked the boot order. I have 3 separate hard drives installed and the order had indeed changed. Having reset it, the machine then restarted without any problems. This has never happened to me before on all the systems way back to Win XP, and it is rather worrying. It suggests something may happen that I won't be able to recover from. Has anyone else experienced unexpected behaviour with Win10?
Well, ever since upgrading from 7 to 10, I'm having trouble with standby. The machine would go into standby, but when I later fiddle with the mouse or keyboard to wake it up, it tries, but then shuts down completely. I haven't invested enough energy into figuring this out to say for certain whether this has anything to do with Windows 10 or not, because I never used standby all that often anyway.
-
Well, ever since upgrading from 7 to 10, I'm having trouble with standby. The machine would go into standby, but when I later fiddle with the mouse or keyboard to wake it up, it tries, but then shuts down completely. I haven't invested enough energy into figuring this out to say for certain whether this has anything to do with Windows 10 or not, because I never used standby all that often anyway.
-
Having had problems with an unlicensed copy of Win8 that was installed on a new machine I bought a few years ago, I purchased a pukka copy of Win10 Home and installed it. I must say I like it very much, including Edge. However, I get unusual things happening from time to time. They are usually not that important. Things like desktop icons of automatically started programs suddenly start disappearing off the desktop only to re-appear perhaps a week later. Last night, however, I thought the system had gone. My wife called me for dinner so I just left the system as it was and went down to join her. When I had finished, I went back to my office and the screen was off, as I would have expected after such a time period. I twiddled the mouse expecting the screen to display the last desktop image. However, I got a message indicating that it was trying to boot from a non-bootable disc partition. I did a restart and went into the BIOS and checked the boot order. I have 3 separate hard drives installed and the order had indeed changed. Having reset it, the machine then restarted without any problems. This has never happened to me before on all the systems way back to Win XP, and it is rather worrying. It suggests something may happen that I won't be able to recover from. Has anyone else experienced unexpected behaviour with Win10?
Sounds like you have a hardware issue perhaps aggravated by W10. In my experience with W10 on my laptop, it loves to install updates at the most inopportune times. I'm wondering if it installed an update while you were gone and the system was idle. It rebooted (unlikely but possible) and then ran into a transitory hardware glitch - perhaps the m-board battery like has been mentioned. Just spit-balling. Is there an update for BIOS? (BTW, I'm unfamiliar with the term "pukka".)
Cheers, Mike Fidler "I intend to live forever - so far, so good." Steven Wright "I almost had a psychic girlfriend but she left me before we met." Also Steven Wright "I'm addicted to placebos. I could quit, but it wouldn't matter." Steven Wright yet again.
-
Sounds like you have a hardware issue perhaps aggravated by W10. In my experience with W10 on my laptop, it loves to install updates at the most inopportune times. I'm wondering if it installed an update while you were gone and the system was idle. It rebooted (unlikely but possible) and then ran into a transitory hardware glitch - perhaps the m-board battery like has been mentioned. Just spit-balling. Is there an update for BIOS? (BTW, I'm unfamiliar with the term "pukka".)
Cheers, Mike Fidler "I intend to live forever - so far, so good." Steven Wright "I almost had a psychic girlfriend but she left me before we met." Also Steven Wright "I'm addicted to placebos. I could quit, but it wouldn't matter." Steven Wright yet again.
Sorry about that. Pukka is adopted from the times of the English Raj in India. It is an Anglo-Indian word which means, among other things, thoroughly good, complete, solidly built, genuine, high class. It's an interesting, plausible suggestion as to what might have caused the re-boot. I will see if it happens again. I've never actually done a BIOS update although I have been tempted. I will check if one is available and, if so, see if I can pluck up the courage to do one.
-
I've noticed a big change in the effort needed to get out of standby. I really haven't had a chance to tinker with the power settings too much, but am considering disabling standby.
"Go forth into the source" - Neal Morse
-
Well, ever since upgrading from 7 to 10, I'm having trouble with standby. The machine would go into standby, but when I later fiddle with the mouse or keyboard to wake it up, it tries, but then shuts down completely. I haven't invested enough energy into figuring this out to say for certain whether this has anything to do with Windows 10 or not, because I never used standby all that often anyway.
We have a surface book pro 4, and it will go into fake standby mode (black screen, except for JING Icon), and we cannot seem to do anything. It is partially alive. Luckily, hitting Ctrl-Alt-Del got me back to the login screen, everything was normal after that. We have noticed HUGE issues once updates are downloaded and ready to install. It is like it starts disabling crap until you do the reboot that installs stuff. Comparing the two, I prefer windows 7 still, but I can see eventually making the switch. HTH
-
Sorry about that. Pukka is adopted from the times of the English Raj in India. It is an Anglo-Indian word which means, among other things, thoroughly good, complete, solidly built, genuine, high class. It's an interesting, plausible suggestion as to what might have caused the re-boot. I will see if it happens again. I've never actually done a BIOS update although I have been tempted. I will check if one is available and, if so, see if I can pluck up the courage to do one.
Don't try one if your CMOS battery may be flaking out.
-
But what else could change the order? I don't think there's anything; hitting DEL to enter the BIOS is the only way I know. All I did was to get up and go for my dinner leaving everything as it was. I think Visual Studio was open at the time.
If you are using UEFI then I think windows does have the ability to change boot options. This happened to me as well, windows changed my boot order after an update.
--------- Andre Sanches "UNIX is friendly, it's just picky about its friends"
-
If you are using UEFI then I think windows does have the ability to change boot options. This happened to me as well, windows changed my boot order after an update.
--------- Andre Sanches "UNIX is friendly, it's just picky about its friends"
-
Well, ever since upgrading from 7 to 10, I'm having trouble with standby. The machine would go into standby, but when I later fiddle with the mouse or keyboard to wake it up, it tries, but then shuts down completely. I haven't invested enough energy into figuring this out to say for certain whether this has anything to do with Windows 10 or not, because I never used standby all that often anyway.
I gave up using standby, it cant handle my intel hardware. Most times that it does a windows update my start menu and notification panel die and require rebooting in safe mode to make them work again. ms know about this bug but have not yet been able to fix it, so that doesn't pump up my confidence in win10.