Do you have a machine that, in the past, was configured to use WSUS, but has now been moved and is unable to receive updates because the WSUS settings are bad? I ran into this and decided to document the steps.
It still needs work, but it’s nice to see that there is something for people to try out now.
In my case, I’m interested in trying this as a front-end for watching videos on my HDTV, as I haven’t found anything that I quite like yet. Also hoping that they eventually work out Blu-ray navigation in VLC, and that makes it into the Windows 8 version.
Two “A”s in my name gets me onto the first page of the credits. :-)
I’ve ran into this a few times. When trying to enable BitLocker in Windows 8, it starts out working but the vague error message “Element not found” quickly appears and it is not possible to proceed with the encryption.
For me, this happens after cloning the Windows install onto a new drive. According to Microsoft, when using a TPM module to store the keys, using UEFI to boot, and the boot drive has changed, this error will appear. It’s most likely the same with Windows 7 as well.
Fortunately, the solution is simple.
Open an administrative command prompt and run this command to reinitialize the boot loader:
Then reboot the machine and try to start BitLocker again.
My Windows 8 machine ran out of disk space this morning. The Windows Search service decided that it should gobble up all of my remaining space with an index file nearly 300 GB in size. But, that’s a different problem.
Anyway, running out of disk space always causes some odd things to happen. One of them was that the flag icon in the system tray reported “Maintenance in progress” and would not stop. Opening up the Action Center, I could see that it indeed claimed maintenance was in progress, but clicking the “Stop” link didn’t do anything. It appears that the automatic maintenance tried to run at some point during the night, broke because the disk was full, and ended up stuck in a bad state. This persisted across a regular reboot.
To fix it, you have to manually start and stop it again.
- Go to Task Scheduler.
- Navigate to Task Scheduler Library\Microsoft\Windows\TaskScheduler.
- Right-click “Regular Maintenance” and select “Properties.”
- Go to the “Settings” tab, check “Allow this task to be run on demand,” and click “OK.”
- Right-click “Regular Maintenance” and click “Run,” then do it again and click “End.”
After this, the automatic maintenance issue should be sorted out.
writhziden in this thread found the solution.
Note, September 8, 2015: This article was written for Windows 8, but the process also works with Windows 10.
Alright, so. I have a Samsung ML-1210 printer, which is a pretty old black-and-white laser printer.
Samsung made an unsigned 64-bit driver available for Windows Vista. This driver also happens to work with Windows 7 (in fact they later re-packaged it and added Windows 7 to the list of supported operating systems). Windows 7 complains about the missing signature but will allow you to install the driver. I used it for a few years this way. However, Windows 8 is not happy to take the driver. It complains about missing file hashes, claims that the software was probably tampered with, and will not install the driver.
Samsung also has a “universal” driver available. I couldn’t get it to work with the ML-1210.
After quite a bit of searching, I came across an easy solution. I noticed that several other Samsung printers from the era have the same driver available for download. Sure enough, the driver supports many different printer models, which is not surprising really since they probably all use a similar if not identical communication protocol. However, on the support page for the ML-2250, they have a different version of the driver posted (9.61 MB instead of 9.6 MB, even though the version number is the same). Hmm…
It turns out that this driver also supports the ML-1210, and it is signed.
Here’s what you do.
- Download the “Print Driver,GDI” version 3.01 (9.61 MB) from the ML-2250 page (linked above). You get a file called ML-2250_Win7_GDI.exe.
- Use WinRAR or a similar tool to extract the files compressed in ML-2250_Win7_GDI.exe.
- In the files you extracted, navigate to Printer\GDI\VISTA_64. Here’s your printer driver. Save the contents, and point Windows here during driver installation.
One other note. Windows 8 didn’t actually ask me for the driver. It just installed the printer without a driver, I had to find it under “Other devices” in the device manager and install the driver manually. After that, everything worked fine.
This solution is probably not limited to the ML-1210, but to other Samsung GDI printers that don’t have a signed driver available for download on their page. There are several printers listed as supported in the INF.
Update: November 5, 2012
Pascal notes in the comments that this also works with a Lexmark printer, so it’s not limited to just Samsung laser printers. Also, I recently had an issue on the server that hosts this site and had to restore a backup of my database, so I lost a few days of comments right around the launch of Windows 8. A few other Samsung printers have been reported working with this driver, including the ML-1740. If you got your printer working, let us all know the model number in the comments below.
Update: March 13, 2013
From the comments, it looks like there are some Xerox printers out there that also work with this driver.