Results tagged “Windows” from Kazza the Blank One
So this is the error I've been getting ever since the October 2016 Windows 10 updates:
"Error in scanner. Turn off scanner and follow instructions in manual. Scanner driver will be closed. Code : 47,1130,0"
I get it at least half the time I attempt to scan. If I hit OK and hit scan again (I don't bother rebooting the scanner), it'll give me the error up to a few more times, but will eventually scan. It's really pissing me off. I've yet to try it on a different computer to see if it's a problem with the scanner or with windows.
But there's literally no other pages on the internet (that I could find) with that exact error code. So if you come here looking for a solution, sorry I don't have one. But if you do find something, let me know and I'll post it here.
The other weekend I patched and rebooted my computer, as you do.
Except afterwards a whole stack of crap got broken or went weird.
I lost Irfanview from the right-click open-with. Had to go select the application again to get it to remember it.
It changed all my window bars from blue to magenta. Even tho it was still set to blue in the settings. Changed it and changed it back again and it came good.
It finally killed all my scheduled tasks. Ever since upgrading to Windows 10, the scheduled tasks I have that pop up reminders to do things at certain times/days stopped being listed in the Task Scheduler, and gave me errors any time I tried to open it. The tasks all still worked but I just couldn't see or edit them. Well after the last patching cycle they finally stopped working altogether, which is a pain because now I'll have to set them all up again.
I've had issues with my scanner ever since. I don't know if it's a driver problem or a hardware problem. But if I keep clicking ok to the error and trying again it'll scan. Super annoying.
And Windows 10 is extremelly rude and reboots for patching without permission. Often it'll pop up a thing and you can choose to schedule it, but you can only choose to schedule it for a few days before it insists on having to do it. But the other day I came home and it had rebooted without my permission and no warnings. #grunt
Last night we went over to Ben's new place for dinner. He made a lasagna which was delicious. Then just chatted and half watched the food channel. His new flatmate Tim seems like quite a nice guy.
Bit better day today. Even though I never rebooted, the scanner decided it would work this morning so scanned thirty six photos.
Tonight my todo list took me til just now (9:40pm) to get through. It include such things as cooking dinner, cleaning up the kitchen and running the dishwasher, taking out the recycling, doing a load of washing and hanging it out, and downloading my photos and backing up my computer. That one took a while because I was closely watching it to make sure windows 10 didn't do anything funky with robocopy. Aside from some new status codes (anything that's not modified is "modified" - wtf?? and some files said "older", but what the heck does that mean? It still has extra files, actually modified files, new files etc. Weird weird weird). But I checked source and destination file and byte counts and it all looked ok.
I also managed to geotag day 33 of my trip, and after adding the exiftool to the exclusions list from Windows Defender, it seems to run a *lot* faster!
Now it's 9:45pm and I still need to wash my hair.. :/
So windows 10 has not been as disruptive as I thought.
The damned Antimalware Service Executable interferes with everything. Mainly GeoSetter. Any time I try and save images edited with GeoSetter, the stoopid Windows Defender decides to hogg all the available CPU, and my machine grinds to a halt. Saving a directory of images in GeoSetter used to take minutes, now it takes *hours* :(:(:( Super frustrating. I've tried putting in exclusions for the MsMpEng.exe, for the GeoSetter.exe and the photo folder, but nothing works. It's making the whole geotagging process very frustrating. #grunt
So a pretty good weekend. In that I got to spend most of it at home doing *stuff*.
Yesterday I installed Windows 10 on my puta. After one false start I tried again and it installed. Took most of the day to download, install, fail, try again and install.
Some notes so far:
* video adapter was not found straight away so had to download an updated driver for it
* ugly window frames. seriously. ugly.
* it kept all my task bar settings which was nice of it
* gadgets are gone - but logitech motion sensor still works
* images defaulted back to opening with microsoft, had to change back to acdsee
* geosetter had a spaz about Internet Explorer, but I'm not sure it was that - could just have been our internet which has been mostly dead all weekend, or the file on the site just wasn't there anymore. Coincidence?
Other than that yesterday was fish tank stuff, housework and food shopping. Chrissie came up in the evening for a roast pork dinner, and we just chatted for ages after dinner which was nice.
Today was some food cooking, holiday photo processing, a walk with Chris, pool maintenance, more food cooking etc. I'm sure there was more but it escapes me right now.
Our internet has been epic fubar this weekend. Usually it's bad when it's windy/rainy, but it's been especially fail this weekend.
Oh we also bought some danios to be dither fish in my upstairs two foot, which they did splendidly for. The rummy nosed tetras coloured up beautifully and have been swimming around not just hiding. The danios I have in my big tank look *huge* in comparison - I think they're all girls! Stu bought some worms which I've fed to all the fish. The angel knew exactly what to do, but the danios took a while to figure out they were food!
But after some time of it extracting files, it gave this lovely friendly error:
Windows cannot access the installation sources. Verify that the installation sources are accessible, and restart the installation.*yay*
Googling tended to indicate that probably the hard drive was fubar. Fine. Well lets see if I can boot off a live CD and mount my drive and see what can be salvaged.
The two knoppix cds I have refused to boot (the old Neither of my Knoppix cds boot. Can't find KNOPPIX filesystem, sorry. error) so tried a Suse cd Simon burnt me last year. This thing *just worked* first go, even on the network.
So figured out how to mount the internal drive ( mount -t ntfs /dev/sda3 /mnt ) and then attached a memory stick. Was able to retrieve the file I most wanted to. But had all sorts of problems with the drive staying online (and getting lots of I/O errors in the syslog). Stu brought home a large hard drive for me to copy files to, but Suse kept wanting to make the NTFS drive read only. Tried a few things, but in the end just formatted the disk as linux. Will be able to copy off from a live CD if need be.
So I'm currently copying off what I can from stuff I know I've modified in the past few weeks.
The plan is to buy a new drive as soon as possible, install Windows 7 on it (Windows will be on a separate partition this time!!), then restore/retrieve my data from backups. The medium term plan is to get a file server so can actually do daily backups, instead of backups every couple of weeks when I bring home hard drives to backup to.
I kinda like this Suse thingie too. May even setup a virtual machine with it on at some point.