Steamをインストール
ログイン
|
言語
简体中文(簡体字中国語)
繁體中文(繁体字中国語)
한국어 (韓国語)
ไทย (タイ語)
български (ブルガリア語)
Čeština(チェコ語)
Dansk (デンマーク語)
Deutsch (ドイツ語)
English (英語)
Español - España (スペイン語 - スペイン)
Español - Latinoamérica (スペイン語 - ラテンアメリカ)
Ελληνικά (ギリシャ語)
Français (フランス語)
Italiano (イタリア語)
Bahasa Indonesia(インドネシア語)
Magyar(ハンガリー語)
Nederlands (オランダ語)
Norsk (ノルウェー語)
Polski (ポーランド語)
Português(ポルトガル語-ポルトガル)
Português - Brasil (ポルトガル語 - ブラジル)
Română(ルーマニア語)
Русский (ロシア語)
Suomi (フィンランド語)
Svenska (スウェーデン語)
Türkçe (トルコ語)
Tiếng Việt (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
Maybe it is related to certain games, as I also play Skyrim, but it's the Enhanced Edition (whether or not that makes a difference). The other game I was playing a lot when I found the issue happening was Mass Effect. One of the suggestions was to use compatibility mode with older games, so yeah, maybe it's that. It's hard to know for sure, though, at least until I've managed to properly narrow it down. Going to do some more trial-and-error. Will update if I find anything helpful.
Not exactly. From memory I just force-closed it, rebooted and it worked okay after that. Actually I think it jammed up a couple more times throughout the game (cut-scenes), which was a bit annoying because I'd lost my progress up until the most recent checkpoint, but I got through it at least. I feel like the devs probably should be trying to fix this issue, especially for the unlucky ones who find that closing/restarting doesn't help.
EDIT: Sorry, my reply was intended for a different thread (didn't check which one I opened lol). That aside though, I haven't found a fix for this issue either. At this point I think I'm just going to have to do a fresh install of Windows 10, as much as I'm dreading the prospect.
1st: Purging Steam cache [Failed]
2nd: Reinstalling Steam [Failed]
3rd: Moving Steam to another drive [Failed]
4th: Using another computer [Works...but doesn't solve problem]
5th: Restart of machine [Works as per noted before...but is a hard-kill to the problem]
6th: Updated graphic drivers [Failed]
7th: Updated all drivers [Failed]
8th: Updating Windows [Failed]
9th: Updating Bios [Failed]
10th: Steam Compatibility Settings [Failed]
11th: Steam Administrator Settings [Failed]
12th: Windows Power Settings [Failed]
13th: Bios Performance Settings [Failed]
14th: Screaming at the heavens while having a mental breakdown [Failed]
15th: Pleading to the machine as I try restarting the process over and over [Failed]
16th: Reset/modified Steam's Registry keys [Failed]
Now I am here with the only thing I have not tried is a complete rebuild of the machine...which I'm skeptical if it'd have any effect for the amount of trouble it'd be (Running windows 10 educational edition)
Edit: I will note that from my study of the situation: it generates NO logs in event viewer from launch failures, and the only log that gets updated is bootstrap_log, which shows that there was no need to update and verification was complete...it then does nothing else
A: It's something wrong with the OS install itself
B: It's a memory problem where SOMEWHERE something isn't clearing. Reason for my presumption there is because I've had the issue start up recently with a game that PREVIOUSLY wouldn't suffer the lockups. It's the only thing I can also presume for how it would cause windows itself to hang on shutdown/restart (waiting for X task to finish).
For A: Someone would need to test rebuilding a machine for it (which is a funky affair)
For B: That's entirely on support to help figure out what's going on.
It's ENTIRELY possible there is some C solution that I'm missing, but at this point I'm grasping at straws.
Edit: there's another thread apparently with similar notations https://steamcommunity.com/discussions/forum/1/1843566500531445264
Edit2: HOLY SMOKES PRAISE BE THE HEAVENS...For me unhooking my 360 controller and trying to restart steam worked fine
well ♥♥♥♥... i damn near left this thread without reading page 2 thinking i need to find a more recent thread for an answer. decided to goto page 2, read your post... unplugged my ps3 controller and before i can even take a breath, steam automatically opens without any further action.
so thank you for that!
been having this annoying problem for awhile now.
After finally giving up on Windows and switching to Ubuntu semi-permanently, I have been having a pretty good run apart from today when oddly I had the same exact issue again: (Steam not launching, OS stuck while trying to reboot), so after seeing this post figured I'd try unplugging my Xbox 360 controller.... well, there you have it! Reboot "unstuck" itself and Steam is launching again. Seems the issue isn't OS related at all, but directly USB/Hardware/driver related. *shrugs* At least there's a simple solution! Cheers, everyone!
Alright. I've tried all but this one. Not sure where services are.
Point being, sometimes Steam connects as PC powers up from cold.
Mostly, however, a full PC restart is required before Steam can form an online connection.
Windows 10 here.
Always a Steam fan, figuring this common issue to be addressed with a soon patch, please.
Old thread I know... but I too have had this indefinitely restarting windows issue and I am pretty sure it is somehow related to Steam. Did you ever solve this problem?
I know this is really old... but for some technical knowledge, I can provide.
Fast Startup is a setting within windows that is enabled by default. When you shutdown your machine, windows loads everything from your Ram (Memory) into your storage device on the machine so when you turn the machine on again, it can pickup exactly where it left off which can make for a faster startup.
How ever, if you are having technical difficulties with your machine and you "Turn it off and back on again", it will not fix anything because the PC never fully cleared its memory, cache or anything, it turned off, remembered its exact state and turned back on to the same state like nothing ever changed.
The only way to properly clear your cache, memory, etc etc with fast startup enabled is to "Restart" the machine. This sounds contradictory but when you do a restart with fast startup enabled, it clears your cache, memory, etc etc and will then act as a shutdown and reboot.
If you disable Fast Startup which will not harm your machine in any way, shape or form, and you shutdown your machine, it will shutdown, clear your memeory, cache, etc etc and usually fix any weird issues.
Now for the topic; If you open steam and it does not open, it may have already been opened and is just malfunctioning. The reason that Restarting the machine temporarily fixed the issue is because of having fast startup enabled. As i mentioned, with fast startup enabled, shutting down the machine saves its state including the programs that are running, how ever, rebooting the machine with fast start up enabled will not save the state of the machine and will clear any actively running programs, thus allowing you to start up steam properly.
When you click on a program to open said program and nothing happens, you can check the details tab in task manager as the program may be running just not working. Closing the program from the details tab in task manager can allow you to reopen the program without needing to reboot your PC.
In future, just disable fast startup. Its a pain in the butt if you have technical issues.
I always disable it.