forum

[resolved] [osu!stable] access OSU when from Win7 32bit to 64bit

posted
Total Posts
3
Topic Starter
Tgfirl4268
The thing is, about a week ago I was still able to access osu normally, but after installing win 7 64bit I tried everything but it said it couldn't connect to the server to update. Can anyone tell me the reason?

This is my logs update:
2024-11-17T09:46:35: CallbackStatus updated to Checking
2024-11-17T09:46:35:
2024-11-17T09:46:35: Beginning update thread
2024-11-17T09:46:35: Stream: Stable40
2024-11-17T09:46:35:
2024-11-17T09:46:35: Running cleanup..
2024-11-17T09:46:35: Cleanup successful!
2024-11-17T09:46:35: Requesting update information...
2024-11-17T09:46:35: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream.
2024-11-17T09:46:35: at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)
2024-11-17T09:46:35: at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
2024-11-17T09:46:35: at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
2024-11-17T09:46:35: at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
2024-11-17T09:46:35: at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
2024-11-17T09:46:35: at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
2024-11-17T09:46:35: at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
2024-11-17T09:46:35: at System.Net.TlsStream.CallProcessAuthentication(Object state)
2024-11-17T09:46:35: at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
2024-11-17T09:46:35: at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
2024-11-17T09:46:35: at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
2024-11-17T09:46:35: at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
2024-11-17T09:46:35: at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
2024-11-17T09:46:35: at System.Net.ConnectStream.WriteHeaders(Boolean async)
2024-11-17T09:46:35: --- End of inner exception stack trace ---
2024-11-17T09:46:35: at #=zRq_m3tTMDZgCTteZIHNJy4Q=.#=z1KOuQfAWYwkc()
2024-11-17T09:46:35: at #=zp$Bjy_gQvQgWG54d91Z4xxI=.#=za5L25P0=()
2024-11-17T09:46:35:
2024-11-17T09:46:35: Saving out global config
2024-11-17T09:46:35:
2024-11-17T09:46:35: Ending update thread with result: Error
2024-11-17T09:46:35:
2024-11-17T09:46:35: CallbackStatus updated to Error
2024-11-17T09:46:35: Running cleanup..
2024-11-17T09:46:35: Cleanup successful!
2024-11-17T09:46:35: Resetting update process
Snapy
Well osu doesn’t support Windows 7, at least I know that Lazer doesn’t, so you will most likely have to upgrade to windows 8. Here’s the supported version list -

Latest Windows Tested:
Windows 10 Technical Preview (10.0.10056)
Previously Tested Releases:
Windows 10 Technical Preview (10.0.9926)
Windows 10 Technical Preview (10.0.9888)
Windows 10 Technical Preview (6.4.9879)
Windows 10 Technical Preview (6.4.9841)
Windows 8.1 Pro x64 Update 1 (6.3.9600.17031)
Windows 8.1 Pro x64 (9600)
Windows 8.1 Leak x64 (9471)
Windows 8 Pro x64 (9200) - If osu! crashes on startup, reinstall the .NET Framework 3.5 (includes .NET 2.0 and 3.0) feature, or fully update your OS via Windows Update
Windows 8 Consumer Preview x64 (8250)
Windows 8 Developer Preview x64 (8102)
Windows 8 Leak x64 (7989)
Windows 8 Leak x86 (7955)

And that was from 13 years ago… so uhh idk how you managed to actually play on Windows 7
Topic Starter
Tgfirl4268
Ok everyone I have now fixed this error through ALL IN ONE RUNTIMES software
Please sign in to reply.

New reply