Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Waiting for sens and then reboots

  • Please log in to reply
2 replies to this topic

#1 Brenda52411


  • Members
  • 2 posts
  • Local time:08:56 AM

Posted 02 August 2017 - 12:03 PM

We have multiple Win 10 machines around the house.  This morning we found the computers would not connect to the internet for no known reason, so we rebooted the DSL modem and router.  My Win 10 laptop connected to the internet, but another Win 10 desktop would NOT connect to the internet.  That machine gave the error message "Waiting for sens".

It appears to finally finish the boot, (still not connected to the internet).  Within just a couple of minutes (or less - not long enough to do anything) I get the message that "in the next minute, the computer will be rebooted".

Then the machine waits 1 minute and reboots, going back to the "Waiting for sens" message, etc.  I'm just caught in what I used to call a "do loop" (old programmer).

I'm not sure what to do.  I have not installed any new programs, have not made any changes to the machine, have not had any BSOD.  Basically this machine has not ever been a problem machine.  (Dell that is about 3 years old.)

I'm at a loss as to what my options are, besides just rebuilding the machine.  It's used every day.  I didn't notice yesterday that it had any updates from Microsoft.

I have googled this issue for a few hours this morning.  It seems to have happened to many SERVERS, not desktops.  I haven't seen any fixes that actually have been reported to work for this problem.

Thoughts before I rebuild the machine?

Thank you,


BC AdBot (Login to Remove)


#2 britechguy


    Been there, done that, got the T-shirt

  • Moderator
  • 9,247 posts
  • Gender:Male
  • Location:Staunton, VA
  • Local time:08:56 AM

Posted 02 August 2017 - 12:15 PM



          I'm not quite sure what you mean by "rebuild the machine."


          If you're still on Version 1607 on that Machine I'd definitely try the instructions on Updating Windows 10 using the Windows 10 ISO file to upgrade the machine to Version 1703 to see if this solves anything.  You will, though, probably have to do the upgrade/update by changing boot order and actually using the Windows 10 media from that avenue rather than straight from the desktop.  I just updated seven machines yesterday using the exact technique in those directions because the machines actually boot, but the same options should present themselves going the bootable route.

Brian  AKA  Bri the Tech Guy (website in my user profile) - Windows 10 Home, 64-Bit, Version 1809, Build 17763 

     Presenting the willfully ignorant with facts is the very definition of casting pearls before swine.

             ~ Brian Vogel






#3 Brenda52411

  • Topic Starter

  • Members
  • 2 posts
  • Local time:08:56 AM

Posted 02 August 2017 - 12:34 PM


Thank you.  I will try your suggestion.  Hopefully that will fix the problem.  I have never seen a machine do anything like this.  I wish I could figure out what caused the problem, but if I can get it fixed, that's the important thing.


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users