Andrei V.’s Post

𝐖𝐢𝐧𝐝𝐨𝐰𝐬 𝟏𝟏 𝐈𝐧𝐬𝐭𝐚𝐥𝐥𝐚𝐭𝐢𝐨𝐧 𝐁𝐮𝐠 𝐀𝐥𝐞𝐫𝐭: What Developers Need to Know 🚨 As developers, our workflow depends on reliable and secure systems. Microsoft recently identified a bug in manually created 𝐖𝐢𝐧𝐝𝐨𝐰𝐬 𝟏𝟏 installer media that could disrupt security updates for new PC installations. 𝐇𝐞𝐫𝐞’𝐬 𝐭𝐡𝐞 𝐢𝐦𝐩𝐚𝐜𝐭: If you’ve set up a new machine using October or November 2024 installer media for version 24H2, future security updates won’t install. This could leave systems vulnerable and potentially disrupt development workflows relying on secure environments. 𝐖𝐡𝐚𝐭 𝐜𝐚𝐧 𝐰𝐞 𝐝𝐨? Recreate your installation media with the December 2024 patch, reinstall Windows, and ensure your setups stay compliant. While Microsoft works on a permanent fix, let’s stay proactive and minimize risks to our daily routines. #Linkedin #India #Futurism #AI #Motivation #Innovation #Developers #Windows11 #TechAlert #SecurityUpdates #DailyWorkflow

A widespread Windows outage is not what businesses need on a Friday afternoon. Here's how to fix it: 1. Restart Windows and boot into Troubleshooting mode 2. Open a command prompt 3. Go to C:\Windows\System32\drivers\CrowdStrike 4. Locate the file matching "C-00000291* sys", and delete it. 5. Continue normal startup I hope this helps. Let us know if you have any other workaround to share. #CrowdStrike #Microsoft

A widespread Windows outage is not what businesses need on a Friday afternoon. The screenshot below (from SMH) shows the cause of the issue in tiny text - a device driver called csagent.sys. Here's how to fix it, according to a reliable source: 1. Restart Windows and boot into Troubleshooting mode 2. Open a command prompt 3. Go to C:\Windows\System32\drivers\CrowdStrike 4. Locate the file matching "C-00000291* sys", and delete it. [was: Rename the file CSAgent.sys to something else, eg. donotcrash.sys] 5. Continue normal startup I hope this helps. Let us know if you have any other workaround to share! #GlobalOutage #Microsoft

If You’re Reading This, Please Keep Scrolling… Still here? Well, let’s talk about something we all know is a bad idea but still happens far too often: running cutting-edge software on outdated IT equipment. We all know budgets are tight, and the old hardware still technically works. But pairing 2024-level software with a server that wheezes like it’s running on Windows NT (or NT 3.51 if you’re old like me) is like trying to stream 4K movies on a dial-up modem. Sure, you might get it to work eventually, but at what cost? It just might be your (or your Developer’s) sanity! Modern software requires modern infrastructure. That new SW your team spent months developing, it needs an environment that can actually support its features without constant crashes or lag. Let’s stop asking our developers to innovate while working on systems that were barely state-of-the-art during the dot-com boom. Invest in the tools your people need to succeed. Your team and your customers will thank you. #ITLeadership #TechUpgrades #SoftwareDevelopment #ModernInfrastructure #OmniFederal

This is crazy! I never tried to track my time spent on a computer in a given day until today (Tracking time spent on a project, yes, but that's another story). And it has to be done automatically otherwise too much hassle. Oh boy, it's been 3:59 (h/m) already for today. How much have I accomplished? Not huge. And if you have a lot of days gone by like this that would be nuts. How did I do it? Wrote a little desktop program, nothing fancy but very practical and it starts at Windows startup (10 or 11). See screenshot below. At that point I've already spent 2:19:39 (h/m/s). Even after shutting down and then restart, it would still check your total time spent on this computer for the day. How do you track your time spent on your computer? Assessment of productivity is one thing it can help and for another, maybe a reminder to get off your screen for God's sake, for your vision.

A widespread Windows outage is not what businesses need on a Friday afternoon. The screenshot below shows the cause of the issue in tiny text - a device driver called csagent.sys. Here's how to fix it, according to a reliable source: 1. Restart Windows and boot into Troubleshooting mode 2. Open a command prompt 3. Go to C:\Windows\System32\drivers\CrowdStrike 4. Locate the file matching "C-00000291* sys", and delete it. [was: Rename the file CSAgent.sys to something else, eg. donotcrash.sys] 5. Continue normal startup

A widespread Windows outage is not what businesses need on a Friday! The screenshot below shows the cause of the issue in tiny text - a device driver called csagent.sys. Here's how to fix it: 1. Restart Windows and boot into Troubleshooting mode 2. Open a command prompt 3. Go to C:\Windows\System32\drivers\CrowdStrike 4. Locate the file matching "C-00000291* sys", and delete it. [Or Rename the file CSAgent.sys to something else, eg. CSAgentOld.sys] 5. Continue normal startup I hope this helps.

🤖 T200 Alert! How can companies cope with the Windows outage? In such a crisis, what can companies do? Here is the IMMEDIATE solution- 𝐌𝐚𝐧𝐮𝐚𝐥 𝐑𝐞𝐜𝐨𝐯𝐞𝐫𝐲 Booting in Safe Mode and deleting problematic driver files is the first step for many IT departments. But how do you manually recover SO MANY windows systems in such less time? The answer is simple - 𝐀𝐮𝐭𝐨𝐦𝐚𝐭𝐞𝐝 𝐒𝐮𝐩𝐩𝐨𝐫𝐭 Companies are using platforms like Workativ to automate notifications and support. Workativ’s chatbot can send a notification to all your employees ⚠️ And guide them through the manual recovery processes. reduces the burden on service desks and speeds up resolution times. And save the world! 🤠 Want to know more? Leave me a message 💬 #CrowdStrikeUpdate #AzureOutage

Good guidance…

🚨URGENT SHARE SOMEONE NEED IT 🚨 A widespread Windows outage is not what businesses need on a Friday afternoon. The screenshot below (from SMH) shows the cause of the issue in tiny text - a device driver called csagent.sys. Here's how to fix it, according to a reliable source: 1. Restart Windows and boot into Troubleshooting mode 2. Open a command prompt 3. Go to C:\Windows\System32\drivers\CrowdStrike 4. Locate the file matching "C-00000291* sys", and delete it. [was: Rename the file CSAgent.sys to something else, eg. donotcrash.sys] 5. Continue normal startup 👑Full credit of the post , thank you so much Vaughan Shanks #microsoft #crowdstrike #globaloutage