Got to the bottom of the issue with my PC being a twat
It’s the AIO
Rather it’s the fan hub that runs the AIO, it’s straight up died on me
Very annoying, but this does explain the issues
#ComputerIssues
Can’t delete a folder because of the Thumbs.db | https://techygeekshome.info/cant-delete-a-folder-because-of-the-thumbs-db/?fsp_sid=11591 | #Microsoft #Windows#ThumbsDBIssues #MastodonTech #FolderDeletion #TechGlitches #FileManagement #WindowsProblems #DigitalTroubleshooting #ComputerIssues #TechHelp #FileDeletionProblems
https://techygeekshome.info/cant-delete-a-folder-because-of-the-thumbs-db/?fsp_sid=11591
अपने Windows टास्कबार की समस्याओं को तुरंत ठीक करें
क्या आपका Windows टास्कबार काम नहीं कर रहा है? जब टास्कबार जैसी कोई मुख्य सुविधा काम करना बंद कर देती है, तो यह निराशाजनक हो सकता है, जिससे आपके कंप्यूटर का उपयोग करना कठिन हो जाता है। चिंता न करें! अपने टास्कबार को फिर से काम करने के लिए यहाँ कुछ आसान उपाय दिए गए हैं।
पहले आज़माने के लिए त्वरित समाधान
अधिक उन्नत तरीकों में जाने से पहले, इन सरल चरणों को आज़माएँ:
- अपने कंप्यूटर को पुनः आरंभ करें: कभी-कभी, टास्कबार किसी अस्थायी गड़बड़ी के कारण काम करना बंद कर देता है। एक त्वरित पुनरारंभ आपके सिस्टम को ताज़ा कर सकता है और समस्या को हल कर सकता है।
- SFC स्कैन चलाएँ: सिस्टम फ़ाइल चेकर (SFC) दूषित फ़ाइलों को स्कैन और सुधारता है जो समस्या का कारण हो सकती हैं। कमांड प्रॉम्प्ट खोलें,
sfc /scannowटाइप करें और एंटर दबाएँ। - अपने ड्राइवर अपडेट करें: पुराने ड्राइवर समस्याएँ पैदा कर सकते हैं। अपडेट की जाँच करने और नवीनतम संस्करण इंस्टॉल करने के लिए डिवाइस मैनेजर पर जाएँ।
- विंडोज अपडेट की जाँच करें: Microsoft अक्सर बग को ठीक करने वाले अपडेट जारी करता है। सेटिंग्स → विंडोज अपडेट पर जाएँ और “अपडेट की जाँच करें” पर क्लिक करें।
विंडोज एक्सप्लोरर को पुनः आरंभ करें
यदि आपका टास्कबार फ़्रीज़ हो गया है, तो विंडोज एक्सप्लोरर को पुनः आरंभ करने से मदद मिल सकती है। टास्क मैनेजर खोलने के लिए Ctrl + Shift + Esc दबाएँ, “Windows Explorer” ढूँढें, उस पर राइट-क्लिक करें, और “पुनरारंभ करें” चुनें।
कोई दूसरा उपयोगकर्ता खाता आज़माएँ
अगर टास्कबार अभी भी काम नहीं कर रहा है, तो किसी दूसरे खाते पर जाएँ या नया खाता बनाएँ:
- सेटिंग → खाते → परिवार → किसी को जोड़ें पर जाएँ।
- नया खाता बनाने के लिए निर्देशों का पालन करें।
- नए खाते से लॉग इन करें और टास्कबार देखें।
तृतीय-पक्ष सेवाएँ अक्षम करें
कभी-कभी, तृतीय-पक्ष ऐप आपके टास्कबार में हस्तक्षेप कर सकते हैं। जाँच करने के लिए:
- सिस्टम कॉन्फ़िगरेशन खोलने के लिए Win + R दबाएँ और
msconfigटाइप करें। - “सेवाएँ” टैब के अंतर्गत, “सभी Microsoft सेवाएँ छिपाएँ” चुनें और “सभी अक्षम करें” पर क्लिक करें।
- अपने कंप्यूटर को पुनः आरंभ करें और देखें कि टास्कबार काम करता है या नहीं।
PowerShell के साथ Windows ऐप्स को फिर से पंजीकृत करें
यदि अंतर्निहित ऐप्स समस्याएँ पैदा कर रहे हैं, तो आप उन्हें PowerShell का उपयोग करके रीसेट कर सकते हैं:
- व्यवस्थापक के रूप में PowerShell खोलें।
- कमांड टाइप करें:
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"} - एंटर दबाएँ और अपने कंप्यूटर को पुनः आरंभ करें।
“टास्कबार छिपाएँ” सुविधा को अक्षम करें
यदि आपका टास्कबार गायब है, तो सुनिश्चित करें कि ऑटो-छिपाने का विकल्प सक्षम नहीं है:
- सेटिंग्स और वैयक्तिकरण और टास्कबार पर जाएँ।
- “डेस्कटॉप मोड में टास्कबार को स्वचालित रूप से छिपाएँ” को बंद करें।
टास्कबार को लॉक करें
अपने टास्कबार को हिलने या गायब होने से बचाने के लिए:
- सेटिंग्स और वैयक्तिकरण और टास्कबार पर जाएँ टास्कबार पर जाएँ और “टास्कबार को लॉक करें” को ऑन पर सेट करें।
सिस्टम रिस्टोर का उपयोग करें
यदि उपरोक्त में से कोई भी चरण काम नहीं करता है, तो आप सिस्टम रिस्टोर का उपयोग करके पिछले बिंदु पर वापस जा सकते हैं जब आपका टास्कबार काम कर रहा था। सुनिश्चित करें कि आगे बढ़ने से पहले आपके पास रिस्टोर पॉइंट सेट है।
अपने टास्कबार को फिर से काम करने लायक बनाएँ!
आपके विंडोज टास्कबार के काम न करने के कई कारण हो सकते हैं, लेकिन ये चरण आपको इसे जल्दी से ठीक करने में मदद करेंगे। यदि आपको लगता है कि एक तरीका काम नहीं करता है, तो समाधान मिलने तक अगला तरीका आज़माएँ। धैर्य रखें, और आपका टास्कबार कुछ ही समय में वापस आ जाएगा!
#ComputerIssues #FixTaskbar #PCTips #Taskbar #Windows #WindowsHelp #WindowsTroubleshooting
Seems like the original intestines of my most powerful machine are giving up the ghost by and by. I had already replaced the old Radeon HD 7770 graphics card with a Radeon RX 590 a few months ago.
Now something else must have broken.
All I know that the whole machine froze while running under high load, including playing a video. Not even the mouse cursor moved anymore.
Ever since, I can't boot any operating system anymore. The installed Debian seems to halt around the point when it's supposed to create the RAM disc. A Manjaro live system wouldn't boot. Live Debian doesn't boot either, not from an USB drive and not from DVD. It simply stops with a black screen with backlight on. So the boot process starts, but it always halts at some point.
Memtest86+ works. One run didn't show any issues, but I didn't want to leave it running for hours over night or so until something shows up.
Now I'm wondering what broke this time.
RAM: Will be easy to detect by re-installing the old RAM. I got me some used replacement RAM along with the RX 590, also to increase the amount of RAM in the machine. It didn't come in appropriate packaging, though. Still, it worked. Could be it no longer does.
CPU: An old 3-core Phenom II, older even than the mainboard. Might not have survived the mistreatment over the lasts few years. A lot of load for at least one core over hours continuously, and I've never replaced the cooler or the thermal paste. A damaged CPU would be easy to replace for now by acquiring an AMD FX for cheap and adding a second-hand cooler for both the AM3+ and the AM4 socket which I could keep after eventually upgrading the mainboard.
Mainboard: A 970A-UD3. Newer than the CPU, but has seen over a decade of duty. Mainboards should take a lot of beating, but I think they're more susceptible to aging than CPUs. If the mainboard is broken, a repair would be more costly, and I'm on a budget already. Replacement full-size board, replacement CPU (Ryzen 5 Zen probably), replacement RAM, and I'll need a replacement cooler anyway.
SSD: Well, I'd replaced the original HDD with an SSD that had run in another machine previously, although it's still newer than the mainboard. But I don't think live systems refuse to start due to a faulty SSD.
Graphics card: Nope. The graphics card is the second-newest component in that machine. I've installed it only a few months ago. And believe me, I know what a failing graphics card looks like. That wasn't it.
PSU: Nope. That's the newest component, and I think 500W are sizable for this machine.
Come to think of it, not long after installing the replacement graphics card, I experienced a full shutdown. Like, the machine went out completely at once. That happened when I had two instances of the Firestorm viewer running with both avatars at the same party. I did that because the machine finally had the oomph to handle two Firestorms now with 8GB of VRAM instead of 1GB and 16GB of identical RAM instead of a 12GB hodge-podge partly salvaged from the same machine as the SSD.
I can test the SSD and the RAM tomorrow. As for the rest, no idea.
#ComputerIssues #HardwareFailure #Long #LongPost #CWLong #CWLongPost
Now something else must have broken.
All I know that the whole machine froze while running under high load, including playing a video. Not even the mouse cursor moved anymore.
Ever since, I can't boot any operating system anymore. The installed Debian seems to halt around the point when it's supposed to create the RAM disc. A Manjaro live system wouldn't boot. Live Debian doesn't boot either, not from an USB drive and not from DVD. It simply stops with a black screen with backlight on. So the boot process starts, but it always halts at some point.
Memtest86+ works. One run didn't show any issues, but I didn't want to leave it running for hours over night or so until something shows up.
Now I'm wondering what broke this time.
RAM: Will be easy to detect by re-installing the old RAM. I got me some used replacement RAM along with the RX 590, also to increase the amount of RAM in the machine. It didn't come in appropriate packaging, though. Still, it worked. Could be it no longer does.
CPU: An old 3-core Phenom II, older even than the mainboard. Might not have survived the mistreatment over the lasts few years. A lot of load for at least one core over hours continuously, and I've never replaced the cooler or the thermal paste. A damaged CPU would be easy to replace for now by acquiring an AMD FX for cheap and adding a second-hand cooler for both the AM3+ and the AM4 socket which I could keep after eventually upgrading the mainboard.
Mainboard: A 970A-UD3. Newer than the CPU, but has seen over a decade of duty. Mainboards should take a lot of beating, but I think they're more susceptible to aging than CPUs. If the mainboard is broken, a repair would be more costly, and I'm on a budget already. Replacement full-size board, replacement CPU (Ryzen 5 Zen probably), replacement RAM, and I'll need a replacement cooler anyway.
SSD: Well, I'd replaced the original HDD with an SSD that had run in another machine previously, although it's still newer than the mainboard. But I don't think live systems refuse to start due to a faulty SSD.
Graphics card: Nope. The graphics card is the second-newest component in that machine. I've installed it only a few months ago. And believe me, I know what a failing graphics card looks like. That wasn't it.
PSU: Nope. That's the newest component, and I think 500W are sizable for this machine.
Come to think of it, not long after installing the replacement graphics card, I experienced a full shutdown. Like, the machine went out completely at once. That happened when I had two instances of the Firestorm viewer running with both avatars at the same party. I did that because the machine finally had the oomph to handle two Firestorms now with 8GB of VRAM instead of 1GB and 16GB of identical RAM instead of a 12GB hodge-podge partly salvaged from the same machine as the SSD.
I can test the SSD and the RAM tomorrow. As for the rest, no idea.
#ComputerIssues #HardwareFailure #Long #LongPost #CWLong #CWLongPost
Wtf happens if press close app when my phone tells me my user interface isn't working?
Like any other app would just close and reopen when I tap it again.
But like without the UI how would I be able to do anything.
I don't understand why a device would ask a user to essentially disable the way is which they interact with the device.
Interviews today, had 3 already, with a 4th coming up this afternoon.
Computer issues messed up the first one this morning, so that will need to be rescheduled. But I'm hopeful that the others went well.
Has ANYONE in the world successfully gotten #TensorFlow to install on an Apple M1 Mac? If so PLEASE HELP! I am losing it. #MachineLearning #AppleM1 #ComputerIssues #academia #CompSci
EDIT: FINALLY DID IT!!! This website has instructions that worked (in case you are also having this problem!) https://caffeinedev.medium.com/how-to-install-tensorflow-on-m1-mac-8e9b91d93706
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst