Example Disrupted Application Configurations

[alarwasyi98]

Issue Description

Hi there! I recently tried using the PSWindowsDotfiles module to organize my application configurations in a manner similar to UNIX system dotfiles management. I followed the example template provided in the repository and applied it to my computer. However, instead of creating dummy documents for the example, the module disrupted all my existing application configurations, including those for Windows Terminal and VSCode.

Environment

Windows: 23H2
OS Build: 22631.3737

This warning appears every time I start powershell 7, ISE, and VS 2022:

. : File C:\Users\<username>\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 
cannot be loaded because running scripts is disabled on this system. For more information, 
see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.                                                                                                       At line:1 char:
+ . 'C:\Users\<username>\Documents\WindowsPowerShell\Microsoft.PowerShell_pr ... +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo: SecurityError: (:) [], 
PSSecurityException + FullyQualifiedErrorId : UnauthorizedAccess                                                                       

Because there was no documentation explaining that even if I used the example repository it would affect my overall configuration. is there any way to restore and undoing to my config? there's no anything changes even after Uninstalling the Module.

Step to Reproduce

1. Cloned the PSWindowsDotfiles-Example repository from GitHub.
2. Utilized the provided example template from the repository.
3. Followed the documentation to install and configure the module on my Windows 11 system.
4. Run Install-Dotfiles $HOME\PSWindowsDotfiles-Example;

Expected Behavior:

• The module should create dummy documents for the example setup.
• Existing application configurations should remain intact and unaffected.

Actual Behavior:

• The module interfered with existing configurations rather than creating dummy documents.
• My critical application configurations for Windows Terminal and VSCode were disrupted.
• Loss of custom settings and configurations that took significant time to establish.

This issue has caused significant inconvenience as I now need to restore my configurations manually. I believe this behavior is not intended and could affect other users similarly.
Could you please look into this and provide guidance on how to avoid such disruptions in the future? It would also be helpful to update the documentation to prevent other users from experiencing similar issues.

Thank you for your attention to this matter.
Best regards,