Can't connect to OneDrive from my PC!
Hi there, I've had issues recently with connecting and syncing OneDrive on my PC so I contacted the Microsoft support service and they recommended I uninstall then reinstall the OneDrive app but since then I can't connect at all! I keep receiving the 0x8004de40 error message. FYI: I use an Ethernet connection on a private/home network (fiber optic), I have Windows 11 (up to date), on a desktop PC. I tried in WiFi but I get the same message. Using the inetcpl.cplI command, I also made sure only TLS 1.2 and 1.3 were ticked (as recommended by Microsoft support). Bizarrely OneDrive works fine on my laptop connected in WiFi to the same network... Any suggestions? Thanks in advance for your help as I'm at the end of my tether here! 🙃Devices Not Working - File Explorer Not Working - Corrupted Files - Insider Program Beta Release
I started having this issue in December, and finally had a time to try and resolve it today. I contacted support and they said since I'm in the Windows Insider Program, the only support is through this forum. Camera and Audio In early December, my camera stopped working in both Teams and Zoom. Didn't think much of it at the time, but it is persistent, and now I'm doing all my video calls on my iPad. File Explorer - When I click on File Explorer, my display flashes for a second and doesn't do anything. I can get to my files by opening up Control Panel, and then hitting the up arrow to get to my folders. Corrupted Files - I ran a scan in the command prompt (sfc /snannow) and received the following messages (Windows Resource Protection found corrupt files but was unable to fix some of them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log.) - I have the log from today Repair Not working - I went through a whole repair process and tried to reinstall the bad files, but that failed. I almost bricked my OS and lucky to be back where I am. Info: Device name JV-Yoga-2024-01 Processor Snapdragon® X Elite - X1E78100 - Qualcomm® Oryon™ CPU 3.42 GHz Installed RAM 16.0 GB (15.4 GB usable) Device ID A6F067C8-B7D9-4226-9850-46B50601CA0C Product ID 00330-80000-00000-AA099 System type 64-bit operating system, ARM-based processor Pen and touch Touch support with 10 touch points Windows Specs: Edition Windows 11 Enterprise Version 24H2 Installed on ‎8/‎14/‎2024 OS build 26120.1843 Serial number PF4VVG6K Experience Windows Feature Experience Pack 1000.26100.23.0 Insider Program: Installed Build: 26120.1843 ge_release All my updates are current. Please help if you can.
Windows 11 Autopilot and language packages
Hi everyone, I work for a Company with about 10.000 employees. We have a working SCCM envoirenment and an Autopilot PoC which should go live in the near future. The whole project was in cooperation with DELL. The problem here is that DELL scammed us a little bit, because they always ensured us, that we will get the DELL ready image for the region where Notebook is deployed (DELL ready Image contains the LPs for all countries in the Region e.g. central Europe, Asia pecific etc.). At the End Dell told us, that it us technically not possible to provide us this image and the only thing they can do is to provide us the basic US image That's where our problem started... We need some languages for our subsidaries in some countries. Thus we tried to create a package for the Language install. 1. First idea was to use the Powershell cmdlet install-language (https://learn.microsoft.com/en-us/powershell/module/languagepackmanagement/install-language?view=windowsserver2022-ps). The problem here is that this package runs pretty unstable. During Autopilot the command needs about 30 Minutes to finish. Sometimes the command throws an error: "Language Pack or feature could only be partially installed. Error Code: -2147023436“ (I guess it is a timeout but I didn't find anything on Google). The strange thing here is that this cmdlet runs pretty good and stable in private envoirenment. I tested it on my PC at home with Windows 10 22H2 and on a company device with the Microsoft en-US base Image (Win 11 23H2). With Autopilot it worked 70-80% of the time and the rest failed. It was very strange that in the logs the cmdlet faild with error Code: -2147023436, but after Autopilot finished, the Language was available if I called get-language. I also monitored it in the OOBE with the powershell. Result: cmdlet sometimes failed, Language was av Does anyone know how install-language works in the Background? Which URLs are called or what this error code means? Thank you for every kind of help Best regards SvenHow to fix Windows Update 0xc1900101 error?
Hello, my computer running WIndows 11 Insider Preview 23H2 26016.1012 Has stopped updating every time it tries it throws out the error mentioned in the title i have tried a lot of things (Verifying Drivers, Turning off Wi-Fi Card, Updating Drivers, Manually Updating The OS Through An ISO Image, Etc, Etc), but none have worked i remember when checking some Windows Update logs, there was something about it failing in the SAFE_OS phase i don't remember where these logs were though, please tell me how to fix this issue or how to upload more information, and please do not suggest reinstalling in any form, i have tries resetting the pc while keeping the documents and it didn't work and i don't have any storage device big enough to store all my data so i want to keep this system, (Please excuse my grammar i am not a native english speaker). Computer Model: MSI GF63 Thin 11UC CPU: Intel i5-11400H @ 2.70GHz GPU: Nvidia GeForce RTX 3050 Laptop RAM: 2x8GB Dual Channel SO-DDIM DDR4-3200Install Issue - Windows 11 Insider Preview 10.0.26120.2705 (ge_release_upr)
I joined windows insider, and before I start I wanted to note originally only wanted to be in the beta, not the DEV or CANARY builds as I am a beginner. However, at this moment in time, the DEV build downloaded and this build is trying to install, I have clicked download/install multiple times and it takes forever, (I know it takes time but normally is much faster on my device) but when it finally hits 100%, it requests the restart for the update process, whenever my system is rebooted windows update says "Attention Needed" and the install failed. Yet-- when I go to update history this is what shows: Here is what my insider page looks like currently for note: So I am confused and frankly would either like to get this update install gone, or just the beta. Any assistance would be very much appreciated, especially since I am a newbie.Windows Insider 26100 Crashes with iaStorE.sys Upon First Reboot
Manufacturer: Dell Model: Precision 7820 Tower Current Build: 10.0.26100.1 OS: Windows 11 Pro for Workstations ---- After a clean install of Windows 11, 26080, and an upgrade to Windows Update, 26100, the system would always crash upon the first boot. The first crash was a "green" screen with iaStorE.sys as the failing component. Subsequent reboots were blue screens with the same error. Since the crash happened following an attempted upgrade to 26100, there were no restore points to which it could revert back. Each crash resulted in having to do a clean install. . In an effort to troubleshoot, I set Windows Update so that it does not provide drivers when checking for updates via LGPO. However, the update to 26100 does not adhere to this setting, thus resulting in a crash during the first reboot following installation. . The only way I could get build 26100 installed in this system was to do the following: Install 26080 to a Hyper-V VM and upgrade to 26100 Do a sysprep (generalize) Capture the wim via DISM and split the WIM into install.swm and install2.swm Install to the target system using a USB drive with the updated install.swm, install2.swm Once the target physical system was clean installed with build 26100, I created manual system restore points. Then, when doing a Windows Update and accepting the drivers provided, I could recreate the same crash with the same faulting driver. However, in this case, I could boot into the install media and revert to the system restore checkpoint. When I visited the Intel website and manually downloaded the drivers for the afflicted storage device, all worked normally. The Windows Update driver I believe to be causing the issue is "Intel Corporation - SCSAdapter - 7.7.0.1260 (failed)," and it is still being offered via Windows Update. I will, again, configure Windows Update not to provide drivers, but this is undesirable behavior. It is important to note that when this system had Windows 11, 23H2, build 22631.3447, it experienced the same crashing behavior with this device driver.
