Timeline for Why was my answer deleted
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 16 at 8:18 | comment | added | luator | @Ramhound That's a good point, I didn't consider. If the problem indeed wasn't resolved by some fix in the firmware but just by some implicit settings change, then I agree, that it is not a good answer. I'm still with TOOGAM that any hint, which might get your system working, is good to have, but I better understand now why it should maybe rather be a comment than an answer. | |
| Sep 10 at 0:58 | comment | added | Ramhound | @TOOGAM - I am sorry, “I update the firmware and it solved my problem”, isn’t an answer to a question caused by a missing Intel RST driver while installing Windows it’s just dumb luck. | |
| Sep 10 at 0:08 | comment | added | TOOGAM | @Ramhound : Answers where people don't understand the root cause for the answer's success are lame, at least in comparison to being able to educate someone into a real full understanding. However, even a stumbled-upon answer has potential value. If an approach ends downtime and resumes productivity (whether this is a business workstation or not, even if "productivity" is just producing high scores in a game), I see some potential undeniable value in being able to have that success. If I ruled out the likelihood of a BIOS update fixing it, an answer like this could be just what brings success | |
| Sep 6 at 5:51 | comment | added | Ramhound | If you had an issue, and you were trying to install Windows while Intel RST was enabled, and by resetting the firmware resulted in Intel RST becoming disabled. You simply stumbled into a resolution, the real answer to that exact situation, would be to provide the missing driver. I am guessing you cannot confirm which driver was missing, I dislike answers which claim they had the same problem, and after reading them I often conclude they likely didn’t actually have the same problem. It’s often a sign of someone who stumbled upon a solution but doesn’t understand why they had success | |
| Sep 6 at 5:46 | comment | added | Ramhound | @luator - The fact you don’t understand why the firmware reset resolves the problem is exactly the reason you shouldn’t be suggesting it, an educated guess is that you also had an Intel RST issue, and by the firmware resetting your firmware the resulting configuration was changed with regards to Intel RST. Without understanding what settings resulted in the solution to a problem the author identified and confirmed as a conflict with Intel RST it’s hard to say. You like also didn’t have the exact same problem as the author, there many different reasons, you would get that error message. | |
| Sep 4 at 8:12 | comment | added | luator | ... So it was not clear to me how I should have extended the answer. What I do understand now, is that I should have made it clear, that I have different hardware and that the cause of the error was probably different than in the question. | |
| Sep 4 at 8:12 | comment | added | luator | Thanks a lot for putting in the effort and reaching out again! I agree that it would be nice to have some explanation why the BIOS update helped. Unfortunately, I don't know that myself (I only found out that it helped). I didn't add anything from my comment, because I didn't understand how any of it would answer the WHY/HOW or be otherwise relevant for a future reader (obviously I had the same error, otherwise I wouldn't be here; the mere fact that I tried different things before is imo also not really interesting for others). ... | |
| Sep 3 at 14:41 | history | answered | music2myear | CC BY-SA 4.0 |