Блог системного администратора Windows/Linux/FreeBSD

Как посмотреть uptime в Windows Server

Как посмотреть uptime(время работы) в Windows Server 2008/R2/2012/R2 ?

1. В Windows 7/8/Server 2008 , открыть диспетчер задач и на вкладке «Быстродействие/Производительность» посмотреть время работы Windows:

2. Нужно запустить в командной строке утилиту systeminfo. В ней можно узнать время загрузки системы. Открываем командную строку и вводим:
systeminfo | find «System Boot» или systeminfo | find «Время загрузки» :

Как удалённо узнать время последней загрузки Windows? Uptime

С помощью PSExec.
Computername — имя удалённого компьютера:

Для англоязычной версии операционной системы:

Для русскоязычной версии операционной системы:

С помощью Powershell и службы событий:

Как узнать время работы в Windows?

Какой самый простой способ узнать, как долго компьютер включен в Windows?

8 ответов 8

• Запустить командную строку
• Тип Systeminfo

Найти «Время загрузки системы»

Дней: 10 часов: 10 минут: 10 секунд: 10

Для более короткого результата вы можете использовать:

есть отличный инструмент командной строки от Microsoft uptime.exe:

Хорошо, что этот инструмент работает очень быстро.

Время работы [сервер] [/s] [/a] [/d: мм / дд / гггг | / p: n] [/ heartbeat] [/? | /Помогите]
Имя сервера или IP-адрес удаленного сервера для обработки.
/s Показать ключевые системные события и статистику.
/a Показать события сбоя приложения (предполагается /s).
/d: рассчитывать только для событий после мм / дд / гггг.
/ p: рассчитывать только для событий за предыдущие n дней.
/ сердцебиение Включить / выключить сердцебиение системы
/? Основное использование.
/ help Дополнительная информация об использовании.

Откройте командную строку и введите:

Изменить: На самом деле это скажет вам дату и время, когда компьютер был с, а не продолжительность.

В Windows 7 / Windows Server 2008 и выше эта информация отображается в диспетчере задач на вкладке «Производительность».

Это может быть быстрее, чем при использовании командной строки, и работает в тех случаях, когда у вас могут быть проблемы с WMI, мешающие запуску systeminfo.

Если вам нужно найти это удаленно, вы также можете запустить

systeminfo /s SERVERNAME | найти «Время:»

из командной строки.

Следующая команда дает время последней перезагрузки для удаленной системы:

Windows 10: 35 minute boot time on fast PC

I recently upgraded my PC to windows 10. Initially (the first two days) it was rocket fast at booting up — amazingly so.

Yesterday though something must have happened because now it takes 30 minutes to boot up. When it is finally running it is super-quick and everything works. It is just the crazy long boot time that is the problem.

It displays the Windows 10 icon briefly, then goes black for 30-35 minutes. Then it starts OK.

Details (I am not a technical person sorry).

PC has a 250GB SSD and 1TB HDD

Was running Windows 7 64bit before upgrade.

-Disabling and updating graphics drivers (no effect)

-Defrag Hard drives.

-Full system scan x2 with Nortons.

-Disable/enable «fast startup»

-Scan disk came up clean

I have a feeling it may be something to do with the communication between the SSD and HDD but have no idea how to assess this problem.

Any suggestions would be welcome,

Replies (16) 

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Thank you for posting your query on Microsoft Community.

I appreciate you for providing details about the issue and we are happy to help you.

I recommend you to run the System Maintenance troubleshooter and check if it helps.

Follow the below steps:

1. Type troubleshooting in the search bar.

2. Select Troubleshooting .

3. Select View all on the top left corner.

4. Click on System Maintenance .

5. Follow the on-screen instructions to run the troubleshooter.

R eference: Refer to the following Microsoft article on Windows 10 help & how-to .

Kindly let us know if you need any further assistance with Windows. We are glad to assist you.

3 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

This post mentions a file called «Boot time custom view.zip», it might help you see where the problem is. The problem is that you may have to join that Forum to get the file downloaded.

If you want to get things going yourself, and manually setup (boot time logging), try and follow these instructions.

If this is a recent occurrence then try fixing things via System Restore.

How to repair the operating system and how to restore the operating system configuration to an earlier point in time in Windows Vista (or 7, or 8).
http://support.microsoft.com/kb/936212/#appliesto

See, Control Panel\All Control Panel Items\Recovery\ Open System Restore

How does it boot into Safe Mode?

How to perform a clean boot to troubleshoot a problem in Windows Vista, Windows 7, or Windows 8
http://support.microsoft.com/default.aspx/kb/929135

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

