shutdown /r /t 0 | TheaterFire

it saves so much time on a slow machine if you're getting ready to clone and you want to disable hibernate or encryption... or anything else for that matter

[-]

BlackV@reddit

Win + r would seem faster than that

[-]

RCN_KT@reddit

Not for admin. Just for regular-degular CMD

[-]

Secret_Debt_88@reddit

Ctrl+shift+enter opens run commands as admin

[-]

Creative-Type9411@reddit

no, I understand that but when a machine is being super laggy, nothing works, and I have had problems in unresponsive situations where I can get task manager to pop before anything else

[-]

vass0922@reddit

Oh man reminds me of the NT4 days. If the mouse cable was unplugged, the only way to get your mouse back was reboot which took ages.

There was no windows key back then so had to wonky things like that.

Also on some iLO if mouse wasn't functioning or if it was just too slow

[-]

dccjaday@reddit

In our lab, there was no space between the keyboards for a mouse. So the techs learned all the keyboard shortcuts. Windows were flying up and down. So it never mattered if the mouse got disconnected!

[-]

TMITectonic@reddit

Win + X, then press A. Works much quicker for me... ¯\_(ツ)_/¯

[-]

Creative-Type9411@reddit

ill try that on a slow machine but im pretty sure task manager comes up quicker

[-]

TMITectonic@reddit

Fair enough, but I suspect we might be defining 'quicker' differently...

From a technical standpoint, Win+X is just triggering a quick context menu via the Windows Shell. Whereas Ctrl+Shift+Esc has to spin up the Task Manager process first. On a healthy machine, Win+X is definitely lighter and faster.

Having said that, I do concede that if a machine is hanging so badly that the Shell (Explorer) is unresponsive, Task Manager is often the only thing that will still pop up, as the keys trigger an Interrupt that will try to launch Task Manager, instead of asking the already busy Shell. For day-to-day use, though, Win+X saves a fair amount of clicking and wait time for Task Manager to load. Cheers.

[-]

Kompost88@reddit

Win + X still opens mobility center in my head :D

[-]

RandomSkratch@reddit

How does UAC not catch this?

[-]

WhyLater@reddit

Having a /t greater than 0 implies /f.

So you just need:

shutdown /r /t 1

[-]

HoolioLion@reddit

Always has been

[-]

CthulhuBathwater@reddit

Should be the top comment to fix OP's problem.

[-]

oversizedmoosecalf@reddit (OP)

Does not fix it for me. Same result of “you’re about to be signed out. Windows will shut down in 1 minute.”

[-]

dewatermeloan@reddit

Could it be any GPO that's causing this timeout?

[-]

ifitwasnt4u@reddit

On desktops. Not servers. Servers you have to provide a comment too.

[-]

Flerbizky@reddit

Not OOTB you won't. Unless someone added a Policy saying a comment is required, /r /t 01 will do you just fine.

[-]

Bitcoin__Dave@reddit

this is the way

[-]

webjocky@reddit

Let's not forget about /fw /r /f /t 0 that immediately reboots you into the UEFI.

[-]

oversizedmoosecalf@reddit (OP)

Apparently our AV has been interfering with it disabled specific component and it works.

Thanks for confirming I’m not crazy that I used to work. :D

[-]

_araqiel@reddit

What tool?

[-]

PizzaCatLover@reddit

This is the way

[-]

Frothyleet@reddit

/t with a value of anything besides 0 implies /f

[-]

xGrim_Sol@reddit

Same, but I always do /f /r /t 0 instead in that order.. It made it easy to remember when I was starting out in IT that it was the “shutdown fart” command.

[-]

djdanlib@reddit

What's wrong with “reboot now"

[-]

Doomstang@reddit

That's my go-to as well

[-]

Sad_School828@reddit

What's wrong with shutdown /r now?

[-]

oversizedmoosecalf@reddit (OP)

Interestingly, init 6 stopped working on some of my Linux machines, as if it were an invalid command. I guess that’s an old way of doing it too.

[-]

CarelessAd3496@reddit

You are not going crazy.

[-]

El_Gigamono@reddit

Not knowing OP personally, I'm not sure we're qualified to make that statement. Maybe "This is not evidence of you going crazy". (I know, I know, its being pedantic)

[-]

oversizedmoosecalf@reddit (OP)

