Author Topic: Windows Update error - BITS not starting - SOLVED (Read 38424 times)

Shane · « **Reply #25 on:** July 15, 2015, 07:40:01 pm »

Might be worth looking at. So far MS only says the key has to be created and be there. (Of course permissions matter on it as well) but doesnt say on anything being int here that would cause it to mess up. So yeah send me the export, maybe there was something int here that shouldnt have been.

Shane

LadyBird · « **Reply #26 on:** July 16, 2015, 03:09:27 am »

Okay, here we have:
pic 1 - the single entry in the subkey
pic 2 - full 'plain English' view of the data in the entry
txt - regkey export

Hope it helps!

Boggin · « **Reply #27 on:** July 16, 2015, 08:07:14 am »

Just noticed yours is named FilesNotToSnapshot.

LadyBird · « **Reply #28 on:** July 16, 2015, 08:44:13 am »

Oh flipping heck!

I am extremely embarrassed at having been talking twaddle....
In my defence, I was brain dead from going round in circles with the problem.

So, effectively, I deleted a subkey which hadn't been mentioned in any of the previous articles which happened to be under the same key as one in the advice, and then I created a 'replacement' which was actually the one prescribed in the article, so that fixed the problem.

Which means that both of the machines satisfied the criteria of 'not having the key therefore create the key'.
And everything else should be ignored.
Very well spotted Boggin, thank you.

I'm now going to crawl back into a corner and put a blanket over my head until the shame dies down....

Boggin · « **Reply #29 on:** July 16, 2015, 09:47:13 am »

Do you still have the key that you backed up to your Desktop that you could restore and then see if the BITS problem returns.

Failing that, your restore points should be recent enough to go back to before you deleted the key and then you can recreate the FilesNotToBackup key.

The article if I remember correctly, said that if the key existed then to exit the registry - so what would that have solved ?

Office must have created that key separately which I would have thought could have fitted into FilesNotToBackup unless Snapshot means something else.

Shane · « **Reply #30 on:** July 16, 2015, 01:54:11 pm »

lol, well I have the program set to make the 3 folders I had found just in case, so now we will wait and see if that does the trick

Shane

Boggin · « **Reply #31 on:** July 16, 2015, 02:38:30 pm »

I've just checked mine and I have the Snapshot and FilesNotToRestore, but if the keys already exist, how would Windows react to that ?

Shane · « **Reply #32 on:** July 16, 2015, 02:49:09 pm »

It doesnt do anything. I only have the folders themselves set to be created, it doesnt remove first or anything, so if they are already there it keeps on going.

Shane

Boggin · « **Reply #33 on:** July 17, 2015, 12:21:34 am »

Okay - it's just that I thought that when you try to create or copy something that is already there, that usually invokes a prompt possibly to merge.