Jump to content

BOOT

Members
  • Posts

    488
  • Joined

  • Last visited

Everything posted by BOOT

  1. It could be one of the entries in: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components They are processed when the user profile is first created. You can test each one in turn as they can be disabled by adding a REG_DWORD entry "Enabled" with a value of 0
  2. I have it set via group policy; the changes stay even if the policy is removed, they don't change back.
  3. The values are under in the users registry: Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders The key names are guids Documents: {FDD39AD0-238F-46AF-ADB4-6C85480369C7} LocalDocuments: {F42EE2D3-909F-4907-8871-4C22FC0BF756} Set the type to REG_EXPAND_SZ and the value to the path you want.
  4. KnownFolders have had an overhaul, there's at least 3 IDs for documents now. If they're not set, they'll default to the user profile.
  5. @samaaron I use a custom launcher that does the following: Stops any scsynth or or sonic-pi processes running for that user Clears the contents of the numbered folder in boost_interprocess Runs sonic-pi This works pretty well, though I do occasionally have to clear the users .sonic-pi folder completely.
  6. Check the permissions on: C:\ProgramData\boost_interprocess and delete any files within. Check that scsynth.exe isn't still running.
  7. Try downgrading Intel Display drivers to v26.x
  8. How are you removing profiles? Delprof, ProfileList registry and Users\Profile folder deletions are going to break the sync between the UWP App registry and the Profile.
  9. or: net use \\server /delete
  10. I use: /auto upgrade /DynamicUpdate disable /Compat IgnoreWarning /quiet /noreboot
  11. Looks like stockpiling is back.
  12. It's a little more complex, there is a GPO that makes it a lot easier (not needing to edit hundreds of users): Computer Policy \System\User Profiles\[Only allow local user profiles]
  13. Just out of curiosity... have you used delprof2 on any of those?
  14. Roaming profiles are no longer supported. Switch to using local profiles, far fewer problems.
  15. Pub seems to be a safer environment than school TBH.
  16. It's an optional feature now, no longer a package. I use this powershell script: if (-Not $PSScriptRoot) { $PSScriptRoot = Split-Path $MyInvocation.MyCommand.Path -Parent } Write-Output "Running from: $PSScriptRoot" Import-Module Dism Enable-WindowsOptionalFeature -Online -FeatureName NetFx3 -Source "$PSScriptRoot" -LimitAccess -All
  17. Have you tried disabling automatic repair? As in this post: http://www.edugeek.net/forums/security/201386-access-admin-command-prompt-automatic-startup-repair.html#post1718910
  18. If it's just the odd one, test the RAM. If they're all the same model, it's probably driver related.
  19. Got tired of removing user profiles with broken XP-era tools. Found scripts that weren't much better. Decided I could do better. https://github.com/SN29856L/UserProfileCleanup/releases/tag/v0.2
  20. Anyone else completely in the dark about the imminent return?
  21. The policy is in the same place as the other one. I've never found it to break anything. Scripts still work etc. Just stops them browsing to it by typing the path or clicking "Open File Location". I would also suggest looking at restricting the default administrative shares (C$ etc) as you can still browse the local disk via those.
  22. Are you also using the "Prevent access" policy or just "Hide these drives"?
  23. Yes, and I'd definitely recommend it.
  24. Change the path in the value "ProfilesDirectory" in: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
  25. Unmanned flying machines.. What do you think the collective noun for drones should be? So far: Squadron Flight Wing
×
×
  • Create New...