All tests came up clear unfortunately and problem persists.

I will be trying a roll-back to Windows 7 this evening.

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thanks for that. I tried a system restore but no luck unfortunately.

I will try Event Viewer this evening to see if I can identify the problem.

It is looking loke a rollback to Windows 7 might be in order though.

1 person found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thanks for that. I tried a system restore but no luck unfortunately.

I will try Event Viewer this evening to see if I can identify the problem.

It is looking loke a rollback to Windows 7 might be in order though.

Give Joythar Microsoft support engineer Aug 21, 2015 fix a try:

It could be a compatibility issue with the new Fast Startup component.

Try the below steps and check:

Method 1:

1. Open Control Panel / Power Options.
2. On the Left side menu, select Choose what the power buttons do.
3. Select Change settings that are currently unavailable.
4. Scroll down to the Shutdown settings section.
5. Remove the check mark from the Turn on Fast Startup option.
6. Select the Save Changes Button.

Shut Down the computer, wait a couple of minutes and then use the Power Button to start the computer.

You may try from the command prompt and check as well it if it doesn’t fix the issue.

Method 2:

1. Press Windows + X Hope
2. Select Command prompt admin
3. Type powercfg /hibernate on and press enter.

Measure Boot Time in Windows 10 with Windows Boot Timer

Have you ever measured your PC’s boot time? I guess, not! Well, here’s a simple utility called Windows Boot Timer that may interest you. Windows Boot time utility is a useful boot timer utility that loads itself into memory when you start your computer and measures total system boot time.

After all system processes have loaded, the utility removes itself from the system memory and displays the total boot time. No installation is required. All you need to do is double-click on the executable & upon restart; it will display the time taken by your computer to load windows. It does not count the time taken to go through BIOS or BIOS boot up a password.

Sadly, the program without your consent takes you to the developer’s site for feedback and product endorsements.

Measure Windows Boot Time

Download Boot Timer from here. It works with Windows 10, Windows 8, Windows 7 & Windows Vista too! Save all you work and then use this utility.

Run the downloaded utility. It will ask for permission to reboot. Click OK. On reboot, you will first get a message asking you to not use the mouse or keyboard for some time. So please adhere to it. Soon you will get a dialog box telling you your Windows Boot up time.

Here is my regular startup time.

And here are the readings after I removed the start-up entry. My computer was able to shave off a little time.

BootRacer is another tool that helps you measure boot tie.

AppTimer is a freeware that will run an executable, a pre-set number of times and then measure the time it takes to start-up each time.

Soluto will not only measure your boot time but also help you optimize boot time further.

Happy SysAdm

Resources, solutions and tips for system administrators

Tuesday, July 8, 2014

Windows boot time, explored in Powershell

Windows is booting, but what time is it?

4. An introduction to WMI performance classes

5. System boot time from RAW Performance Counters

7. System boot time from COOKED Performance Counters

15. Conclusions

13 comments:

Learned a lot! Thanks.

Wow Giant post 😉
Great article

Glad you liked it, FX!
Carlo

Cool stuff I did not expect to learn in just one blog post! You rock!

Great stuff,
what about if VM was suspended? Wouldn’t that make a TickCount method (and all the WMI methords) display incorrect boot time, since the ticks would not get incremented while VM is in suspended mode?
Which method we can use to display correct boot time in such case?

As Aurimas asked, I’d also like to now. For a workstation that is suspended most of the time, will TickCount and WMI methods return the correct boot time?

I’ve been investigating boot times myself lately. You said that event 12 «returns the exact time your Windows computer bootstraps after POST». How did you verify that? Do you know if this includes the OSLoader phase or not? I was able to verify that this time does not include the time in the BIOS, but could not figure out about OSLoader.

Also, I haven’t been using PS for my investigation, but just recording ETL during boot and then using PerfView to look a the files.

This is event 12 from one of my boots:

0: a 0 0 0 0 0 0 0 | 0 28 0 0 65 40 0 0 . .(..e@..
10: 0 0 0 0 0 0 4c ed | bd 3f 80 68 d1 1 . L. . h..

You can see that the TimeStamp is 08:07:01.047430 while there’s a payload StartTime=»2/16/2016 8:07:00 AM». So I’m not sure what $Event12.Timegenerated gives you, but if it gives you the TimeStamp when the event was written to the log then it’s most probably not the boot time but some tens or hundreds of milliseconds later. Of course, it all depends on what you call «boot time» but still, for this specific event I think that it reports something which happened in the past (before the message was logged), which is why the TimeStamp and StartTime payload are not the same.