lol. I’m not thankfully. Just our shitty endpoint that changed command I’ve been using since the early 2000s. It works fine without the software.

[-]

Shagam@reddit

Check their CO detectors.

[-]

CarelessAd3496@reddit

Very good point! >.<

[-]

B0ndzai@reddit

That's a perfectly sane command to run.

[-]

_Durs@reddit

You’re missing /f to force.

[-]

MacrossX@reddit

Shhh sleep now

gif

[-]

ph33rlus@reddit

I use shutdown -r now. Works great

[-]

420GB@reddit

shutdown /r /t 0 restarts immediately but doesn't force the restart, so it's very possible it gets delayed or even blocked completely by any running process.

shutdown /r /t 1 does force the restart so it will really happen immediately without interference unless the OS is on a really really broken state. Had one VM once that just wouldn't reboot no matter what (always got stuck) unless you hard reset.

[-]

pawwoll@reddit

u do it wrong, open copilot, ask for command to shutdown pc, copy paste
faster than 1min

[-]

ComprehensiveBerry48@reddit

Iam using just 'now' instead of a number.

[-]

Aggravating_Ad8597@reddit

Yeah I use shutdown -r now

[-]

h9xq@reddit

I use restart-computer -force

[-]

russellvt@reddit

Dashes, not slashes.

[-]

oversizedmoosecalf@reddit (OP)

Help file indicates slashes. Dashes and mixed work as well. Not the issue anyway, it was my AV component causing the issue.

[-]

russellvt@reddit

Sounds like Windoze, then?

