Windows 10: Any way to fix up the Windowsupdate.log file to remove the 1600/12/31?

Every time I run the get-windowsupdatelog command to view the windowsupdate.log file, it's full of entries that state 1600/12/31 18:00:00.0000 Unknown GUID stuff. This happens on every machine I've run it on.

Is there some way to make it not do that as the log file is mostly useless the way it is now since it's all convoluted with those entries mixed in with the actually useful entries.

I've tried clearing out the folder and did get the prompt for the Symbol thing but it had no effect at all.

Thanks.

:)

 

N73 - any way to remove the camera slider function?

So nobody knows?

 

N73 - any way to remove the camera slider function?

All you can do is take it to nearest nokia care to replace your slider or you can keep the slider on for every time. Just select camera from menu and then don't close the cover instead select exit.

May this helped you!

 

You can clear the log history entirely and start over if you wish:

Reset Windows Update in Windows 10

 

What version of Windows 10? An Insider build?

https://support.microsoft.com/en-gb/...0-version-1607

Looks like you're not getting the public symbols. You may have better luck if you download the public symbols yourself.
Download Windows Symbol Packages

FWIW, I have no problems on 1703, os build 15063.250

 

No, this is a regular, Windows 10 Enterprise machine. Not a preview. Just upgraded to Anniversary edition. I'll run it again and see if it's still having issues.

 

Enterprise? In a business environment? can you see this: Microsoft® Symbol Server through the firewall?
https://msdn.microsoft.com/library/w...(v=vs.85).aspx

 

Yes. We don't block much as far as web traffic goes.
When I click that link it says:
Microsoft® Symbol Server

Welcome to the Microsoft Symbol Server. This site is provided by Microsoft to enhance debugging by automatically retrieving symbols for various Microsoft products during a debugging session.

The data at this site is not browseable. Instead, it is accessed by the debuggers that ship with Debugging Tools for Windows .
For more information about how to use the Microsoft Symbol Server click here .

 

If you can see that server then there's no obvious reason why you shouldn't be getting the symbols from it. Apparently you're not though, if every machine behaves like this. Have you tried downloading the symbols from here?

https://developer.microsoft.com/en-u...wnload-symbols

 

It must have been something to do with the 1511 or whatever version I was on. I just reran the command now that I have anniversary installed and everything looks normal. Or else installing 1607 just flushed something out that was causing the issues. Either way, it is now fine.

Thanks!

 

Ah, 1511, that probably explains it. Everything changed with 1607...

https://support.microsoft.com/en-gb/...0-version-1607