Powershell usage and usage for computer diagnostics

I'll comply with any requests. It may be that it is over my head and too much to handle. For me this is about
what can be done, but I'll not leave Win7 as my regular operation system any time soon.

Like Dirty Harry says, 'A man has to know his limitations.'

I've taken the unusual move of doing a Windows 10 reset (no ethernet plugged in.

My goal is to have a new slate to use the tools presented here at 10Forums.

The reason for this was a file folder sharing botch for my homenetworkgroup (called HOMENET) and which
I expect to have to reinstall to the other nodes.

I didn't know how to nor was I likely to understand any explanation of how to reverse what had
become Shared c --- just c showing at the pipe folder icon on the network. Opening that showed
what was on C: in Win10. But it gave no access to the Public folders etc and I knew I had
made some error while typing in which this 'c' became the only share.

Because of this I did the reset.

Without doing any carving out of things, I'll check to see if the stock shared folders are
restored and use Services to simply turn off updates. I'll review all the suggestions made and avoid
introducing anything from another source.

Callender said:

Check what you see here:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center]"cval"=dword:00000000

If set to 1 - try 0 instead and reboot to test.

RE: Blackbird. There is also a way to restore windows defaults. (Run restore backup and you should see the option)

On my machine I no longer need Blackbird. I created a new profile with admin rights and used software to copy existing parts of the old blackbird modified profile into the new one. Then deleted the old profile. I now have Windows 10 without Windows Store, Store Apps, Cortana, Edge. No problem. That's how I like it.

Problem. I was lucky and cannot remember the exact steps taken.

Just making a place holder here for running the Reg key you have. I get the permission denied
to look at Win10 workgroup called homenet (which I always repeat incase it is needed for you to give some command instructions) At this time I have a couple of Win10s on various old HDs and one do-over scratch install to get rid of the
botched shared file which went nowhere. So a clean slate started on one install made from my dvd.

I'm transferring the reg key info via sneaker net on a thumb drive. Will respond when I've completed the task
on all Win10.

We can belay the reg key for a bit.

I made just a bit of progress on that request I had to get a public folder into the Network.
On the desktop I just 'created' a folder called Public and it's properties seem to contain
shared permissions. It's still on the desktop and I made a screen shot of the properties and the
path. I just need help getting this Public folder to where it's useful in network. And to have it
visible at other PCs.

Today I had some hardware problems to resolve and made a few backups. Will post the screen shot
shortly.

Here is the screen shot. Though I've depended on canned public files ready made to share in network,
perhaps this public file can be moved by some means. It does not want to drag and drop though that's part of my ignorance.

Once done I'll have to work my wway through the reg instructions etc.

I belayed the Windows 10 project for a bit or maybe not to return. I'll explain.

I ran the profile fixer but since I did not have Win10 connected, I'd have to return to that.

But here's another thing about all the effort to turn off Windows Update.

I saw the unwanted Update process start again after doing these many things suggested here.
But at one point I had a USB stick attached to transfer a program while the ethernet was
turned off. It turns out, which I found out from another site, that the (triggered) message showing
on a large number of my services.msc activated the Update procedure. Triggered shows like that in parentheses and stays on after reboot

It was an opinion at the other site (I can find the thread in my history if interested) that because
of all the workarounds and 'undocumentated features' of Windows 10 Update that it is acting
like a hostile virus. I tend to agree with this and will watch for any Microsoft revisions in
this tactic.

Please test this yourself for the "USB effect" if you wish.

No powerhell text book for me yet at the local library. Perhaps someone made off with it.

If you wish to close the thread please advise.