Sorry, I try to error on the POSIX side rather than be more Windows-centric (ie. I don't think that will work on any other platform, will it?).

[-]

ThecaptainWTF9@reddit

Shutdown -r -t 0 is what I do

[-]

Newalloy@reddit

powershell instant:

Restart-Computer -Force

[-]

Witte-666@reddit

That's also what I do, the only drawback is the time Powershell takes to start the console. Cmd is much faster.

[-]

VaderJim@reddit

WIN KEY + `

[-]

BlackV@reddit

Only true if you don't have powershell open 24/7, and why would you closer powershell like a loony person ;)

[-]

QuantumDiogenes@reddit

Sometimes your servers restart. Then you have to open PowerShell back up.

[-]

BlackV@reddit

That's rookie talk, never reboot

[-]

QuantumDiogenes@reddit

pats Linux servers. Already ahead of you. :)

[-]

BlackV@reddit

ha, hey windows hotpatch is here to save us on this side of the fence too.....
...
..
probably

[-]

Newalloy@reddit

Powershell.exe -command Restart-Computer -Force

[-]

fizzlefist@reddit

How do I do that with the copilot button? /s

[-]

Rockz1152@reddit

-ComputerName <Host> is a handy option for this too

[-]

illicITparameters@reddit

had to scroll way too far down to find this.

[-]

oversizedmoosecalf@reddit (OP)

This still works for me, I use it in scripts.

[-]

tacticalAlmonds@reddit

Wat? Surely this can't be real. I'll have to check later today. What os?

[-]

oversizedmoosecalf@reddit (OP)

Win 11 24h2 but I swear it’s been happening on servers as well.

[-]

theEvilQuesadilla@reddit

I got an instant reboot on my system.

[-]

oversizedmoosecalf@reddit (OP)

Thanks. It’s doing it on win 11 and server 2022 for me. Possible others

Checking group policy, maybe there’s some setting??

[-]

cruel-ko@reddit

Only works on prod servers, so try that.

[-]

hihcadore@reddit

Gotta wait till Friday at 4 pm to be sure

[-]

oversizedmoosecalf@reddit (OP)

Locked and loaded.

[-]

iama_bad_person@reddit

This has been a thing on and off for years since Windows 10. I never know if it is going to work so I ALWAYS use /t 1 instead of 0.

[-]

tacticalAlmonds@reddit

It was their edr

[-]

oversizedmoosecalf@reddit (OP)

It turns out our endpoint security was interfering with this…. Jfc

[-]

ProfessionalITShark@reddit

Which EDR

[-]

tacticalAlmonds@reddit

oof. If it's not DNS it's EDR :) good luck.

[-]

oversizedmoosecalf@reddit (OP)

I almost blamed DNS first. Hah.

Thanks!

[-]

HappyDadOfFourJesus@reddit

I've only ever used shutdown /r /t 1 because in the grand scheme of things, one extra second isn't making any difference.

[-]

oversizedmoosecalf@reddit (OP)

It’s interesting that /t 1 still works for me, just not 0.

Still waiting to hear why it’s like this from a vendor.

[-]

SnooCamera@reddit

I've not looking at that. I've always used, shutdown -h now

[-]

TronFan@reddit

while we are on the topic of the shutdown command.

is there a way to use this to reboot a server without installing a pending update.

[-]

christurnbull@reddit

my favourite is shutdown -p

[-]

FleaDad@reddit

shutdown -t 0 -h now

[-]

anonpf@reddit

I always use shutdown /r /t 00 with no issue.

What AV? Also, did you run powershell elevated?

[-]

MuthaPlucka@reddit

Shutdown -r -f -t 1

[-]

ParanoiA609@reddit

Shutdown -rtfm

[-]

anonpf@reddit

😂😂😂

[-]

MuthaPlucka@reddit

I see what you did there :-)

[-]

wildfyre010@reddit

I have never done anything other than shutdown -r now. The existence of the -t flag is a surprise!

[-]

Catsrules@reddit

shutdown -r now

That doesn't work on Windows. It works fine on Linux but Windows requires the -t X

[-]

Rawme9@reddit

-f is for force. I think setting -t 0 automatically creates the force flag as well as making it immediate which is why I was taught to use it

[-]

BlackV@reddit

No, the help says force is only implied it times greater than 0

[-]

Rawme9@reddit

Ahh my bad..misremembered!

[-]

Frothyleet@reddit

Actually, -t with any value greater than 0 implies -f. "-t 0" on its own does not force close apps.

[-]

anonymousITCoward@reddit

shutdown /? is going to blow your mind!

[-]

WWGHIAFTC@reddit

I used to (waay back int he day) have scripts that I could feed bulk hostnames too to schedule reboots for overnight using the /t (or -t back then) Or I could select AD OUs to reboot a specific store or department.

The timer was great for that.

[-]

Steve_78_OH@reddit

There are other switches as well. Run "shutdown /?" to see all of them.

[-]

UseMoreHops@reddit

I always include the /f as well

[-]

machacker89@reddit

Yea I have two shortcuts on my desktop for Restart and shutdown. I noticed the same thing. I thought it was just me. Lol

[-]

DonL314@reddit

I saw a lot of the other comments so far. I haven't tested as I have no Windows computer nearby, but just speculating: Was it in a cmd shell or PowerShell shell? (🙂)

There could be a difference.

[-]

oversizedmoosecalf@reddit (OP)

Cmd prompt. Powershell you have to add a bunch of arguments to format it correctly

Either way, it was my AV causing issues.

[-]

armaghetto@reddit

/r is restart. /s is shutdown

[-]

Rosenqvist@reddit

I always did /1. Maybe I knew

[-]

noOneCaresOnTheWeb@reddit

shutdown /r /t 1 is the only correct answer.

[-]

Pristine-Item6452@reddit

i'm a batch coder (this command restart the computer now( the /r stands for restart and the t stands for timeout

[-]

King-of-the-Elves@reddit

I swear that by adding the /t arg it imploed the /f arg as well.

[-]

fmtek81@reddit

It does

[-]

BlackV@reddit

It does on values greater than 0

[-]

fmtek81@reddit

True. Just saw that.

[-]

freebytes@reddit

I have always used shutdown -r now if I want an immediate restart. (Not sure what operating system you are referencing, but I think this works on everything.)

[-]

Frothyleet@reddit

Rookie windows admins think "shutdown /f" is a forced shutdown.

OG admins know that a REAL forced shutdown is best accomplished with sysinternals in your $PATH:

notmyfaultc.exe crash 0x01

[-]

oversizedmoosecalf@reddit (OP)

Ctrl-alt-del

Ctrl + click on the power button on lower right

:o

[-]

HimalCheese@reddit

I've always used: "shutdown -f -r -t 1"

[-]

Allen_Ludden@reddit

Splat used to be the rectangle with elongated corners on travel agent keyboards running Sabre.

As in “g splat 880843” as the key sequence to identify your agency.

[-]

lbaile200@reddit

I must be old. Sudo shutdown now

[-]

Stryker1-1@reddit

This is a windows machine thus no sudo or shutdown command

[-]

lbaile200@reddit

Ah, this makes way more sense. Thanks for clarifying.

[-]

BlackV@reddit

Also the want to reboot not shutdown

[-]

severedgoat_01@reddit

What if you add /f?

[-]

oversizedmoosecalf@reddit (OP)

Same, 1 minute warning.

[-]

puffpants@reddit

I think t is not a slash but a hyphen

Shutdown /f /r -t 0

[-]

agoia@reddit

Think you can do either, I typically do shutdown -r -f -t 0

[-]

severedgoat_01@reddit

Hmm. I always use /t 0 for immediate shutdown

[-]

InfraScaler@reddit

type -a shutdown

[-]

R2-Scotia@reddit

imit 6

[-]

BlackV@reddit

init 0 for the lolz

[-]

BlackV@reddit

Meh

Shutdown /s / t 1

Is the superior option anyway, /t 0 required to add /f to be effective

[-]

New-Seesaw1719@reddit

shutdown /r /t 0 should be immediate

[-]

Casty_McBoozer@reddit

I haven't used shutdown.exe in some time.
Restart-Computer -Force

[-]

headcrap@reddit

Indeed I started using this for "other systems" but my own laptop I still Win+R and choose the /r or /s options in the MRU for whichever function I'm wanting to perform.

-Computername all the rest.

[-]

thewunderbar@reddit

Literally did that 5 minutes ago and it worked just fine.

[-]

oversizedmoosecalf@reddit (OP)

Updated my post. Figured it out. Thanks for confirming!

[-]

TheLexikitty@reddit

Now I think I’m going crazy because I always thought you had to specify at least 1 second. My muscle mentor is /t 1 . I might have memorized it in the XP days though.

[-]

irandolph@reddit

What product was interfering?

[-]

techyno@reddit

I use /r /t 2

2 seconds is enough and has so far worked without fail

[-]

Entire_Dependent8214@reddit

Go physical and hold down that power button.

[-]

oversizedmoosecalf@reddit (OP)

Well now all the servers are down

[-]

Entire_Dependent8214@reddit

You’ve not mentioned. Is this a server or workstation ? If it’s physical server(assuming) . Double check the back and unplug the cable and plug back in it should work . Or just flip the power supply switch…honestly just /f it

[-]

oversizedmoosecalf@reddit (OP)

Physical and VM

I traced it down to our endpoint interfering somehow. Opening a case with vendor because this seems ridiculous.

[-]

Dudefoxlive@reddit

Shutdown -r -t 0 is what i have always used. Wonder if an update may have changed how it works.

[-]

oversizedmoosecalf@reddit (OP)

It turns out our endpoint security was interfering with this…. Jfc

[-]

anonymousITCoward@reddit

use /t 00 for immediate reboots

[-]

fmtek81@reddit

This is what I was going to come say. /t 00 is always what I’ve used. Shutdowns right away.

[-]

overkillsd@reddit

I always use shutdown /f /r /t 0 because I'm childish and it's easy to remember "fart"

[-]

anonymousITCoward@reddit

I do the same!!!!

and it has the benefit of being able to read it out

shutdown /f /r /t 00

shutdown /f(orce) /r(eboot) /t(ime) (n)0 (seconds)

thats how i get the underlings to remember it...

[-]

Brief_Philosophy_861@reddit

Worked few hours ago :)

[-]

PhilosophyBitter7875@reddit

This may be the first time everyone in this sub is being helpful, going to take this moment in.

[-]

oversizedmoosecalf@reddit (OP)

Don’t get used to it!

[-]

connexionwithal@reddit

You sure it’s not -t? Coulda swore it was shutdown /r -t 0

[-]

oversizedmoosecalf@reddit (OP)

Seems you can mix and match - and / but it still does not fix for me, still get 1min sign out warning. Odd

[-]

Fake_Cakeday@reddit

I've used it yesterday, 24 hours ago, with no issue on 24H2 machines.

Maybe I only tried it in the OOBE phase? 🤔 I don't remember.

[-]

purplemonkeymad@reddit

/t 0 does a normal shutdown, anything above 0 (eg /t 1) automatically does /f and won't wait for stuff to stop properly. So if it needs to happen asap /t 1 else just do /t 0 and let it do stuff normally.

[-]

Ok_SysAdmin@reddit

Powershell Restart-computer -force

[-]

erwintwr@reddit

not sure about /t 0

but on my windows 10 :D - yes sorry -
shutdown /p /f
works wonders (normal shutdown especially when rushing someswhere 90% of the time finds some application that is "blocking shutdown" ->
caution above command forces shutdown -> not "are you sure , do you want to save this document" prompts will stop it.

[-]

andpassword@reddit

shutdown -r now

[-]

daveed31@reddit

See you need to tell your computer to

Winninit

That reboots really fast. Best command to quickly reboot.

[-]

vijay-lalwani@reddit

Turn on verbose mode on signin/signout and bsod. You will know where it's stuck at if you really wanna find out.

I can't remember the regkey but it's in christitus windows debloater. You might find the regkey on his website.

[-]

PopePolycarp@reddit

I just tried it on Windows 25H2 (OS Build 26200.8037) and it worked immediately.

[-]

oversizedmoosecalf@reddit (OP)

Thanks. Maybe it’s just our env all of a sudden? Weird.

[-]

Educational_Item5124@reddit

Ask the sysadmin, they'll know what it is for sure!

[-]

Hotshot55@reddit

Yes, giving shutdown a time of 1 second or higher used to imply /f, it was even mentioned in the man page.

[-]

Nandulal@reddit

is there a difference between PS and command?

[-]

oversizedmoosecalf@reddit (OP)

Restart-Computer just does it immediately. No prompt.

[-]

Nitramite@reddit

Haven't tested it with 0, but I've always used /t 1 because anything amount over 0 implies /f which force closes applications, and usually if I'm doing a remotely reboot, I want it to happen, not to stay pending some apps.

Stinks if they added a delay without warning

[-]

insaneturbo132@reddit

This was my first thought as well. It was best practice to choose something above 0 to allow services and applications time to stop gracefully.

[-]

theEvilQuesadilla@reddit

What OS, op?

[-]

oversizedmoosecalf@reddit (OP)

Win 24h2, server 2022

Maybe others. I feel like I’ve run into it a few times now.

[-]

whistlepete@reddit

I always do shutdown /f /r /t 005 and never had a warning doing that. The /f isn’t really necessary as if the timeout is greater than 0 the /f isn’t implied.

[-]

Xanth592@reddit

Ivw always uses a tick - instead of a slash /

[-]

archery713@reddit

Just used this yesterday on a W10 box. Worked instantly. Weird

[-]

FLATLANDRIDER@reddit

Normally shutdown /r gives a 1 minute warning.

Shutdown /r /t 0 should restart immediately.

[-]

oversizedmoosecalf@reddit (OP)

Normally yes, I’ve been using this command forever and just started running into this in the past year or so maybe it’s just our env, not sure.

[-]

rainofterra@reddit

Any shutdown scripts in your environment? Something being enforced by GPO maybe?

[-]

LodanMax@reddit

Yes, and if you actually read what OP said was that they used the “/r /t 0” flags and it still takes 1 minute.

[-]

FLATLANDRIDER@reddit

Yes I know. I said that's what it should do. But from other comments, it seems like it's not.

[-]

Entegy@reddit

Do a /t 1. I think /t 0 implies Windows Emergency Shutdown which has broken some things for me in the past and is just not a good way to always shutdown. Maybe that's why Microsoft added a minute to the emergency shutdown.

/t 1 gives processes 1,000 milliseconds to finish up before doing a normal shutdown with an implied "continue anyway".

[-]

pdp10@reddit

With x86/x86_64 ACPI VM guests, you can trigger a soft-shutdown from the hypervisor without needing to touch the guest OS. In QEMU command protocol or CLI, for example, it's system_powerdown.

As long as RTC timing isn't broken and you can softly shutdown a guest from hypervisor, then it's likely that you don't need a traditional virtualization "guest daemon" like open-vm-tools.

One Windows Server 2022 test instance, takes 8 seconds from system_powerdown to being offline. Pending updates and troublesome services could, of course, extent that.

[-]

oversizedmoosecalf@reddit (OP)

Tried that, still gives 1 min warning.

[-]

Leather-Arachnid-417@reddit

You are not wrong..It used to .add /f now

[-]

samuellavoie@reddit

I’ve always entered shutdown /f /r -t 0

It seems to still work

[-]