builtbybel / builtbybel/FlyOOBE

quit halfway

Open
#452 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
7.3k
Forks
379
PR merge metrics
No merged PRs in 30d

Description

I was hoping to to send a financial input because of solving a 4 day long issue, it all but failed.
This program is so confusing in its initial use, that it bore little confidence.
And sure enough, halfway the proces of installing Win11 25H2, it all went.
Litterally: it went. The update screen just dissapeared. No message, no warning, no feedback, nothing.
Just a computer that found itself in the state as it was before.
I guese this programm needs a lot aof TLC, despite the developper who obviously cares a lot.
I am sorry not to be able to provide a more positive feedback.

Greets, Kurt

Contributor guide

No contributing guide indexed for this repository

Research direction

The report names FlyOOBE and Windows 11 25H2 but no source file, test, or diagnostic information. Start by reproducing the installation failure and locating the relevant installation logs or entry point; done means identifying why the update screen disappears and verifying a user-visible failure path or successful installation.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.